This can be a wiki publish; please edit as needed.
Please, think about subscribing to the Testing Updates Bulletins RSS feed
Gadgets from previous replace sets
- 1 Gnome Three.32: Two extensions removed from our repos.
- 2 Gnome 3.32: Numerous problems
- 3 Yaourt: Relaxation in peace
- 4 vlc-nightly has been dropped
- 5 Kodi 18.1: extensions might not work properly.
- 6 Notifications wanting weird in XFCE
- 7 Plasma won’t reboot from the Software Launcher
- 8 I can’t open Nemo with elevated privileges (as root)
- 9 Pamac: “Failed to commit transaction – Transaction not prepared” at the finish
- 10 AMD-Ucode introduction
- 11 Rebuilding fontconfig cache: failed to put in writing cache
- 12 LibreOffice has no window decoration in KDE
- 13 Putting in glibc (2.28-4) breaks the dependency “glibc=2.27” required by lib32-glibc
- 14 Something utilizing Perl/Python/glibc broke
- 15 I’ve lost a Thunderbird addon/function
- 16 Firefox – WebGL not working anymore
- 17 libutf8proc>=2.1.1-3 update might require guide intervention
- 18 Pamac: “Invalid or corrupted package.”
Gnome Three.32: Two extensions removed from our repos.
We now have dropped two packages that shipped further extensions for Gnome: gnome-shell-extensions-topicons-plus-huttli and gnome-shell-extensions-taskbar. We gained’t keep Topicons Plus and Taskbar anymore.
Those extensions are usually not in lively improvement anymore and should not work properly (or not work in any respect) on Gnome 3.32. Notably, it has been reported that using Topicons Plus on Gnome Three.32 might leads to very excessive CPU usage.
We strongly advocate you to disable those extensions if they are enabled (Tweaks > Extensions) and remove those packages together with your favourite package deal supervisor. To stop potential issues with the subsequent version of Gnome, chances are you’ll do these steps (or no less than the primary one) earlier than upgrading your system.
Gnome 3.32: Numerous problems
There’s presently several problems with Gnome 3.32. Here is what we all know thus far.
1. Risk of broken extensions
Broken extensions is one thing to anticipate when transitioning between main versions of Gnome, especially in case you are using extensions that are not shipped by default on Manjaro Gnome. If in case you have a broken extension taken from some other place than Manjaro official repositories, you’ll have to contact the maintainer on the source you’ve got taken the extension from to get extra help. You might also need to report the problem to the developer(s) of the extension (if not the identical individual/group).
It’s attainable that extensions turn out to be so damaged on Gnome 3.32 that it makes Gnome Shell crash utterly when making an attempt to log in, thus making Gnome utterly unusable. For example, we have now a report of such concern with a third-party extension (that doesn’t come from Manjaro’s official repositories) referred to as Extensions.
To decrease the danger of breakage (especially if operating Gnome extensions that does not come from Manjaro official repositories) and make the improve smoother, you possibly can disable all Gnome extensions (Tweaks > Extensions) earlier than upgrading your system, then enable them one after the other only after being logged in a totally new session on Gnome Three.32.
2. Using world clocks can break Gnome Shell utterly
In case you have configured world clocks in Gnome, it might make Gnome Shell segfaults and crashes when making an attempt to log in for a graphical session, making Gnome unusable. If it occurs, you will want to reset your parameters for world clocks with the following command (do it in TTY): dbus-launch gsettings reset org.gnome.clocks world-clocks.
See this Arch Linux thread and this ticket from upstream.
3. Gnome Shell might crash utterly when resuming from sleep when you use Wayland
In case you are using Wayland (as an alternative of X.org), Gnome Shell might crash when resuming from sleep. Upstream is conscious of this problem. As a workaround, you might use X.org as an alternative of Wayland for now.
Some packages don’t get targeted after being launched. Reported to upstream and confirmed for distributions aside from Manjaro too.
Yaourt: Relaxation in peace
Yaourt has been faraway from our repositories utterly. We gained’t keep the yaourt package deal anymore, which signifies that you will not receive any updates from us for this package deal. A really previous package deal named yaourt-gui-manjaro has been eliminated on the similar time too.
In case you are still using Yaourt, we strongly encourage you to modify to an alternate like Pamac CLI (package deal: pamac-cli), Trizen (package deal: trizen), Yay (package deal: yay) or Pacaur (package deal: pacaur); and uninstall Yaourt from your system.
Along with that, we’ve dropped help for several packages that trusted yaourt: allservers, pacli and pacli-jwm. These packages has been faraway from the official repositories utterly.
vlc-nightly has been dropped
The vlc-nightly package deal, which was really helpful in a time when VLC 3 was not officially out yet, has been dropped on our aspect and isn’t in the official repositories anymore. Should you still have this package deal and you need the newest secure version of VLC media player, remove vlc-nightly, then install the vlc package deal.
Otherwise, you’ll be able to proceed to make use of vlc-nightly from the AUR (but you’ll need to compile it yourself).
Kodi 18.1: extensions might not work properly.
Kodi 18.1 is now out there in our repositories. Since this can be a major version change, extensions for Kodi (should you use some) might stop working properly. Builders of those extensions will need to make them suitable with Kodi 18.
If Kodi 18.1 doesn’t work correctly for you and you absolutely want to make use of your extensions, you might use the previous kodi package deal in /var/cache/pacman/pkg in an effort to downgrade Kodi to version 17.6. Please notice that it is a momentary workaround and that the software offered within the previous kodi package deal might stop working properly sooner or later too. You shouldn’t hold the downgrade eternally.
Notifications wanting weird in XFCE
Because the package deal dunst consists of now dunstfy in the primary package deal notifications might not displayed properly in XFCE. Please uninstall that package deal to unravel that difficulty. Normally not wanted in that edition.
Plasma won’t reboot from the Software Launcher
Should you update from within Plasma (e.g. from the konsole), you might have to difficulty a systemctl reboot to reboot.
I can’t open Nemo with elevated privileges (as root)
Workaround discovered: Use the dbus-x11 package deal as an alternative of the regular dbus package deal. This package deal is on the market in the official repositories and offers dbus compiled with out the –without-x choice.
To exchange dbus with dbus-x11 package deal, merely install dbus-x11 together with your favorite package deal manager: dbus shall be changed by dbus-x11.
Pamac: “Failed to commit transaction – Transaction not prepared” at the finish
Up to now, it has only been a false alarm: updates are applied efficiently.
Until you’ve already executed this beforehand, All customers of AMD-APUs/CPUs ought to set up this update like this:
sudo pacman -Syyu
sudo pacman -S amd-ucode
sudo pacman -R intel-ucode
Step Three is optionally available.
Rebuilding fontconfig cache: failed to put in writing cache
Please ignore this message. Upstream already works on an answer. More concerning the difficulty right here.
LibreOffice has no window decoration in KDE
New line export SAL_USE_VCLPLUGIN=gtk3_kde5, once merged into present /and so forth/profile.d/libreoffice-fresh.sh , fixes a moderately longterm problem. If it doesn’t be just right for you, you could use gtk as an alternative of gtk3_kde5 as UI framework.
Putting in glibc (2.28-4) breaks the dependency “glibc=2.27” required by lib32-glibc
Set up the replace both:
- from terminal: sudo pacman -Syu or;
- with Octopi as an alternative of Pamac.
Something utilizing Perl/Python/glibc broke
- If it’s an AUR package deal, try to reinstall it from AUR. It most certainly needs to be rebuilt.
- If it’s a repo package deal, please report and examine again often for updates.
I’ve lost a Thunderbird addon/function
Thunderbird 60 disables incompatible addons by default. There’s an about:config change do you have to need to force-enable the addon, but many addons merely won’t work with the newer Quantum-based Thunderbird.
Learn extra about Thunderbird 60 right here: Thunderbird 60
Firefox – WebGL not working anymore
Chances are you’ll attempt the next answer:
Open about:config and set security.sandbox.content material.read_path_whitelist to /sys/.
libutf8proc>=2.1.1-3 update might require guide intervention
This should usually be mechanically fastened by way of manjaro-system update.
The libutf8proc package deal previous to model 2.1.1-3 had an incorrect soname link. This has been fastened in 2.1.1-Three, so the improve will need to overwrite the untracked soname hyperlink created by ldconfig. For those who get an error
libutf8proc: /usr/lib/libutf8proc.so.2 exists in filesystem
when updating, use
pacman -Suy –overwrite usr/lib/libutf8proc.so.2
to perform the upgrade.
Pamac: “Invalid or corrupted package.”
For those who receive an “Invalid or corrupted package.” error message with Pamac and if the small print accommodates an output just like the next:
DetailsSynchronizing package deal databases…
Starting full system upgrade…
Loading packages information…
Checking file conflicts…
Checking out there disk area…
Upgrading manjaro-system (20180702-1 -> 20180716-1)…
==> Repair libutf8proc upgrade …
on the lookout for conflicting packages…
Packages (1) libutf8proc-2.1.1-4
Complete Download Measurement: 0.05 MiB
Complete Put in Measurement: 0.32 MiB
Internet Upgrade Measurement: 0.00 MiB
:: Proceed with installation? [Y/n]
:: Retrieving packages…
checking package deal integrity…
loading package deal information…
checking for file conflicts…
checking out there disk area…
:: Processing package deal modifications…
:: Operating post-transaction hooks…
(1/1) Arming ConditionNeedsUpdate…
Operating post-transaction hooks…
Warning: lock file missing /var/lib/pacman/db.lck
Starting full system improve…
Error: could not open file /var/lib/pacman/local/libutf8proc-2.1.1-2/information: No such file or directory
Warning: couldn’t absolutely load metadata for package deal libutf8proc-2.1.1-2
Failed to organize transaction:
invalid or corrupted package deal
Attempt the next steps: shut Pamac window first, then launch it again and start the replace process again. It should continue from where it left off.
Points with folder view widget in KDE v5.13
KDE launched a new setting for icon sizes. Now you’re capable of define also the dimensions on your panel. In case you have a high-DPI show, you could need to improve the value. It will repair the display concern with given widget.
With this update we now have a /and so on/pulse/default.pa.pacnew. It might be necessary to merge (some strains related to “GSettings” in /and so forth/pulse/default.pa ) if ‘default.pa’ has been customised.
File battle engrampa.faucet
thunar-archive-plugin: /usr/lib/xfce4/thunar-archive-plugin/engrampa.faucet exists in filesystem (owned by engrampa-thunar-plugin)
thunar-archive-plugin has added native help for the Engrampa archive manager. engrampa-thunar-plugin is not wanted. Take away engrampa-thunar-plugin to continue with the update.