[Stable Update] 2019-10-10 - Gnome 3.34.1, Plasma 5.16.5, KDE Apps & Framework, Pamac 9.0, Mesa 19.2.1

Hello community,

I am happy to announce another Stable Update. It took us over a month to complete this update-pack for our stable branch. We had a little struggle to get Gnome 3.34 stable enough, so we decided to polish that before we do another update to this branch. Also we managed to get Snap support into Pamac 9.0 series. You may install a new plugin for that function. As usual we also updated KDE and Budgie plus added further updates to XFCE 4.14. Enjoy the latest changes in 18.1.1-rc2 Install-Medias.

Update news

This update holds the following changes:

  • All Kernels got updated and rebuilt against the new toolchain. We dropped Kernel 5.1 series
  • Beginning with Pamac 9.0 series, we now support snaps via a plugin. We focused on fixing reported issues of this series.
  • Gnome got updated to 3.34.1. Tell us your findings!
  • Budgie got updated to work with Gnome 3.34
  • We have now KDE Plasma 5.16.5
  • KDE Apps are now at 19.08.1
  • KDE Framework is now at 5.62 and we updated most or our KDE-git packages
  • Mesa got updated to 19.2.1
  • The long waited for LibreOffice 6.3.2 update got added.
  • LibreOffice got needed security updates
  • coding environment Gambas got updated to 3.14.0
  • Firefox got fixed for crashes during playing Youtube videos
  • Some work went into Octopi. Give us some feedback if there are some improvements.
  • We are currently working on repo-compare, a new web-service.
  • Kodi is now at 18.4
  • We are currently working on repo-compare, a new web-service.
  • bauh is now at 0.6.1
  • We worked on our Gnome Themes
  • Calamares gained some fixes in regard of GeoIP
  • ZFS got updated to 0.8.2
  • Gstreamer got updated to 1.16.1
  • Bluez is now at 5.51
  • Some Browser got updated as needed
  • Thunderbird is now at 68.1.0. We pushed this also to our stable branch.
  • We managed to renew our KDE-Dev packages
  • Qt5 got bumped to 5.13.1 which brings needed fixes. Report if we still have to rebuild some packages against it.
  • The usual haskell, php and regular python updates
  • Additional regular improvements and upstream package renewals
  • Manjaro 18.1.1-rc2 got released! Please test and give us feedback: gnome, kde, xfce
  • Latest efforts by KDE can be reviewed via our current KDE-Dev ISO or current KDE-Vanilla ISO

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

Current supported Kernels

  • linux316 3.16.75
  • linux44 4.4.196 (no legacy nvidia-340 module!)
  • linux49 4.9.196
  • linux414 4.14.148
  • linux419 4.19.78
  • linux52 5.2.20 [EOL] (no catalyst module!)
  • linux53 5.3.5 (no catalyst module!)
  • linux54 5.4.0-rc2 (not all modules build yet!)
  • linux419-rt 4.19.72_rt25
  • linux52-rt 5.2.19_rt11

Package Updates (Thu Oct 10 13:58:42 CEST 2019)

  • stable community x86_64: 2099 new and 2058 removed package(s)
  • stable core x86_64: 99 new and 97 removed package(s)
  • stable extra x86_64: 1460 new and 1545 removed package(s)
  • stable multilib x86_64: 63 new and 58 removed package(s)

A detailed list of all packages 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 Stable Updates Announcements RSS feed

xfce4-terminal / xfce4-power-manager / guake does not open

Please update to kernel 4.14 or higher (4.14, 4.19, 5.2 [EOL], 5.3)

There is an issue with vte3 0.58.1-1 and upower 0.99.11-1 on kernels 4.4 and 4.9.

Replace linux51 with community/linux-latest ?

linux51 is EOL and has been removed from the repositories. It will be replaced by a metapackage which will from now on keep you on a maintained kernel.

If you want to keep the old kernel and modules then include them in your pacman.conf's IgnorePkg.

pip behaves differently

Downgrade to 19.0.3. This experiment is apparently a total failure and from the responses it's not worth trying to improve the wider ecosystem.

With the 19.2.3-1.4 package, pip now includes by default the --user flag for all operations. This will help prevent file conflicts caused by sudo pip install.

This will work correctly within any venv environment or anywhere Python's ensurepip functionality is used. It may break e.g. Conda environments.

To revert to "normal" behaviour simply edit or remove /etc/pip.conf to remove user=yes.

Pamac-Qt is not compatible to 9.0 API of Pamac


the pkgver 19.10.1 ship with an hook to remove the capability from gnome-shell. A message is present during install but essentially you need to reboot the system to show correctly the icons in the desktop. More info here


WOO HOO! Thank you Manjaro for all your hard work!


An update to jsoncpp causes polybar to fail - the solution is to re-build polybar.
This is a known issue with polybar as detailed here: https://github.com/polybar/polybar/issues/885

Everything else good here.

After such a long time I had to update my pacman mirrors :smile:

Thank you for your work

Updates went fine.
pamac now have huge icons and doesn't offer the option to ignore certain package updates anymore.

My update stuck on 36/36 Post-Transaction-Hooks
these are the latest output in pamac-manager:

