[Stable Update] 2019-06-11 - Kernels, KDE Apps & Frameworks, Browsers, Nvidia, Xorg-Server, Mesa

Hello community,

I am happy to announce another Stable Update right right from the #snapcraftsummit in Montreal!

This update holds the following changes:

  • We updated some of our Kernels. Note that linux50 is now marked end of life. We recommend to move on to linux51 kernel series. Remember that linux318 now really had it's last build aswell!
  • Xorg-Server is now at 1.20.5
  • Nvidia driver got updated to 430.14
  • Gparted is now at v1.0
  • KDE Frameworks is now at 5.59.0
  • KDE Apps are now at 19.04.2
  • KDE-Git packages got added. You may check them out via our new ISOs
  • we adopted to the new matcha themes created by @cscs (see troubleshoots for more info)
  • most of our settings packages got adopted to use the new kvantum-theme-matcha package
  • i-nex we dropped. Please use cpu-x as an alternative
  • we added needed workarounds to get pamac-qt more stable when using qqc2-desktop-style
  • Palemoon is now at 28.5.2
  • Firefox got a new development and stable release
  • Mesa is now at 19.0.6
  • XFCE is now at 4.14-pre1.
  • More package updates to Deepin. Please discuss if Deepin is still useful for Manjaro
  • Calamares is now at 3.2.9. We use kpmcore3 on our ISOs to have a stable install routine
  • We updated Octopi. Report any issues you may have with it
  • The usual haskell and python package updates
  • We updated zfs modules to 0.8.0 including a resolved critical bug
  • Haskell, python and other packages got updated to their latest build

With this we also released Manjaro 18.1.0-rc1. Get the latest ISOs from OSDN: XFCE, KDE, Gnome
Give us the usual feedback and let us know what you think about this update.

Current supported Kernels

  • linux316 3.16.67

  • linux318 3.18.140 [EOL] (it is now really EOL!)

  • linux44 4.4.180 (no legacy nvidia-340 module!)

  • linux49 4.9.179

  • linux414 4.14.124

  • linux419 4.19.49

  • linux420 4.20.17 [EOL]

  • linux50 5.0.21 [EOL]

  • linux51 5.1.8

  • linux51 5.2-rc4 (few extramodules build, but not all yet!)

  • linux419-rt 4.19.37_rt20

  • linux50-rt 5.0.14_rt9

Package Updates (Mon Jun 10 07:48:10 CEST 2019)

  • stable community x86_64: 1393 new and 1342 removed package(s)
  • stable core x86_64: 36 new and 35 removed package(s)
  • stable extra x86_64: 693 new and 699 removed package(s)
  • stable multilib x86_64: 38 new and 38 removed package(s)

A detailed list of all package changes may 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

XFCE 4.14-pre1 : I do not see XFCE 4.14-pre1 in the repositories!?

You won't see explicitly 4.14-pre1 anywhere on our xfce-gtk3 packages. We follow the versioning used by upstream. Here's the list of all components that are part of XFCE 4.14-pre1.


Kvantum theme reset

If you are using the Matcha theme in kvantum you may experience a theme reset. Simply install kvantum-theme-matcha if not happend yet and select the new provided variants. Manjaro 18.1 releases will ship with the new themes by default.

Issues with Octopi

Currently several users report different issues for Octopi. So if you encounter some of them, you may switch to pamac for now: sudo pacman -Syu pamac

(Note that sudo pacman -Syu pamac will both install Pamac and upgrade all upgradable packages on your system at the same time.)

Issues with DisplayCAL

DisplayCAL - Missing python2-dbus causes failure to launch application.

Solution - Install the python2-dbus package for now. Version 3.8.2 fixes the dependency error. As and when DisplayCAL 3.8.2 reaches stable branch you can remove python2-dbus as it does not require it. Only remove python2-dbus again if you installed it specifically for DisplayCAL.

Items from previous update sets

Regression with Linux firmwares on machine running Vega GPUs.

June 2, 2019: We expect it to be fixed with linux-firmware 20190514-711d329-1.1. We downgraded the firmware related to Vega GPUs to a previous version. You should now be able to use Linux 4.19 correctly.

[Stable Update] 2019-05-26 - Kernels, XFCE 4.14-pre1, Virtualbox, LibreOffice

linux-firmware 20190514-711d329-1 introduced a regression that can make the system unbootable on systems that use a AMD Vega GPUs (for example: Vega 64, Vega 56, Vega 10) and Linux 4.19.

It is a regression that affects both Manjaro and Arch Linux. Here's some links.

Arch Linux bugtracker: https://bugs.archlinux.org/task/62666
Manjaro forum: Most recent stable branch update problem
Manjaro forum: Manjaro update prevents system booting
Manjaro forum: 'linux-firmware 20190514.711d329-1' update prevents my system booting.

If you are affected by this issue, you have essentially two choices: either use a different kernel or downgrade linux-firmware. The most preferred method is the first one since it doesn't involve keeping a package to an older version. Either way, if your system is completely unbootable (not even with a command line interface), you will need to do a chroot to repair your system. For each solution suggested below, we will suppose that you need to do a chroot; skip the chroot part if you manage to reach an usable command line interface.

For the first solution, as far as we know, it works fine on Linux 5.1 and supposedly also on Linux 5.0. Follow these steps in order to be able to install a new kernel:

  • Launch a live session with an installation medium;
  • Open a terminal;
  • Chroot your system. You may do so automatically with manjaro-chroot -a. On more complex system where manjaro-chroot may simply fail, you may have to do a manual chroot.;
  • Once you have chrooted on your system, use mhwd-kernel -i linux51 to install Linux 5.1 and all extra modules needed for your system. You may also try with Linux 5.0 (replace linux51 with linux50), although Linux 5.0 is expected to be End of Life soon.

(If you have multiple kernels installed on your machine, you may want to boot with other kernels before trying to install a new one.)

For the second one:

  • Chroot to your system from a live session;
  • Downgrade the linux-firmware package to version 20190424.4b6cf2b-1 with pacman -U /var/cache/pacman/pkg/linux-firmware-20190424.4b6cf2b-1-any.pkg.tar.xz. If the package is not available in your local cache, use pacman -U https://archive.archlinux.org/packages/l/linux-firmware/linux-firmware-20190424.4b6cf2b-1-any.pkg.tar.xz instead.

(Note that if you know how to use downgrade, you may also use downgrade.)
(Remember that downgrading a package is merely a temporary solution, do not hold the package to a previous version forever.)

signature from "Helmut Stult (schinfo) <helmut.stult@schinfo.de>" is marginal trust

Update manjaro-keyring first. For more options read this thread:

Issues with "signature is marginal trust" or "invalid or corrupted package"

replace steam-devices with community/game-devices-udev?

Yes. The package name changed. Accept the replacement.

Linux 5.1 - Which extra modules are currently missing?

As said in the announcement, while the newest Linux version has been released in this update set, not every extra modules are currently available in our official repositories. Before jumping on Linux 5.1, please verify if you do not need any of those missing extra modules on your system.

(Last verification: May 26, 2019)
The following extra modules are missing:

The following extra modules are available:

  • ACPI call (linux51-acpi_call);
  • BBSwitch (linux51-bbswitch);
  • Broadcom wireless driver (linux51-broadcom-wl);
  • Catalyst drivers (linux51-catalyst);
  • Legacy NVIDIA 340.XX drivers (linux51-nvidia-340xx);
  • Legacy NVIDIA 390.xx drivers (linux51-nvidia-390xx);
  • NDIS wrapper (linux51-ndiswrapper);
  • Current NVIDIA drivers (linux51-nvidia);
  • NVIDIA backlight (linux51-nvidiabl);
  • Realtek 8168 drivers (linux51-r8168);
  • Realtek 8732bu drivers (linux51-rtl8732bu);
  • Thinkpad SMAPI (linux51-tp_smapi);
  • SCSI emulation (linux51-vhba-module);
  • VirtualBox guest modules (linux51-virtualbox-guest-modules);
  • VirtualBox host modules (linux51-virtualbox-host-modules).

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

