[Testing Update] 2019-01-19 - Kernels, Mesa, Browsers, Nvidia, Deepin, VirtualBox

Important notice

Please use pamac upgrade --enable-downgrade or sudo pacman -Syyuu for this update, to avoid issues!

Hi community,

Welcome to our third testing update of 2019. With this we added a lot of new packages into the mix. So what do we have with this one?

  • most Kernels got updated. Note that linux44 is currently frozen, as some proprietary drivers don’t build with 4.4.168+. We also removed linux417 and linux418. If you still use these series, please move on to linux419 series and uninstall them, as we won’t compile any extramodules for them from now on.
  • some updates to Cinnamon and Deepin
  • rebuilds against new readline and libidn2, therefore please keep close attention to your upgrade and report any issues on those matters
  • systemd got again downgraded to v239.6 as we got reports of graphical crashes.
  • KDE Framework is now at 5.54.0
  • Mesa is now at 18.3.2
  • Palemoon is now at 28.3.0
  • Firefox is now at its eleventh beta release of v65 series
  • Virtualbox got its first stable point-release of v6.0 series
  • Nvidia got updated to 415.27
  • the regular python and haskell updates

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


Some of our core developers will join PINE64 Inc. at FOSDEM19 in Brussels. We will establish an even more closer relationship with this ARM based company. Also we are looking forward to see your reactions on the big announcement PINE64 Inc. will do at FOSDEM19. Stay tuned for any upcoming news.

Partnership with FCS Linux Aarhus

We are happy to announce a new partnership with FCS Linux Aarhus owned by @linux-aarhus. This enables us to offer you Laptops with Manjaro pre-installed and Manjaro Stickers you can use on your own hardware or gift them to a friend. For each sale FCS will donate a percentage to the Manjaro project.

Manjaro v18.0.2 released!

To end the year with a high note 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.14 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.132 [EOL]
  • linux44 4.4.167 [FZN]
  • linux49 4.9.151
  • linux414 4.14.94
  • linux419 4.19.16
  • linux420 4.20.3
  • linux414-rt 4.14.93_rt53
  • linux416-rt 4.16.18_rt11
  • linux418-rt 4.18.16_rt9

Package Updates (Sat Jan 19 08:24:22 CET 2019)

  • testing community x86_64: 822 new and 807 removed package(s)
  • testing core x86_64: 51 new and 56 removed package(s)
  • testing extra x86_64: 401 new and 429 removed package(s)
  • testing multilib x86_64: 19 new and 14 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

“warning: systemd: local (239.3XX-X) is newer than core (239.6-4)” What do I do?

You have to downgrade at least to 239.6-4 otherwise you will have a broken system as 239.3XX-X is NOT compiled against the new libidn2 package. You can do the downgrade with pamac upgrade --enable-downgrade or sudo pacman -Syyuu.

“warning: systemd: local (240.275-1) is newer than core (239.6-4)” What do I do?

systemd packages has been downgraded again to an older version. Hence, as long as the version installed on your system will be on a higher version, you’ll receive a warning.

If you already have systemd 240.275 on your system and you have no problem with it, you can just ignore the warning and continue to use systemd 240.275. There’s no need to do any action.

If you are still interested to downgrade systemd to 239.6, you can do the downgrade with pamac upgrade --enable-downgrade or sudo pacman -Syyuu.

Need to merge configurations with pacdiff

This update brings some changes in system configuration files. Use sudo pacdiff to review and merge properly.

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.

Items from previous update sets

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.

1 Like

I see a conflict between thunar-gtk3 and nautilus:

:: Proceed with installation? [Y/n] 
(304/304) checking keys in keyring                                                  [################################################] 100%
(304/304) checking package integrity                                                [################################################] 100%
(304/304) loading package files                                                     [################################################] 100%
(304/304) checking for file conflicts                                               [################################################] 100%
error: failed to commit transaction (conflicting files)
thunar-gtk3: /usr/share/dbus-1/services/org.freedesktop.FileManager1.service exists in filesystem (owned by nautilus)
Errors occurred, no packages were upgraded.
Error installing repo packages

Any suggestion how to solve this? I want to keep XFCE in parallel to gnome.

All good here. XFCE, kernel 4.20.
“User Manager” took two minutes to stop while rebooting / shutting down after the update, but seems ok after another reboot now.

1 Like

Something like 450-460 Mb. No problems at all. Only “bad point”: I had to wait 2 minutes before my PC reboot. Related to some user migration going on?

Seems to be related to systemd 240.xxx, I had the same behaviour on my Archlinux powered desktop PC.

Please decide which filemanager should support the freedesktop service. Each filemanager is now having this file for compatibility reasons. Also you normally have only one filemanager installed on your system. More about it here and here.

Yes. This is what I did. I removed thunar. And that removes the file
/usr/share/dbus-1/services/org.freedesktop.FileManager1.service without notice. And this was my nautilus file. So I had to reinstall nautilus to get it back.

I probably need to explain that: In order to allow the update to run through I created a backup of the file and then removed the original. Then the update installed thunar-gtk3. I subsequently restored the nautilus relate file /usr/share/dbus-1/services/org.freedesktop.FileManager1.service from the backup. So now removing thunar-gtk3 removed the nautilus file.

Other than that the update went well: linux414+nvidia+gnome+zfs

Systemd messages on boot.

Jan 19 18:47:29 xmg systemd[3063]: Stopping D-Bus User Message Bus...
Jan 19 18:47:29 xmg systemd[3063]: Stopped target Default.
Jan 19 18:47:29 xmg systemd[3063]: dbus.service: Succeeded.
Jan 19 18:47:29 xmg systemd[3063]: Stopped D-Bus User Message Bus.
Jan 19 18:47:29 xmg systemd[3063]: Stopped target Basic System.
Jan 19 18:47:29 xmg systemd[3063]: Stopped target Sockets.
Jan 19 18:47:29 xmg systemd[3063]: gpg-agent-extra.socket: Succeeded.
Jan 19 18:47:29 xmg systemd[3063]: Closed GnuPG cryptographic agent and passphrase cache (restricted).
Jan 19 18:47:29 xmg systemd[3063]: p11-kit-server.socket: Succeeded.
Jan 19 18:47:29 xmg systemd[3063]: Closed p11-kit server.
Jan 19 18:47:29 xmg systemd[3063]: gpg-agent-browser.socket: Succeeded.
Jan 19 18:47:29 xmg systemd[3063]: Closed GnuPG cryptographic agent and passphrase cache (access for web browsers).
Jan 19 18:47:29 xmg systemd[3063]: gpg-agent-ssh.socket: Succeeded.
Jan 19 18:47:29 xmg systemd[3063]: Closed GnuPG cryptographic agent (ssh-agent emulation).
Jan 19 18:47:29 xmg systemd[3063]: dirmngr.socket: Succeeded.
Jan 19 18:47:29 xmg systemd[3063]: Closed GnuPG network certificate management daemon.
Jan 19 18:47:29 xmg systemd[3063]: gpg-agent.socket: Succeeded.
Jan 19 18:47:29 xmg systemd[3063]: Closed GnuPG cryptographic agent and passphrase cache.
Jan 19 18:47:29 xmg systemd[3063]: pulseaudio.socket: Succeeded.
Jan 19 18:47:29 xmg systemd[3063]: Closed Sound System.
Jan 19 18:47:29 xmg systemd[3063]: Stopped target Paths.
Jan 19 18:47:29 xmg systemd[3063]: Stopped target Timers.
Jan 19 18:47:29 xmg systemd[3063]: dbus.socket: Succeeded.
Jan 19 18:47:29 xmg systemd[3063]: Closed D-Bus User Message Bus Socket.
Jan 19 18:47:29 xmg systemd[3063]: Reached target Shutdown.
Jan 19 18:47:29 xmg systemd[3063]: systemd-exit.service: Succeeded.
Jan 19 18:47:29 xmg systemd[3063]: Started Exit the Session.
Jan 19 18:47:29 xmg systemd[3063]: Reached target Exit the Session.
Jan 19 18:47:29 xmg systemd[3064]: pam_unix(systemd-user:session): session closed for user sddm

For those cautious users amongst us, I would recommend a tty update due to …

systemd  239.6-2 -> 240.275-1


Big KDE update 244 packages, 1.1 GB download.

1 Like

That happens because some process won’t terminate gracefully.

No issues apart the 2 minutes waiting for reboot. Updated on 2 machines with the console, KDE edition.

Evrything is ok on 2 machines.
The 2mn are “A stop job is running for user…”

1 Like

I update using “systemctl isolate multi-user.target” as @torvic stated to be more efficient:

Everything went fine, although there are some messages about “mariadb”

1 Like

All is well on my computer, thanks.
OS: Manjaro 18.0.2 Illyria
Kernel: x86_64 Linux 4.20.3-1-MANJARO
Uptime: 9m
Packages: 1114
Shell: bash 5.0.0
Resolution: 1920x1080
DE: Xfce4
WM: Xfwm4
WM Theme: Agua
GTK Theme: Clearlooks [GTK2]
Icon Theme: gnome
Font: Noto Sans 11
CPU: Intel Core i5-4460 @ 4x 3.4GHz [44.0°C]
GPU: GeForce GT 720
RAM: 762MiB / 7908MiB

Thanks for the advice. I dropped to the TTY (Ctrl Alt F4, without logging off first, as that appeared to disable my WiFi) and had a smooth update.

Just as on unstable almost a month-ago, I had a one-time delay in re-booting:

A stop job is running for User Manager for UID 1000 (count-up timer / 2min 5s)

I updated on a cinnamon session (not on tty), cinnamon suddenly stopped working and went into fallback mode. It now always boots on fallback mode. When i try to use pacman on tty:

pacman: error loading shared libraries: libidn2.so.0: cannot open shared object file: No suck file or directory

I have chosen to remove nautilus instead.

Then, shouldn’t thunar-gtk3 and nautilus “conflict” in package info?

And this issue should go to “Known Issues post”, but is it enough to say “Keep one of the two”? Any more comments are appreciated @philm

yes but you can rename this file in your thunar-gtk3 PKGBUILD ?
with dolphin we have the same (but only one will be used ?):

cat /usr/share/dbus-1/services/org.kde.dolphin.FileManager1.service                                           HPmachine  Arch  95 61 
[D-BUS Service]
Exec=/usr/bin/dolphin --daemon


There was no libidn2.so.0 in /usr/lib/ but there was a libidn2.so file, so i cp libidn2.so libidn2.so.0 and could use pacman again.

However, i had some keyring issues and couldn’t install anything. When trying to fix/update pacman keyring i got another missing library: libreadline.so.7.

Here i’ve reinstalled libreadline and libidn2 through pacman cache

I had libreadline.so.8.0 in /usr/lib/ directory, so after cp libreadline.so.8.0 libreadline.so.7 i could update the pgp keys and use pacman to update the system.

I think it was not the correct way to solve this (the ideal would get the actual files and put in /usr/lib/ (not renaming other files)) but everything is working fine now.

I don’t know if it’s possible but would be cool if on dangerous updates like this it happened like on fedora: downloads the update and installs it on next reboot (outside any GUI).

1 Like

I did the CTRL-ALT-F4 then systemctl isolate mutli-user.target thing and so far, no issues.

  Host: jpk-desktop Kernel: 4.19.16-1-MANJARO x86_64 bits: 64 compiler: gcc                                                         
  v: 8.2.1 Desktop: Gnome 3.30.2 Distro: Manjaro Linux                                                                              
  Type: Desktop Mobo: ASUSTeK model: ROG STRIX B450-I GAMING v: Rev 1.xx                                                            
  serial: <filter> UEFI: American Megatrends v: 1103 date: 11/16/2018                                                                                                                                            
  Topology: Quad Core model: AMD Ryzen 5 2400G with Radeon Vega Graphics                                                           
  bits: 64 type: MT MCP arch: Zen L2 cache: 2048 KiB
  flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
  bogomips: 57512
  Speed: 1423 MHz min/max: 1600/3600 MHz Core speeds (MHz): 1: 1522 2: 1472                                                        
  3: 1446 4: 1466 5: 1420 6: 1422 7: 1370 8: 1420
  Device-1: AMD Ellesmere [Radeon RX 470/480/570/570X/580/580X]
  vendor: Micro-Star MSI driver: amdgpu v: kernel bus ID: 01:00.0
  Display: x11 server: X.org 1.20.3 driver: amdgpu
  resolution: <xdpyinfo missing>
  OpenGL: renderer: Radeon RX 580 Series (POLARIS10 DRM 3.27.0
  4.19.16-1-MANJARO LLVM 7.0.1)
  v: 4.5 Mesa 18.3.2 direct render: Yes
  Device-1: AMD Ellesmere [Radeon RX 580] vendor: Micro-Star MSI
  driver: snd_hda_intel v: kernel bus ID: 01:00.1
  Device-2: AMD vendor: ASUSTeK driver: snd_hda_intel v: kernel
  bus ID: 06:00.6
  Sound Server: ALSA v: k4.19.16-1-MANJARO
  Device-1: Intel I211 Gigabit Network vendor: ASUSTeK driver: igb
  v: 5.4.0-k port: d000 bus ID: 04:00.0
  IF: enp4s0 state: up speed: 1000 Mbps duplex: full mac: <filter>

Forum kindly sponsored by Bytemark