[Testing Update] 2019-03-27 - Kernels, Gnome, LibreOffice, Mesa, Budgie, Browsers, Qt


Hi community,

Welcome to our nineteenth testing update for 2019. This is a refresh of our last update. So what do we have with this one?

  • we renewed most of our Kernels
  • we updated Gnome to 3.32 series
  • Budgie got updated to 10.5
  • LibreOffice got renewed to the latest
  • our graphical stack runs now with Mesa 19
  • we also bumped Qt to 5.12.2. Tell us if we need more rebuilds

We hope with all these changes Manjaro to be more efficient for you all.


Get our new T-Shirt collection #CLT2019! They are the latest design we did exclusively for Chemnitz Linux Days.

Manjaro v18.0.4 released!

We updated our flagship ISOs of Manjaro Illyria with the latest packages. It comes with refreshed packages and updated tools. You may want to download our XFCE Edition with the latest 4.13 packages, aswell as our most recent styling efforts. Our KDE fans may try our KDE Edition with the latest KDE v5.15 instead. And our GNOME fans may try our Gnome Edition with the latest GNOME v3.30.

Current supported Kernels

  • linux316 3.16.62
  • linux318 3.18.137 [EOL]
  • linux44 4.4.167 [FZN]
  • linux49 4.9.166
  • linux414 4.14.109
  • linux419 4.19.32
  • linux420 4.20.17 [EOL]
  • linux50 5.0.5
  • linux51 5.1-rc1 (no extramodules yet)
  • linux418-rt 4.18.16_rt9
  • linux419-rt 4.19.25_rt16
  • linux50-rt 5.0.3_rt1-1

Package Updates (Sat Mar 23 08:59:08 CET 2019)

  • testing community x86_64: 1241 new and 1237 removed package(s)
  • testing core x86_64: 16 new and 13 removed package(s)
  • testing extra x86_64: 526 new and 628 removed package(s)
  • testing multilib x86_64: 22 new and 20 removed package(s)

A detailed list of all package changes can be found here.

  • No issue, everything went smoothly
  • Yes there was an issue. I was able to resolve it myself.(Please post your solution)
  • Yes i am currently experiencing an issue due to the update. (Please post about it)

0 voters

Check if your mirror has already synced:


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-topicons-plus-huttli and 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.

4. Miscellaneous
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 yaourt: allservers, pacli and pacli-jwm. Those packages has been removed from the official repositories completely.

Menulibre: " UnicodeDecodeError: 'utf-8' codec can't decode byte 0xc3 in position 13: unexpected end of data" or something similar

Menulibre is currently broken and unusable for some users. For now, we don’t know what’s happening exactly. Sorry for the inconvenience. We’ll ship a more functioning version as soon as possible.

March 24, 2019: Should now be fixed with the menulibre 2.2.0-4 package.

Items from previous update sets

vlc-nightly has been dropped

The 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 vlc package.

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 --without-x option.

To replace dbus with dbus-x11 package, simply install dbus-x11 with your favorite package manager: dbus will be replaced by dbus-x11.

Pamac: “Failed to commit transaction - Transaction not prepared” at the end

So far, it has only been a false alarm: updates are applied successfully.

AMD-Ucode introduction

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
sudo update-grub

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

New line 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

Rebuilds needed!

  • 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:

Open about:config and set security.sandbox.content.read_path_whitelist to /sys/.

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...

Resolving dependencies...
Checking inter-conflicts...
Downloading manjaro-system-20180716-1-any.pkg.tar.xz...
Checking keyring...
Checking integrity...
Loading packages files...
Checking file conflicts...
Checking available disk space...
Upgrading manjaro-system (20180702-1 -> 20180716-1)...
==> Fix libutf8proc upgrade ...
resolving dependencies...
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...
downloading libutf8proc-2.1.1-4-x86_64.pkg.tar.xz...
checking keyring...
checking package integrity...
loading package files...
checking for file conflicts...
checking available disk space...
:: Processing package changes...
upgrading libutf8proc...
:: Running post-transaction hooks...
(1/1) Arming ConditionNeedsUpdate...
Running post-transaction hooks...
Arming ConditionNeedsUpdate...
Warning: lock file missing /var/lib/pacman/db.lck
Starting full system upgrade...
Resolving dependencies...
Checking inter-conflicts...
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.


