[Stable Update] 2020-08-28 - Kernels, Systemd, PAM, PAMBASE, KDE-git, Deepin, Pamac, Nvidia 450.66, LibreOffice 7.0

Hello community,

Another stable branch update with some interesting updates for you!

Checkout our latest Merch#stayhome, #staysafe, #stayhealthy

  • LibreOffice got renewed to the latest releases: 6.4.6; 7.0.0
  • All our Kernels got updated
  • Systemd is at 246.2
  • pam and pambase got updated. This might need manual intervention from your end. See Troubleshoot guidelines!
  • We updated more of our KDE-git packages
  • Deepin pushed some newer packages
  • Pamac has some fixes added
  • Nvidia driver series had another update: 450.66
  • Mate got it’s first point-release in 1.24 series
  • gcc10 got updated to 10.2 and all Kernels got compiled against it
  • Usual Python and Haskell package updates and rebuilds

If you like following latest Plasma development you may also like to check out our current version of manjaro-kde-dev, which we build on a regular basis against kde-git master packages. Also check out our latest RC of Manjaro Mikah 20.1! XFCE, KDE and Gnome

Our current supported kernels

  • linux44 4.4.233
  • linux49 4.9.233
  • linux414 4.14.194
  • linux419 4.19.141
  • linux54 5.4.60
  • linux57 5.7.17
  • linux58 5.8.3
  • linux54-rt 5.4.59_rt36
  • linux56-rt 5.6.19_rt12

Package Changes (Sun Aug 23 17:42:12 CEST 2020)

  • stable community x86_64: 1136 new and 1124 removed package(s)
  • stable core x86_64: 66 new and 64 removed package(s)
  • stable extra x86_64: 454 new and 439 removed package(s)
  • stable multilib x86_64: 19 new and 19 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 Stable Updates Announcements RSS feed

dunst: /usr/bin/dunstify exists in filesystem (owned by dunstify)

dunstify has been depreciated for dunst. Uninstall dunstify before updating or update by:

sudo pacman -Syyu --overwrite /usr/bin/dunstify

PAM and PAMBASE got updated, which might prevent you from login

Due to updates from pambase and pam you might take care about any .pacnew files in /etc/pam.d as for example pam_tally, pam_tally2 and pam_cracklib got deprecated. Read in the ArchWiki about managing those files.

Typical issue:

For recovery, it is enough to boot with kernel option “systemd.unit=rescue.target”, then proceed into /etc/pam.d and merge “system-auth” and “system-auth.pacnew”

If you have however issues with pam or/and pambase please open a new thread in our dedicated support section.

Older Issues

System takes a long time to boot

If you’ve got errors like Failed to start Network Manager Wait Online. you can try removing systemd from passwd and group in /etc/nsswitch.conf as described here
Update: If you can see the line
dbus-daemon[1453]: [system] Connection has not authenticated soon enough, closing it (auth_timeout=30000ms, elapsed: 45146ms)
in in your dbus log ( journalctl -b -u dbus ), the new/better workaround is to switch cups from service to socket as described here:
systemctl disable org.cups.cupsd.service
systemctl enable org.cups.cupsd.socket

I think I’ve some font problems

With the update of fontconfig some major rules how fonts get applied changed. Make sure that your system has ttf-dejavu installed. A more in depth explanation can be found here.

Gnome-shell-extension-pop-shell is currently incompatible with wayland

… and causes the system to freeze when the first window is tiled and can render it unbootable. Solution is a hard reset and disabling either pop shell or wayland. If the system becomes unbootable, use a live USB to edit /etc/gdm/custom.conf to disable wayland and reboot.


Unable to update:
errore: impossibile eseguire l’operazione richiesta (file in conflitto)
dunst: /usr/bin/dunstify è già presente nel filesystem (appartiene a dunstify)
Si sono verificati degli errori, nessun pacchetto è stato aggiornato.

English translation:
error: unable to execute requested operation (file conflict)
dunst: /usr/bin/dunstify already present in filesystem (belongs to dunstify)
Errors occurred, no package have been updated.

I guess you need to remove it and then proceed with the update

Do i need to remove dunst or donstify?

dunst is marked as dependency for dunstify.

Thank you for your help!

remover or rename dunstify. Or use --overwrite /usr/bin/dunstify when you update.


No issues. Kernel 5.8, Cinnamon DE, AMD video.

A small issue:
had to reboot the computer via console.

I’m still not able to pull the update. maybe something wrong with my mirrors, but usually it takes only a few minutes.

edit: Never mind. Checked the mirror list, apparently some I use are no longer reachable, which is strange because I selected them only about 2 weeks ago. A never mind, updating now, looking forward to it!

no issues here, didnt need to intervene with pom or pombase


Same issue as some people here : dunstify error message. I removed dunstify and dunst. Upgrade. And then reinstall dunst. All is ok now.

A post was split to a new topic: Rtl8821ce: Bad return status for module build on kernel: 5.8.3-2

(92/92) Prüfe auf Dateikonflikte [########################] 100%
Fehler: Konnte den Vorgang nicht durchführen (In Konflikt stehende Dateien)
dunst: /usr/bin/dunstify existiert im Dateisystem (gehört zu dunstify)
Fehler sind aufgetreten, keine Pakete wurden aktualisiert.

Next time when posting CLI output, add export LANG=C before you run a command.
From that point onwards until you close the terminal, its output will be in English.

Kein Problem: Ich verstehe Deutsch…

And here is your solution (someone already mentioned this above):



Hi, in my particular issue, the affected files were:


The last one contains the same that the first, but without lines with pam_tally and pam_tally2

Use the pacnew version was enough to login again on reboot

Thanks in advance!


Same here, update went ok, nothing about pom or pombase.
Rebooted and logged in, no problem

Thanks Manjaro Team.

Is the release of the final version of Manjaro 20.1 near ?

pam not good for me before install with 2 manjaro:

$grep -E "pam_tally|pam_cracklib" /etc/pam.d/*
/etc/pam.d/lightdm-autologin:auth        required    pam_tally.so file=/var/log/faillog onerr=succeed
/etc/pam.d/passwd:#password     required        pam_cracklib.so difok=2 minlen=8 dcredit=2 ocredit=2 retry=3
/etc/pam.d/system-login:auth       required   pam_tally2.so        onerr=succeed file=/var/log/tallylog
/etc/pam.d/system-login:account    required   pam_tally2.so 
grep -E "pam_tally|pam_cracklib" /etc/pam.d/*
/etc/pam.d/passwd:#password     required        pam_cracklib.so difok=2 minlen=8 dcredit=2 ocredit=2 retry=3
/etc/pam.d/sddm-autologin:auth        required    pam_tally.so file=/var/log/faillog onerr=succeed
/etc/pam.d/system-login:auth       required   pam_tally2.so        onerr=succeed file=/var/log/tallylog
/etc/pam.d/system-login:account    required   pam_tally2.so 

now all commented before update, I can run

and after merge .pacnew if exists / replace pam_tally2.so by pam_faillock.so

EDIT: no merge /etc/shadow or /etc/passwd !!! manjaro is break


I had the same issue with dunst (/usr/bin/dunstify) and I’ve overwritten it like @chomsky suggested:

sudo pacman -Syu --overwrite /usr/bin/dunstify

Everything else was updated without issues :slight_smile:

Thank you :slight_smile:


I used to have problems with mirrors just about every time I updated. Now I run sudo pacman-mirrors --fasttrack before updating. No problems since. :fireworks: