[Testing Update] 2019-05-13 - Linux52, KDE Apps, Haskell, Gnome Extensions

Hello community,

I am happy to announce another Testing Update!

This update holds the following changes:

  • We added linux52 in its current git snapshot. Few extramodules build, but not all yet!
  • Some Gnome-Extensions got updated
  • KDE Apps is now at 19.04.1
  • For all using Haskell, you find now the latest updates in our repos.

Give us the usual feedback and let us know what you think about this update.

Current supported Kernels

  • linux316 3.16.65
  • linux318 3.18.139 [EOL]
  • linux44 4.4.179 (no legacy nvidia-340 module!)
  • linux49 4.9.175
  • linux414 4.14.118
  • linux419 4.19.42
  • linux420 4.20.17 [EOL]
  • linux50 5.0.15
  • linux51 5.1.1 (few extramodules build, but not all yet!)
  • linux51 5.2-rc0 (few extramodules build, but not all yet!)
  • linux419-rt 4.19.37_rt19
  • linux50-rt 5.0.14_rt9

Package Updates (Mon May 13 07:10:18 CEST 2019)

  • testing community x86_64: 435 new and 435 removed package(s)
  • testing core x86_64: 5 new and 3 removed package(s)
  • testing extra x86_64: 239 new and 230 removed package(s)
  • testing multilib x86_64: 3 new and 3 removed package(s)

The full list of 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

Small cleanup of Manjaro official repositories

Please note that the following packages got removed from our repositories.

  • chromium-chromevox
  • gimp-gtk3
  • pamac-classic
  • pamac-dev
  • pamac-dev-tray-appindicator

Items from previous update sets

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.

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.

No Sound:
Please edit at the Loudspeaker / Configuration tab, your analog or digital sounddriver. Currently it will not be saved until the next boot, so one has to edit the Configuration tab again.

All good here and i just wanted to say that the kernel 5.2 (even tho is rc) doesn't present the old nag i had when connecting the tablet to have a simultaneous connect/disconnect event (making the tablet unusable unless restarted again). Now all works as supposed. Beautiful job!!! Thanks! :slight_smile:

Again, thank you all for your work.
Will test this when done switching back to Gnome tonight...

No problems updating KDE edition on 3 different hardware. Thank !

you run manjaro on a tablet!?

I use a Cintiq22HD (Pen Dysplay) that is connected to my PC. Is working like a Display/Stylus/Tablet. Before i had for test also an Intuos3, Intuos5 and a Bamboo Fun that are only Stylus/Tablet + have some Touchpad like functions.
Never tested Wacom pen computers (that come with Windows preinstalled, and other models with Android), but from what i gathered, if another OS is installed on them the warranty becomes void.

1 Like

High pace recently :slight_smile:

No issues as usual, switched to kernel 5.1 with this update as well.
Kernel 5.1.1-2, KDE, btrfs, luks, nVidia 418.74, Virtualbox

1 Like

All OK here (that includes the 11th May update) on three computers (KDE, Lxde) and a virtual machine (Xfce), all of them running 4.19.

After installing this update, starting docker sudo systemctl start docker, docker-compose produces the following:

λ docker-compose ps
/usr/lib/python3.7/site-packages/requests/__init__.py:91: RequestsDependencyWarning: urllib3 (1.25.2) or chardet (3.0.4) doesn't match a supported version!
λ docker-compose stop phpmyadmin
/usr/lib/python3.7/site-packages/requests/__init__.py:91: RequestsDependencyWarning: urllib3 (1.25.2) or chardet (3.0.4) doesn't match a supported version!
Stopping phpmyadmin ... done

AFAICT the commands are functional.

Update without problem.
LXQT with Kernel 5.1.

So far so good

journalctl -p 4 -b -0

May 13 12:06:32  systemd-vconsole-setup[339]: KD_FONT_OP_GET failed while trying to get the font metadata: Function not implemented
May 13 12:06:32  systemd-vconsole-setup[339]: Fonts will not be copied to remaining consoles
May 13 12:06:32  systemd-vconsole-setup[340]: KD_FONT_OP_GET failed while trying to get the font metadata: Function not implemented
May 13 12:06:32  systemd-vconsole-setup[340]: Fonts will not be copied to remaining consoles
May 13 12:06:32  kernel: nouveau 0000:08:00.0: bios: OOB 1 d7500086 d7500086
May 13 12:06:32  systemd-udevd[306]: Process '/usr/bin/alsactl restore 0' failed with exit code 99.
May 13 12:06:32  systemd-udevd[301]: Process '/usr/bin/alsactl restore 1' failed with exit code 99.
May 13 12:06:37  kernel: kauditd_printk_skb: 5 callbacks suppressed
May 13 12:06:43  colord[430]: failed to get session [pid 405]: Keine Daten verf<C3><BC>gbar
May 13 12:06:43  colord[430]: failed to get session [pid 405]: Keine Daten verf<C3><BC>gbar
May 13 12:06:52  lightdm[607]: gkr-pam: no password is available for user
May 13 12:07:00  colord-sane[452]: io/hpmud/pp.c 627: unable to read device-id ret=-1

Does it show your desktop just like a normal monitor and you can use it as a monitor with touch abilities?

Yes, it acts like a monitor. My model has no touch as i chose that model, but there is the Cintiq22HD Touch too (plus there are the newer models 24HD and 27HD, and even newer models from the PRO line that is 32 inch + touch that is an entire beast by itself - a $3300 computer pen/touch/display.
I preferred so because for me just the Stylus was important (can be mapped to an area, entire screen in absolute or relative mode, can be mapped to the secondary display or both in the same time), and i use the buttons that come integrated with custom actions/shortcuts depending what i'm working on.

1 Like

Did it get downgraded in repos intentionally?

Warning: pamac-common: local (7.3.5-5) is newer than extra (7.3.5-4)
Warning: pamac-gtk: local (7.3.5-5) is newer than extra (7.3.5-4)

I thought I was alone in this, but I received the same warning as Frog when updating this morning.

We have to check. Currently we are updating to 7.4.0.


No issue so far on KDE but as usual ran the upgrade on a tty.

Activities, KDE/Plasma and Vivaldi
With this update if a Vivaldi window is open on the default activity and then you switch to a different activity the Vivaldi window follows the switch and is still open in the new activity. Neither Chromium nor Firefox do this.

Vivaldi	2.5.1525.40
KDE Plasma Version: 5.15.5
KDE Frameworks Version:5.57.0
Qt Version: 5.12.3
Kernel Version: 4.19.42-1-MANJARO and 4.14.118-1-MANJARO

I thought this might have something to do with Latte Dock, but I unpinned Vivaldi from the default activity and it still happens. I also downgraded Vivaldi to Vivaldi 2.4.1488.38 and it still happens.

Sorry for posting here, I just want to say that today I had a bunch of packages in Unstable branch and everything seems to be OK.

1 Like