COMMAND-NOT-FOUND error during update/installation

During upgrade/installation the package command-not-found tries to sync its database with a mirror that seems to be currently (or permanently ?) offline, resulting in an error message

(1/1) installing command-not-found                                     [########################################] 100%
Could not download catalog file ... aborting
error: command failed to execute correctly

I (oberon) have already opened an issue upstream about the problem.

The KDE Updates Can Cause The Screenlocker To Crash

If you update from within a GUI session and use screenlock (e.g. it kicks in while the large update is being processed), it will crash the screenlocker.

To restore access, press CTRL+ALT+F2 to switch to another tty and log in with your username.

Then type in the following and press enter:

loginctl unlock-session 2

Press CTRL+ALT+F1 to switch back to a now unlocked KDE desktop.

TLP 1.2.1, .pacnew file: Merges may be needed

TLP 1.2.1 got released in [Stable Update] 2019-04-20 update set, replacing TLP 1.1. Therefore, if you have customized your configuration file for TLP (/etc/default/tlp), a .pacnew file will be created when the tlp package will be upgraded. This .pacnew file is the new default configuration file provided by the package. Your old configuration file won't be edited or replaced automatically; by default, your old configuration file will be kept as it is and you will have to merge relevant part the new configuration file manually with a text editor. Guidance can't really be more precise since each person has its own configuration.

You may use a tool such as Meld (package: meld) in order to compare your old configuration file with the .pacnew file and see the differences more easily.

If you haven't modified your configuration file for TLP, normally, you will automatically go on the new configuration file for TLP provided in the package without any manual intervention needed.

If you use the current version of TLPUI (tlpui r109.703bade-1), it may complain with the following error with some settings: "expected item missing in config file." It is most likely because some new parameters introduced with TLP 1.2.1 are not in /etc/default/tlp. To get rid of those messages, you will need to do some merges between your old configuration files and the .pacnew files and manually add all those new settings, even if you end up using the default value for those settings.

TLPUI cannot be launched

There was a bug in a previous version of TLPUI (confirmed on tlpui r89.d6363f0-1) that changed the permissions of /etc/default/tlp to 600 (rw-------). The default permissions for this file is 644 (rw-r--r--).

It is most likely that TLPUI doesn't launch because it doesn't have the right permissions for /etc/default/tlp. TLPUI must be allowed to read that file in order to launch.

First, verify if the permissions of /etc/default/tlp are set correctly. You may verify that with ls -l /etc/default/tlp in a terminal. Here's an example of how the output will look like:

$ ls -l /etc/default/tlp
-rw-r--r-- 1 root root 14238 Apr 11 15:26 /etc/default/tlp

If you have -rw------- instead of -rw-r--r--, change the permissions of that file so this file becomes readable to the group and others too. You may do so in the terminal with sudo chmod 644 /etc/default/tlp.

Once it is done, TLPUI should work properly.

"Spring cleanup" on Arch Linux: impact on Manjaro

Recently, Arch Linux did a "spring cleanup" of their Community repository (see the full discussion on the mailing list and seach for "spring"). Many package got removed from the Arch Linux official repositories and dropped to the AUR. Therefore, it means that many packages that were in our repositories because they were imported from Arch Linux got removed from our repositories too. Here's a non-exhaustive list of packages that got removed:

  • cherrytree - Hierarchical note taking application featuring rich text and syntax highlighting
  • docky - Full fledged dock application that makes opening common applications and managing windows easier and quicker
  • mate-menu - Advanced menu for MATE Panel, a fork of MintMenu (Not to be confused with mate-menus)
  • medit - GTK+ text editor
  • thermald - The Linux Thermal Daemon program from 01.org
  • wine-staging-nine has been removed / replaced with wine-nine. In case it is installed, it should be removed manually. http://archlinux.2023198.n4.nabble.com/Removing-wine-staging-nine-replaced-with-wine-nine-td4722447.html

If you want to continue to use those packages, you will have to use the AUR from now on.

You may try to do a package request in this category, but note that there is a high chance that your demand will be refused.

1 Like

All good for me: linux51+cinnamon+Intel UHD Graphics 620

i'm confused!
i'm running xfce installed by manjaro architecture, stable branch.
but xfce 4.14 is not here!?

All good for me too !
Was 439MB of download after new signature was imported.
Now My Telegram, Krita and much more are up to date.
Thanks a lot !

Just mind when will WPS get updated, but this is not yours i guess.

Well, here is the list of pkg versions ...

Just to make sure, I added the info on the wiki post.

Even myself I was like: "Huh? That's weird."

1 Like

linux52 :wink:



Vapoursynth don't work correctly after the update.
For example:

resize.Point(clip clip[, ...])
resize.Spline36(clip clip[, ...])

work incorrectly. (VapourSynth documentation)

DOWNGRADE_FROM_ALA=1 downgrade zimg

to version 2.8-1 solves this problem. (zimg)

Gnome here and everything went smoothly and I always upgrade to the latest kernel anyway and only go back if there is a problem to the latest Recommended LTS. It's an incredible OS Thanks to the Mighty Manjaro Team.


Linux 5.0 is the only one that where my touchpad works without issue. I hope the new 5.1 has patched the occassional freeze issue.

Perfect update via tty , KDE with 4.19 and Nvidia running great as usual , thank's y'all .

Great update via terminal. Thanks Philm & the team. 2 Asus multi monitor desktop production machines w/ Nvidia graphics. Plasma desktop on both.

Great work!

Great update, no problems! Thanks!

1 Like

Update mostly fine except one of my often use wine game (windows based Wolfenstein-The Old Blood)) has lost sound (not in cut scenes !!!) and stutter very badly. The other wine games seems ok. Steam games works ok too. I restore an disk image from earlier and start installing section of the update. Is it not the new wine (from 4.8 to 4.9). I install the new kernels with the new Nvidia driver. Some wine games won't start at all, so I install everything. I think we have to do that anyway as it is hard to pick what each updates need. That's the only defect so far.

  • One thing I notice is that I don't have to set "composition pipelining" on my GTX1050 card anymore to solve the forever tearing problem. I don't know which Nvidia driver has finally fix that.