Pulseaudio changes

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.


Third time lucky? :laughing:



I could not take it any more about people reporting package installation errors when trying to install them by Yaourt. hahaha


Extensions is now updated for 3.32. I have not tested it as I’m on the stable branch, I just saw the update for it today.

pacui is a good alternative to pacli.


I, for one, liked yaourt. I don’t like yay because it never asks to edit PKGBUILD so trizen is my best bet. Sometimes it’s good to have few AUR helpers to test things but in overall, yaourt still works but removal makes sense. There is no point of keeping not developed packages in repo.


Yep, I liked him too. And I agree to the part of to edit PKGBUILD. It’s helpful sometimes.


Update went fine. No apparent issues.


It works fine for me, in VM & on-SSD.


Updated from Stable to Testing via Pamac GUI. No issues to report.

@michaldybczak @FVGuilherme Try pikaurAUR. It will ask to edit the PKGBUILD when you go to install packages. The order in which it does things is based on the ability to edit all the PKGBUILDS (and answer all the confirmations and whatnot) at the beginning, and do all the building/installing (and as much of the downloading as possible) afterward.

Very well made AUR helper. If you find an issue and report it, the main author is quick to reply. The last issue I reported, he replied in less than 5 minutes, and a fix deployed the next day.

As a bonus, it can also be used to install AUR packages as root, which is useful when you need to install AUR packages when chroot’d into a system. It uses dynamic users in systemd to pull that off.



Here let me make it even easier for you. If we did not have to jump hoops I would have just made a commit on gitlab - just as easy to ignore though.

Updated PKGBUILD for vhba-module (only two lines changed ‘pkgver’ and first checksum)

# Based on the file created for Arch Linux by:
# Ray Rashif <schiv@archlinux.org>
# Mateusz Herych <heniekk@gmail.com>
# Charles Lindsay <charles@chaoslizard.org>

# Maintainer: Guinux <nuxgui@gmail.com>
# Co-Maintainer: Philip Müller <philm@manjarolinux.org>

pkgdesc="Kernel module that emulates SCSI devices"
arch=('i686' 'x86_64')

prepare() {
  cd "$srcdir/$_pkgname-$pkgver"
  patch -p0 -i "$srcdir/linux-4.11.patch"

build() {
  _kernver="$(cat /usr/lib/modules/$_extramodules/version)"
  cd "$srcdir/$_pkgname-$pkgver"
  make -j1 KDIR=/usr/lib/modules/${_kernver}/build

package() {
  cd "$srcdir/$_pkgname-$pkgver"
  install -D vhba.ko "$pkgdir/usr/lib/modules/$_extramodules/vhba.ko"

  sed -i "s/EXTRAMODULES=.*/EXTRAMODULES=$_extramodules/" \

  find "$pkgdir" -name '*.ko' -exec gzip -9 {} \;

  install -Dm644 "$srcdir/60-vhba.rules" \

Budgie community edition install on VM running well.


Edit ~/.config/yay/config.json and set “editmenu” to true.


Welcome to our Forum.

1 Like

Welcome to the Forum.

1 Like

KDE here upgraded no problem. Thanks!


Yay can also edit the config by itself with options.

yay --editmenu --nodiffmenu --answeredit All --save


No issues. Linux 4.19, Intel/Nvidia, Plasma.


It was like an automobile that the family loved for sentimental reasons. They kept it and continued to use in some cases despite the fact that the radiator was busted and it would frequently stall out while driving.


message in warning from Networkmanager
kernel 5.05 & 4.19.32

mars 28 07:32:19 mjro NetworkManager[577]: <warn>  [1553754739.5817] dns-sd-resolved[0x55575b415120]: failed to connect to resolved via DBus: Erreur lors de l’appel de StartServiceByName