[Stable Update] 2020-03-14 - Kernels, Plasma 5.18.3, KDE Frameworks 5.67, KDE Apps 19.12.3, Firefox, Kodi

superbe! :dark_sunglasses: no issues whatsoever. can't wait testing new flatpak-pamac-plugin!

Basically everything is fine with the update. The only inconvenience is that qt applications continue to scale differently than gtk applications and i now need lxappearance to set the font size for gtk apps.
Well done!
(Kernel 5.4/ Nvidia 435/ Plasma)

Issue: font for firefox looks big on KDE.

After applying this update firefox gets a weird font size now for the titlebar and tabs. It looks really big, and I am not sure if it is event the old font previously used.

If you have more than one OSes installed, /etc/default/grub requires the value of 1 or more, for GRUB_TIMEOUT.

Otherwise it waits for 10 seconds before boot.

Another option is to write:


in /etc/default/grub.

After updating /etc/default/grub, do not forget to run:


I had to reboot the computer with "reboot" on console.

Everything else went fine.

Always reboot after updating kernels and/or vital system components like DE or system libraries.


Everything went great, although I removed gtk3-nocsd-git before updating Manjaro KDE. No clue if it's required, but there is a lot of changes to csd in newest Plasma.

pamac says:

Synchronizing package databases...
Refreshing core.db...
Refreshing extra.db...
Refreshing community.db...
Refreshing multilib.db...
Resolving dependencies...
Checking inter-conflicts...
Refreshing multilib.db...
Checking keyring...
Checking integrity...
Error: multilib.db: chromium: signature from "Evangelos Foutras <evangelos@foutrelis.com>" is invalid
Error: multilib.db: linux55: signature from "Philip Müller (Called Little) <philm@manjaro.org>" is invalid
Failed to commit transaction:
invalid or corrupted package:


Linux 5.5.7-1-MANJARO / Manjaro Gnome 19.0.2

With 5.18.3 Kwallet started to ask for root password at boot time directly after entering password in SDDM, with 5.17 and kwallet enabled this was not the case.


Systemd 244 is most likely intentional. It has been in stable-staging for days, and was included in the big update that shipped notably KDE 5.18.3 and most of everything else we are having in this update. It finally made it. (systemd 245 is still only in Unstable for now.)

As for 9.4.0rc4, well, it got added in the last minute though. I don't know if it is a good move, considering that @guinux is still actively working on this release, although I have to admit that it is miles better than the first release candidate versions we got, and in my experience, it seems to be as usable than 9.3.0. However, if it was me, I would have held it back and let guinux finalize Pamac 9.4.0 without pressure.


There is bug concerning font display in Settings GUI : Global Theme, Plasma Style and Application Style

What happens when you update with Pacman?

XFCE update goes fine! Thanks Manjaro :slight_smile:

Fwiw, is working fine for me in Arch, & in my MJ Unstable [though it does cause DMESG to no longer show during boot, unless user edits grub to remove quiet (kudos @anon96998563)].


It would not IMO be fair to blame this as a systemd 245 bug, but instead more a user self-induced problem.


Possibly related: [Stable Update] 2020-03-14 - Kernels, Plasma 5.18.3, KDE Frameworks 5.67, KDE Apps 19.12.3, Firefox, Kodi

looks like sudo pacman -Syyu went through without errors. :woman_shrugging:

'Failed to commit transaction'

Download of xfce4-clipman-plugin (1.4.4-1) started
Download of xfce4-clipman-plugin (1.4.4-1) finished
Download of vim-runtime (8.2.0343-1) finished
Checking keyring...
Checking integrity...
Loading packages files...
Checking file conflicts...
Failed to commit transaction:
conflicting files:
fwupd: /usr/bin/fwupdate already exists in filesystem
fwupd: /usr/share/man/man1/fwupdate.1.gz already exists in filesystem

Manjaro 19.0.2

I had it installed via the AUR. Just needed to remove it first and then run the update. Thanks to those that helped me realize this.

Thanks @muvori
It worked !
Update completed.

Yeah after upgrading today to 5.18.3 stable I got that problem.

The volume increased by a dramatic factor of 10. I now need to set the systems maximum volume to 10% to make it bearable.

Card pulseAudio
Chip PulseAudio
Jabra Evolve headset

Forum kindly sponsored by