==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-5.3-x86_64.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux53.preset: 'fallback'
  -> -k /boot/vmlinuz-5.3-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.3-x86_64-fallback.img -S autodetect
==> Starting build: 5.3.5-1-MANJARO
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [resume]
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-5.3-x86_64-fallback.img
==> Image generation successful
Updating Grub-Bootmenu
Generating grub configuration file ...
Found background: /usr/share/grub/background.png
Found linux image: /boot/vmlinuz-5.3-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-5.3-x86_64.img
Found initrd fallback image: /boot/initramfs-5.3-x86_64-fallback.img
Found linux image: /boot/vmlinuz-5.2-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-5.2-x86_64.img
Found initrd fallback image: /boot/initramfs-5.2-x86_64-fallback.img
Found linux image: /boot/vmlinuz-4.19-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-4.19-x86_64.img
Found initrd fallback image: /boot/initramfs-4.19-x86_64-fallback.img
Found memtest86+ image: /boot/memtest86+/memtest.bin
Reloading system bus configuration...
Warn about old perl modules
Copy Firefox Distribution Settings
Updating 32-bit fontconfig cache...
Updating fontconfig cache...
Probing 32-bit GDK-Pixbuf loader modules...
Probing GDK-Pixbuf loader modules...
Updating GIO module cache...
Compiling GSettings XML schema files...
Probing GTK3 input method modules...
Updating icon theme caches...
Reloading GVFS config...
Creating background picture sym-links for XFCE...
'/usr/share/backgrounds/xfce/breath.png' -> '/usr/share/backgrounds/breath.png'
'/usr/share/backgrounds/xfce/manjarowall17_01.jpg' -> '/usr/share/backgrounds/manjarowall17_01.jpg'
'/usr/share/backgrounds/xfce/manjarowall17_02.jpg' -> '/usr/share/backgrounds/manjarowall17_02.jpg'
'/usr/share/backgrounds/xfce/manjarowall17_03.jpg' -> '/usr/share/backgrounds/manjarowall17_03.jpg'
'/usr/share/backgrounds/xfce/manjarowall17_04.jpg' -> '/usr/share/backgrounds/manjarowall17_04.jpg'
'/usr/share/backgrounds/xfce/manjarowall17_05.jpg' -> '/usr/share/backgrounds/manjarowall17_05.jpg'
'/usr/share/backgrounds/xfce/manjarowall17_06.jpg' -> '/usr/share/backgrounds/manjarowall17_06.jpg'
'/usr/share/backgrounds/xfce/manjarowall17_07.jpg' -> '/usr/share/backgrounds/manjarowall17_07.jpg'
'/usr/share/backgrounds/xfce/manjarowall17_08.jpg' -> '/usr/share/backgrounds/manjarowall17_08.jpg'
Upgrading pip for ensurepip
Updating journal message catalog...
Reloading system manager configuration...
Updating udev hardware database...
Applying kernel sysctl settings...
Creating temporary files...
Reloading device manager configuration...
Arming ConditionNeedsUpdate...
Updating the info directory file...
Copy Thunderbird Distribution Settings
Rebuilding certificate stores...
Updating the desktop file MIME type cache...
Updating the MIME type database...
Updating X fontdir indices...

How should I safely abort and reupdate? Closing the manager does not work.
Im on xfce.

edit: I suspect it has finished the regular update properly and stuck on updating vscode from AUR (it didn't start updating though).

1 Like

Everything went fine, thanks !

We have fixed that issue when AUR was used to tell the user that the process was finished within Pamac 9.0. To make sure you may open a terminal and issue pamac upgrade before you try to reboot your system.

1 Like

Updated a big box and a small laptop via terminal emulator. No issues after restart. Thanks :up:

This is a huge update (1,95 GB), but no issue on my Desktops.

Only my Laptop dosen´t start with kernel 5.3. It needs nvidia 340. But with Kernel 5.2 it works fine.

Thanks to the Manjaro - Team :+1:


1 Like

I'm not sure it was me or obmenu generator update. Anyway, if obmenu don't want to switch from static to dynamic or vice versa probably menu-static.xml was overwritten. Copy settings from menu-static.xml.bak to menu-static.xml fix the issue :slight_smile:

Everything is working fine, no issues after the update :innocent:

@linux-aarhus Is the maintainer of polybar on Manjaro.

Had to remove \usr\share\bleachbit before update. After that, everything was OK. Thanx for update!


Yeah, there was someone who had a similar issue with BleahBit in Testing. He simply uninstalled the package, upgraded, and reinstalled the package after.

Huh, perhaps a small file conflict with the BleachBit package.

Arch Linux advises to install base package.

Issue while updating [RESOLVED]

It's been sat at this point for the last 10 minutes or so.


Left a while and it sorted its self out...

I don't know if it's just the reboot after a few days, but everything feels very snappy™. No problems so far. :+1:

Kernel 5.3, KDE edition.

1 Like

Arch Linux advises to install base package.

Should we on Manjaro Stable do that, too? What happens if we don't?

Nothing happens for now but something may happen in the future. I think we should install it as advised.

Forum kindly sponsored by