Known issues and solutions
This is a wiki post; please edit as necessary.
Please, consider subscribing to the Testing Updates Announcements RSS feed
Gnome 3.32: Two extensions removed from our repos.
We have dropped two packages that shipped additional extensions for Gnome:
gnome-shell-extensions-taskbar. We won’t maintain Topicons Plus and Taskbar anymore.
Those extensions are not in active development anymore and may not work properly (or not work at all) on Gnome 3.32. Notably, it has been reported that using Topicons Plus on Gnome 3.32 may leads to very high CPU usage.
We strongly recommend you to disable those extensions if they are enabled (Tweaks > Extensions) and remove those packages with your favorite package manager. To prevent potential problems with the next version of Gnome, you may do those steps (or at least the first one) before upgrading your system.
Gnome 3.32: Various problems
There is currently several problems with Gnome 3.32. Here is what we know so far.
1. Possibility of broken extensions
Broken extensions is something to expect when transitioning between major versions of Gnome, especially if you are using extensions that are not shipped by default on Manjaro Gnome. If you have a broken extension taken from somewhere else than Manjaro official repositories, you will have to contact the maintainer on the source you have taken the extension from to get more support. You may also want to report the problem to the developer(s) of the extension (if not the same person/group).
It is possible that extensions become so broken on Gnome 3.32 that it makes Gnome Shell crash completely when trying to log in, thus making Gnome completely unusable. For example, we have a report of such issue with a third-party extension (that doesn’t come from Manjaro’s official repositories) called Extensions.
To decrease the risk of breakage (especially if running Gnome extensions that does not come from Manjaro official repositories) and make the upgrade smoother, you can disable all Gnome extensions (Tweaks > Extensions) before upgrading your system, then enable them one by one only after being logged in a completely new session on Gnome 3.32.
2. Using world clocks can break Gnome Shell completely
If you have configured world clocks in Gnome, it may make Gnome Shell segfaults and crashes when trying to log in for a graphical session, making Gnome unusable. If it happens, you will need 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 may crash completely when resuming from sleep if you use Wayland
If you are using Wayland (instead of X.org), Gnome Shell may crash when resuming from sleep. Upstream is aware of this issue. As a workaround, you may use X.org instead of Wayland for now.
Some programs don’t get focused after being launched. Reported to upstream and confirmed for distributions other than Manjaro too.
Yaourt: Rest in peace
Yaourt has been removed from our repositories completely. We won’t maintain the
yaourt package anymore, which means that you will not receive any updates from us for this package. A very old package named
yaourt-gui-manjaro has been removed at the same time too.
If you are still using Yaourt, we strongly encourage you to switch to an alternative like Pamac CLI (package:
pamac-cli), Trizen (package:
trizen), Yay (package:
yay) or Pacaur (package:
pacaur); and uninstall Yaourt from your system.
In addition to that, we have dropped support for several packages that depended on
pacli-jwm. Those packages has been removed from the official repositories completely.
Items from previous update sets
vlc-nightly has been dropped
vlc-nightly package, which was really useful in a time when VLC 3 was not officially out yet, has been dropped on our side and is not in the official repositories anymore. If you still have this package and you want the latest stable version of VLC media player, remove
vlc-nightly, then install the
Otherwise, you can continue to use
vlc-nightly from the AUR (but you’ll have to compile it yourself).
Kodi 18.1: extensions may not work properly.
Kodi 18.1 is now available in our repositories. Since this is a major version change, extensions for Kodi (if you use some) may stop working properly. Developers of those extensions will need to make them compatible with Kodi 18.
If Kodi 18.1 doesn’t work properly for you and you absolutely need to use your extensions, you may use the old
kodi package in
/var/cache/pacman/pkg in order to downgrade Kodi to version 17.6. Please note that it is a temporary workaround and that the software provided in the old
kodi package may stop working properly in the future too. You should not keep the downgrade forever.
Notifications looking weird in XFCE
Since the package dunst includes now dunstfy in the main package notifications may not displayed properly in XFCE. Please uninstall that package to solve that issue. Normally not needed in that edition.
Plasma will not reboot from the Application Launcher
If you update from within Plasma (e.g. from the konsole), you may need to issue a
systemctl reboot to reboot.
I can’t open Nemo with elevated privileges (as root)
Workaround found: Use the
dbus-x11 package instead of the regular
dbus package. This package is available in the official repositories and provides dbus compiled without the
dbus-x11 package, simply install
dbus-x11 with your favorite package manager:
dbus will be replaced by
Pamac: “Failed to commit transaction - Transaction not prepared” at the end
So far, it has only been a false alarm: updates are applied successfully.
Unless you’ve already done 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 3 is optional.
Rebuilding fontconfig cache: failed to write cache
Please ignore this message. Upstream already works on a solution. More about the issue here.
LibreOffice has no window decoration in KDE
export SAL_USE_VCLPLUGIN=gtk3_kde5, once merged into existing
/etc/profile.d/libreoffice-fresh.sh , fixes a moderately longterm issue. If it doesn’t work for you, you may use
gtk instead of
gtk3_kde5 as UI framework.
Installing glibc (2.28-4) breaks the dependency “glibc=2.27” required by lib32-glibc
Install the update either:
- from terminal:
sudo pacman -Syu or;
- with Octopi instead of Pamac.
Something using Perl/Python/glibc broke
- If it’s an AUR package, try to reinstall it from AUR. It most likely needs to be rebuilt.
- If it’s a repo package, please report and check back regularly for updates.
I’ve lost a Thunderbird addon/feature
Thunderbird 60 disables incompatible addons by default. There’s an
about:config switch should you want to force-enable the addon, but many addons simply will not work with the newer Quantum-based Thunderbird.
Read more about Thunderbird 60 here: Thunderbird 60
Firefox - WebGL not working anymore
You may try the following solution:
about:config and set
libutf8proc>=2.1.1-3 update may require manual intervention
This should normally be automatically fixed via manjaro-system update.
The libutf8proc package prior to version 2.1.1-3 had an incorrect soname link. This has been fixed in 2.1.1-3, so the upgrade will need to overwrite the untracked soname link created by ldconfig. If 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 perform the upgrade.
Pamac: “Invalid or corrupted package.”
If you receive an “Invalid or corrupted package.” error message with Pamac and if the details contains an output similar to the following:
Synchronizing package databases...
Starting full system upgrade...
Loading packages files...
Checking file conflicts...
Checking available disk space...
Upgrading manjaro-system (20180702-1 -> 20180716-1)...
==> Fix libutf8proc upgrade ...
looking for conflicting packages...
Packages (1) libutf8proc-2.1.1-4
Total Download Size: 0.05 MiB
Total Installed Size: 0.32 MiB
Net Upgrade Size: 0.00 MiB
:: Proceed with installation? [Y/n]
:: Retrieving packages...
checking package integrity...
loading package files...
checking for file conflicts...
checking available disk space...
:: Processing package changes...
:: Running post-transaction hooks...
(1/1) Arming ConditionNeedsUpdate...
Running 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/files: No such file or directory
Warning: could not fully load metadata for package libutf8proc-2.1.1-2
Failed to prepare transaction:
invalid or corrupted package
Try the following steps: close Pamac window first, then launch it again and start the update procedure again. It should continue 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 able to define also the size for your panel. If you have a high-DPI display, you may want to increase the value. This will fix the display issue with given widget.
With this update we have a
/etc/pulse/default.pa.pacnew. It may be necessary to merge (some lines related to “GSettings” in
/etc/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 support for the Engrampa archive manager. engrampa-thunar-plugin is no longer needed. Remove engrampa-thunar-plugin to continue with the update.