This can be a wiki submit; please edit as essential.
Please, contemplate subscribing to the Testing Updates Bulletins RSS feed
As famous by @mbod for testing-update-2019-05-29, it can be completely fastened
by removing and re-adding the pool’s cachefile :
Gadgets from earlier replace sets
- 1 Gnome 3.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 end
- 10 AMD-Ucode introduction
- 11 Rebuilding fontconfig cache: failed to put in writing cache
- 12 LibreOffice has no window ornament in KDE
- 13 Putting in glibc (2.28-Four) breaks the dependency “glibc=2.27” required by lib32-glibc
- 14 One thing 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 3.32: Two extensions removed from our repos.
We’ve 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 utilizing Topicons Plus on Gnome Three.32 might leads to very high CPU usage.
We strongly advocate you to disable those extensions if they’re enabled (Tweaks > Extensions) and take away these packages together with your favourite package deal supervisor. To stop potential issues with the subsequent model of Gnome, you might do these steps (or at the very least the first one) earlier than upgrading your system.
Gnome 3.32: Numerous problems
There’s presently several problems with Gnome Three.32. Here’s what we know thus far.
1. Risk of damaged extensions
Broken extensions is something to anticipate when transitioning between major variations of Gnome, especially in case you are using extensions that aren’t shipped by default on Manjaro Gnome. If in case you have a damaged extension taken from some place else than Manjaro official repositories, you will have to contact the maintainer on the supply you could have taken the extension from to get more help. You might also need to report the problem to the developer(s) of the extension (if not the same individual/group).
It is potential that extensions turn into so damaged on Gnome Three.32 that it makes Gnome Shell crash utterly when making an attempt to log in, thus making Gnome utterly unusable. For instance, we’ve a report of such situation 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 doesn’t come from Manjaro official repositories) and make the improve smoother, you’ll be able to disable all Gnome extensions (Tweaks > Extensions) earlier than upgrading your system, then allow them one after the other solely after being logged in a totally new session on Gnome Three.32.
2. Using world clocks can break Gnome Shell utterly
If 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 have 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 for those who use Wayland
In case you are utilizing Wayland (as an alternative of X.org), Gnome Shell might crash when resuming from sleep. Upstream is conscious of this concern. 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’ll not receive any updates from us for this package deal. A very previous package deal named yaourt-gui-manjaro has been eliminated at 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 out of your system.
Along with that, we’ve dropped help for several packages that trusted yaourt: allservers, pacli and pacli-jwm. Those packages has been faraway from the official repositories utterly.
vlc-nightly has been dropped
The vlc-nightly package deal, which was actually useful in a time when VLC 3 was not formally out but, has been dropped on our aspect and is not in the official repositories anymore. Should you nonetheless have this package deal and also you want the newest secure version of VLC media participant, take away vlc-nightly, then set up the vlc package deal.
Otherwise, you’ll be able to proceed to use vlc-nightly from the AUR (but you’ll need to compile it your self).
Kodi 18.1: extensions might not work properly.
Kodi 18.1 is now obtainable in our repositories. Since this can be a main version change, extensions for Kodi (in the event you use some) might stop working correctly. Developers of these extensions will need to make them suitable with Kodi 18.
If Kodi 18.1 doesn’t work correctly for you and also you absolutely want to make use of your extensions, you could use the previous kodi package deal in /var/cache/pacman/pkg so as to downgrade Kodi to model 17.6. Please observe that it is a short-term workaround and that the software offered in the previous kodi package deal might cease working properly sooner or later too. You shouldn’t maintain 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 challenge. Usually not needed in that version.
Plasma won’t reboot from the Software Launcher
In case you update from within Plasma (e.g. from the konsole), chances are you’ll have to concern 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 accessible within the official repositories and supplies dbus compiled with out the –without-x choice.
To switch dbus with dbus-x11 package deal, simply install dbus-x11 together with your favorite package deal manager: dbus shall be replaced by dbus-x11.
Pamac: “Failed to commit transaction – Transaction not prepared” at the end
Up to now, it has solely been a false alarm: updates are utilized efficiently.
Until you’ve already completed this previously, All users of AMD-APUs/CPUs should install 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 a solution. More concerning the problem here.
LibreOffice has no window ornament in KDE
New line export SAL_USE_VCLPLUGIN=gtk3_kde5, once merged into present /and so forth/profile.d/libreoffice-fresh.sh , fixes a reasonably longterm difficulty. If it doesn’t be just right for you, you might use gtk as an alternative of gtk3_kde5 as UI framework.
Putting in glibc (2.28-Four) breaks the dependency “glibc=2.27” required by lib32-glibc
Set up the update both:
- from terminal: sudo pacman -Syu or;
- with Octopi as an alternative of Pamac.
One thing utilizing Perl/Python/glibc broke
- If it’s an AUR package deal, try to reinstall it from AUR. It more than likely needs to be rebuilt.
- If it’s a repo package deal, please report and examine back repeatedly 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 simply won’t work with the newer Quantum-based Thunderbird.
Learn more about Thunderbird 60 here: Thunderbird 60
Firefox – WebGL not working anymore
You might attempt the following answer:
Open about:config and set security.sandbox.content.read_path_whitelist to /sys/.
libutf8proc>=2.1.1-3 update might require guide intervention
This could normally be routinely fastened by way of manjaro-system replace.
The libutf8proc package deal prior to version 2.1.1-Three had an incorrect soname link. This has been fastened in 2.1.1-Three, so the improve might want to overwrite the untracked soname hyperlink created by ldconfig. When you get an error
libutf8proc: /usr/lib/libutf8proc.so.2 exists in filesystem
when updating, use
pacman -Suy –overwrite usr/lib/libutf8proc.so.2
to carry out the improve.
Pamac: “Invalid or corrupted package.”
In the event you obtain 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)…
==> Fix libutf8proc upgrade …
in search of conflicting packages…
Packages (1) libutf8proc-2.1.1-4
Complete Obtain Measurement: zero.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 obtainable 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 upgrade…
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 following steps: shut Pamac window first, then launch it once more and begin the replace process again. It should proceed from where it left off.
Issues with folder view widget in KDE v5.13
KDE introduced a new setting for icon sizes. Now you’re capable of define also the dimensions in your panel. If in case you have a high-DPI display, you could need to improve the worth. This can repair the show concern with given widget.
With this update we’ve got a /and so on/pulse/default.pa.pacnew. It might be essential to merge (some strains associated to “GSettings” in /and so on/pulse/default.pa ) if ‘default.pa’ has been customised.
File conflict engrampa.tap
thunar-archive-plugin: /usr/lib/xfce4/thunar-archive-plugin/engrampa.tap 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. Remove engrampa-thunar-plugin to proceed with the replace.