Nvidia drivers got a lot better in last few months. It seems good at first, but playing 60fps videos still have tearing. So I continue to use FFCP.

No issues to report on five Manjaro KDE machines. And as always, great job team Manjaro. Greetings to Montreal.

No issues with the update! Smooth as usual. :+1:
LXQT, NVIDIA nonfree with Kernel 5.1.
XFCE, AMD free with Kernel 5.1

Perfect update here :+1:

Thanks to the Manjaro-Team :eyes:

System:    Host: hoflo Kernel: 5.1.8-1-MANJARO x86_64 bits: 64 Desktop: KDE Plasma 5.15.5 Distro: Manjaro Linux 
Machine:   Type: Desktop System: LENOVO product: 7307A1G v: ThinkCentre M58e serial: <filter> 
           Mobo: LENOVO model: N/A serial: <filter> BIOS: LENOVO v: 5HKT43AUS date: 09/07/2009 
CPU:       Topology: Dual Core model: Intel Core2 Duo E8400 bits: 64 type: MCP L2 cache: 6144 KiB 
           Speed: 1995 MHz min/max: 2003/3003 MHz Core speeds (MHz): 1: 1995 2: 1995 
Graphics:  Device-1: Intel 4 Series Integrated Graphics driver: i915 v: kernel 
           Display: x11 server: X.Org 1.20.5 driver: intel resolution: 1920x1080~60Hz 
           OpenGL: renderer: Mesa DRI Intel G41 v: 2.1 Mesa 19.0.6 
Audio:     Device-1: Intel NM10/ICH7 Family High Definition Audio driver: snd_hda_intel 
           Sound Server: ALSA v: k5.1.8-1-MANJARO 
Network:   Device-1: Marvell 88E8057 PCI-E Gigabit Ethernet driver: sky2 
           IF: ens33 state: up speed: 1000 Mbps duplex: full mac: <filter> 
Drives:    Local Storage: total: 232.89 GiB used: 15.63 GiB (6.7%) 
           ID-1: /dev/sda vendor: Samsung model: SSD 850 EVO 250GB size: 232.89 GiB 
Partition: ID-1: / size: 220.81 GiB used: 15.63 GiB (7.1%) fs: ext4 dev: /dev/sda1 
           ID-2: swap-1 size: 8.43 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda2 
Sensors:   System Temperatures: cpu: 37.0 C mobo: N/A 
           Fan Speeds (RPM): N/A 
Info:      Processes: 170 Uptime: 3m Memory: 3.82 GiB used: 1.06 GiB (27.9%) Shell: bash inxi: 3.0.34 


All well here, thank you!

System Spec

$ inxi -Fxz
Host: manjaro Kernel: 5.0.21-1-MANJARO x86_64 bits: 64 compiler: gcc
v: 8.3.0 Desktop: Xfce 4.13.4git-be04da Distro: Manjaro Linux
Type: Laptop System: Dell product: Vostro 5471 v: N/A serial:
Mobo: Dell model: 08X87Y v: A00 serial: UEFI: Dell v: 1.11.1
date: 01/29/2019
ID-1: BAT0 charge: 29.7 Wh condition: 40.7/42.0 Wh (97%)
model: BYD DELL FW8KR86 status: Discharging
Topology: Quad Core model: Intel Core i5-8250U bits: 64 type: MT MCP
arch: Kaby Lake rev: A L2 cache: 6144 KiB
flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
bogomips: 28808
Speed: 800 MHz min/max: 400/3400 MHz Core speeds (MHz): 1: 800 2: 800
3: 800 4: 800 5: 800 6: 800 7: 800 8: 800
Device-1: Intel UHD Graphics 620 vendor: Dell driver: i915 v: kernel
bus ID: 00:02.0
Display: x11 server: X.Org 1.20.5 driver: intel unloaded: modesetting
resolution: 1920x1080~60Hz
OpenGL: renderer: Mesa DRI Intel UHD Graphics 620 (Kabylake GT2)
v: 4.5 Mesa 19.0.6 direct render: Yes
Device-1: Intel Sunrise Point-LP HD Audio vendor: Dell
driver: snd_hda_intel v: kernel bus ID: 00:1f.3
Sound Server: ALSA v: k5.0.21-1-MANJARO
Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
vendor: Dell driver: r8168 v: 8.047.01-NAPI port: e000 bus ID: 01:00.0
IF: enp1s0 state: down mac:
Device-2: Intel Wireless 3165 driver: iwlwifi v: kernel port: e000
bus ID: 02:00.0
IF: wlp2s0 state: down mac:
IF-ID-1: enp0s20f0u1 state: unknown speed: N/A duplex: N/A mac:
IF-ID-2: tun0 state: unknown speed: 10 Mbps duplex: full mac: N/A
Local Storage: total: 456.46 GiB used: 58.13 GiB (12.7%)
ID-1: /dev/sda vendor: Samsung model: SSD 860 EVO 250GB size: 232.89 GiB
ID-2: /dev/sdb vendor: Western Digital model: WDS240G2G0B-00EPW0
size: 223.58 GiB
ID-1: / size: 24.48 GiB used: 10.82 GiB (44.2%) fs: ext4 dev: /dev/sda4
ID-2: /home size: 14.70 GiB used: 1.26 GiB (8.6%) fs: ext4 dev: /dev/sda5
System Temperatures: cpu: 39.0 C mobo: 36.0 C sodimm: 31.0 C
Fan Speeds (RPM): cpu: 0
Processes: 240 Uptime: 1h 59m Memory: 15.57 GiB used: 2.01 GiB (12.9%)
Init: systemd Compilers: gcc: 8.3.0 Shell: bash v: 5.0.7 inxi: 3.0.34

Forum kindly sponsored by