[Testing Update] 2021-06-16 - Kernels, Alsa, Cinnamon, Deepin, Pamac, Plasma, KDE Gear, Frameworks, Browser. LibreOffice

Hello community,

Another testing branch update with some usual updates for you.

This update is all about KDE Software

  • Most of our Kernels got updated
  • KDE Plasma got updated to 5.22.1
  • KDE Gear is at 21.04.2
  • And KDE Frameworks got renewed to 5.83.0
  • We updated Pamac to work with Pacman 6.0
  • ALSA got needed updates to work better with Pipewire
  • LibreOffice is now at 7.1.4
  • Some of our Browsers got updated
  • Cinnamon going to get updated to 5.0.0
  • Deepin got some new updates
  • Other regular upstream updates including python and haskell

Get our latest daily developer images now from Github: Plasma, Gnome, XFCE. You get the latest stable releases of Manjaro from CDN77.

Our current supported kernels

  • linux44 4.4.272
  • linux49 4.9.272
  • linux414 4.14.236
  • linux419 4.19.194
  • linux54 5.4.125
  • linux510 5.10.43
  • linux511 5.11.22 [EOL]
  • linux512 5.12.10
  • linux513 5.13-rc6
  • linux510-rt 5.10.35_rt39
  • linux511-rt 5.11.4_rt11

Package Updates (Wed Jun 16 09:55:33 CEST 2021)

  • testing community x86_64: 1348 new and 1345 removed package(s)
  • testing core x86_64: 47 new and 47 removed package(s)
  • testing extra x86_64: 742 new and 841 removed package(s)
  • testing kde-unstable x86_64: 261 new and 259 removed package(s)
  • testing multilib x86_64: 14 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

New issues:

  • Compiz packages like compiz-easy-patch got dropped from our repositories. Due to protobuf update you may need to rebuild that package locally on your end. Compiz-easy-patch removed from repos

  • Some Nvidia cards don’t work with the current 465.31 drivers when used with Display Port and/or 4k Monitors. More about the issue at the Nvidia Developer Forum. We recommend to switch to Nouveau driver as needed. If you however need the Nvidia driver, you can get the PKGBUILDs of the 460.73.01 version and build your driver locally with makepkg or use the pre-compiled packages: nvida-utils, dkms and lib32 + precompiled .

Older Issues

  • OS prober does not run and add other operating systems

    Please click the ► at the beginning of this line to view this solution

    To restore, please execute: echo GRUB_DISABLE_OS_PROBER=false|sudo tee -a /etc/default/grub && sudo update-grub

    For more information, see opening post in [Stable Update] 2021-03-08.

Nvidia card owners

  • We simplified nVidia driver installation. This means we dropped legacy drivers.
    • We recommend to switch over to Nouveau drivers if your card is mentioned here and the feature you need is not in red TO DO here for your particular card.

    • If you however still need proprietary drivers, you may want to execute the following to ensure all parts of the nVidia drivers get installed properly:

      sudo mhwd -a pci nonfree 0300
      If proprietary drivers don't fix everything, please click the ► at the beginning of this line to view more info
      1. try installing kernel 5.4 LTS (Long Term Support)
      2. If that doesn’t fix it, take a full system backup, go to a console using Ctrl+Alt+F2 and:
      • Backup /etc/X11/mhwd.d/nvidia.conf if you ever edited that manually

      • remove all nVidia related drivers and applications:

        pacman --remove nvidia*
      • Note which applications are being removed and keep them handy in a list

      • Install the driver first:

        mhwd --install video-hybrid-XXX-nvidia-prime

        (Where XXX is amd or intel if you have hybrid graphics or the whole thing is video-nvidia if you’re on an nVidia-only system)

      • reboot and see if you at least get a screen.

      • Install all the other applications from your handy list that you still need one by one.

      • Restore /etc/X11/mhwd.d/nvidia.conf if you ever edited that manually

      • If that wouldn’t solve the issue open a new issue here referring to this update and posting at a minimum the full output of:

        inxi --admin --verbosity=7 --filter --no-host --width

      If you however still have issues with your Nvidia card, you may open a new thread in our forum: https://forum.manjaro.org/c/support/Graphic-Cards/33 or look at our tutorial on compiling old Nvidia drivers.

For AMD GPU users having a black screen with kernel 5.10

Please click the ► at the beginning of this line to view more info

Due to a bug in the AMD drivers, please try the following first:


  1. Open a terminal or a TTY
  2. Open /etc/default/grub in your favourite CLI editor (nano vi, emacs`)
  3. Find the line: GRUB_CMDLINE_LINUX_DEFAULT="
  4. Add amdgpu.dc=0
  5. Save
  6. Execute sudo update-grub and reboot

For systemd-boot:

  1. Open a terminal or a TTY
  2. Open /boot/loader/entries/manjarolinux5.10.conf in your favourite CLI editor (nano vi, emacs`)
  3. Add amdgpu.dc=0 to the end of the line options
  4. Save & reboot

For rEFInd:

  1. Open a terminal or a TTY
  2. Open /boot/refind_linux.conf in your favourite CLI editor (nano vi, emacs`)
  3. Find the line: "Boot using default options" "root=
  4. Add amdgpu.dc=0
  5. Save & reboot

Possible 2 Min delay on shutdown with Gnome

Please click the ► at the beginning of this line to view more info
  • If you got the problem with shutdown delay (about 2min) on Gnome, here is a workaround:
    • Edit /usr/lib/systemd/user/gnome-session-restart-dbus.service in your favourite editor as root and add Slice=-.slice as a line all by itself like this:

      ExecStart=/usr/lib/gnome-session-ctl --restart-dbus
    • Click this link For more information

Touchpad on a ThinkPad stops working

  • Restart again, please.

You get [PKGNAME] warning: directory permissions differ on [Directory name]

followed by:

Filesystem: NNN package MMM

Please click the ► at the beginning of this line to view this solution
  • The solution:

    sudo chmod MMM DirectoryName

Where obviously MMM is the second number you see (the correct one)

  • The explanation:
    Your package expects the security permissions to be MMM but your system is set to NNN. This is just a warning (today) but to ensure you remain up-to-date with the latest and greatest security rules it’s advised to execute the above command.

Systemd error message: .slice: Failed to migrate controller cgroups

If you have a similar error message like this:

systemd[1004]: -.slice: Failed to migrate controller cgroups from /user.slice/user-1000.slice/user@1000.service, ignoring: Permission denied

… you may need to add this Grub parameter to your /etc/default/grub file in line GRUB_CMDLINE_LINUX_DEFAULT: systemd.unified_cgroup_hierarchy=true. To update your grub menu, call: sudo update-grub. For more information on that issue, see also Arch Forum.

Python 3.9 Requires Rebuilds

Instructions for quickly and easily rebuilding affected AUR packages:

# Install yay
sudo pacman -S --needed --noconfirm yay

# Rebuild AUR python packages
yay -S --noconfirm $(pacman -Qqo "/usr/lib/python3.8/site-packages")

libtraceevent>=5.9-1 update requires manual intervention

2020-10-23 - Sébastien Luttringer

The libtraceevent package prior to version 5.9-1 was missing a soname link. This has been fixed in 5.9-1, so the upgrade will need to overwrite the untracked files created by ldconfig. If you get any of these errors

libtraceevent: /usr/lib/libtraceevent.so.1 exists in filesystem

when updating, use

pacman -Syu --overwrite /usr/lib/libtraceevent.so.1

to perform the upgrade.


OpenVPN connection times out.

Workaround: donwgrade openvpn (2.5.0-1 => 2.4.9-2).
For a proper solution follow this bug report on Arch Linux: FS#68480 : [openvpn] running unprivileged with iproute no longer working

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”

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 cups.service
systemctl enable cups.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.

Please RTFT (Read This Fine Thread) first before reporting the same issues over and over again!

Finally Pacman v6 with parallel downloads! You have to merge the /etc/pacman.conf.pacnew carefully.

1 Like

Yep, it’s beautiful. However, SigLevel = PackageRequired no longer needed?

I don’t know the security implications fully but the 404s of the db’s sig files are gone.

3 new orphans:
asciidoc - no longer required by mkinitcpio
vte3 - because pamac-common was removed.

I removed both, and then vte-common as well.


Unless you have Timeshift installed.


I think the SigLevel = Required DatabaseOptional in the [options] section makes the four occurences of SigLevel = PackageRequired in the repository sections superfluous.

So I removed them.

anyone who uses a pac* chaser should be aware of


One thing to also note is that plasma-systemmonitor is now disconnected from ksysguard so one could remove the latter. I think that was asked before.

1 Like

EDIT: Noticed additional package updates pushed to testing. Reverted to snapshot and retested - no more issue. Thank you

Original problem report

Ran into the following:


$ sudo pamac update
[sudo] password for user: 
Synchronizing package databases...
Resolving dependencies...
Warning: cannot resolve "libalpm.so>=13", a dependency of "libpamac"
Warning: cannot resolve "libpamac>=11.0", a dependency of "pamac-cli"
Warning: cannot resolve "libalpm.so>=13", a dependency of "libpamac"
Warning: cannot resolve "libalpm.so>=13", a dependency of "libpamac"
Warning: cannot resolve "libpamac>=11.0", a dependency of "pamac-cli"
Warning: cannot resolve "pamac-cli=10.1.3-3", a dependency of "pamac-gtk"
Warning: cannot resolve "libalpm.so>=13", a dependency of "libpamac"
Warning: cannot resolve "libpamac>=11.0", a dependency of "pamac-gtk"
Error: Failed to prepare transaction:
could not satisfy dependencies:
- unable to satisfy dependency 'libalpm.so>=13' required by libpamac
- unable to satisfy dependency 'libpamac>=11.0' required by pamac-cli
- unable to satisfy dependency 'pamac-cli=10.1.3-3' required by pamac-gtk


$ sudo pacman -Syu
:: Synchronizing package databases...
 core is up to date
 extra is up to date
 community is up to date
 multilib is up to date
:: Starting full system upgrade...
:: Replace pamac-common with extra/libpamac? [Y/n] y
resolving dependencies...
warning: cannot resolve "libalpm.so>=13", a dependency of "libpamac"
warning: cannot resolve "libpamac>=11.0", a dependency of "pamac-cli"
warning: cannot resolve "libalpm.so>=13", a dependency of "libpamac"
warning: cannot resolve "libalpm.so>=13", a dependency of "libpamac"
warning: cannot resolve "libpamac>=11.0", a dependency of "pamac-cli"
warning: cannot resolve "pamac-cli=10.1.3-3", a dependency of "pamac-gtk"
warning: cannot resolve "libalpm.so>=13", a dependency of "libpamac"
warning: cannot resolve "libpamac>=11.0", a dependency of "pamac-gtk"
:: The following packages cannot be upgraded due to unresolvable dependencies:
      pamac-cli  libpamac  pamac-gtk

:: Do you want to skip the above packages for this upgrade? [y/N] y
looking for conflicting packages...
error: failed to prepare transaction (could not satisfy dependencies)
:: installing alsa-lib ( breaks dependency 'alsa-lib=1.2.5' required by lib32-alsa-lib

In order to update at all, I had to remove quite a few packages (including all of pamac and manjaro-steam):

$ sudo pacman -Rnsc pamac-gtk pamac-cli lib32-alsa-lib web-installer-url-handler
[sudo] password for user: 
checking dependencies...
:: htop optionally requires lsof: show files opened by a process
:: lib32-openal optionally requires lib32-fluidsynth: MIDI rendering
:: lib32-sdl2 optionally requires lib32-alsa-lib: ALSA audio driver
:: lib32-sdl2 optionally requires lib32-libpulse: PulseAudio audio driver
:: lib32-sdl2 optionally requires lib32-jack: JACK audio driver
:: wine-staging optionally requires lib32-libpulse
:: wine-staging optionally requires lib32-alsa-plugins
:: wine-staging optionally requires lib32-alsa-lib

Packages (34) appstream-glib-0.7.18-2  archlinux-appstream-data-20210423-1
              game-devices-udev-0.13-1  gcab-1.4-1  lib32-alsa-plugins-1.2.5-1
              lib32-db-5.3.28-4  lib32-flac-1.3.3-1  lib32-fluidsynth-2.1.8-1
              lib32-jack-0.125.0-3  lib32-libasyncns-0.8+3+g68cd5af-2
              lib32-libinstpatch-1.1.6-1  lib32-libogg-1.3.5-1
              lib32-libpulse-14.2-2  lib32-libsndfile-1.0.31-1
              lib32-libtasn1-4.16.0-2  lib32-libvorbis-1.3.7-1
              lib32-libxss-1.2.3-1  lib32-libxtst-1.2.3-2  lib32-nspr-4.31-1
              lib32-nss-3.66-1  lib32-opus-1.3.1-1  lib32-p11-kit-0.23.22-1
              lib32-portaudio-1:19.7.0-1  lib32-sqlite-3.35.5-1
              libstemmer-0+713-2  lsof-4.94.0-1  manjaro-hello-0.6.6-5
              manjaro-icons-20191015-1  pamac-common-10.1.2-4
              steam-manjaro-  lib32-alsa-lib-1.2.5-2
              pamac-cli-10.1.2-4  pamac-gtk-10.1.2-4

Total Removed Size:  56.22 MiB

After the update, I was able to manually re-install those packages with sudo pacman -S pamac-gtk steam-manjaro manjaro-hello

I’m at a loss as to why that was needed though.

My Elan touchpad on my Lenovo Ideapad 5 is no longer detected with kernel 5.12.10-1. Working fine with 5.10.43-1. Anyone else?

Then simply stay with 5.10 kernel.

which means now the default SIGLEVEL;
SigLevel = Required DatabaseOptional
will be applied to all repos i guess.

i just merged it to pamac.conf and got rid of it, cant understand why it was not differed to user via pacman as other conf files.

i also got /etc/makepkg.conf.pacnew

As for manjaro, after this update, everything is so far
in order. However, I have two bugs in KDE/Plasma.

  1. bug: Discover shows an update in the taskbar even though
    everything is up to date. So the same as in the last update with pamac.

2nd bug: The activation button of the energy saving mode is inverted.
When the button is activated, the energy saving mode is switched off. And vice versa.

If I have time, I will have a look at kde/plasma and report the bugs, if nobody has done it yet.

Do you mean this ?

Thats the new intended way, is not a bug.

Yes, that’s what I mean. So no bug !
One wonders, why always these senseless changes ?

I have read your appendix, wherein the reason for the change is explained. So i can understand now .

But the description behind the button “Inhibit automatic sleep and screen locking”.
is not displayed for me at all. This may be due to the German display. Otherwise it would have been clearer.

I thank you for the hint.

yeah, though the former was already in the [options] that’s why I was wondering, how the latter was kept for so long :slight_smile: Well I guess it deserved a… “clean up” .

I’m seeing a new graphical bug on Manjaro with (but perhaps not related to) KDE Plasma, particularly with my multi-monitor setup.

On the unlock screen (note, not the initial sign in, that’s fine.), both screens’ login displays are shoved up to the top of half one the leftmost display, on top of one another. This also only occurs after displays have already been automatically shut off (screen timeout, in other words). The placement of the login screens is similar to a bug I’ve always had where the initial splash screen for one of the monitors is placed too high and gets cut off.

For the record, my displays are different resolutions, with the leftmost one being 1080p and the right one being 1440p (I only have two). They are aligned in software such that their bottoms line up. So these issues definitely come from the computer trying to place the display(s) at the top left point of the Xorg screen (perhaps this is X11’s doing? I don’t really know, I still don’t fully understand exactly what is handled by the display server and what is handled by the window manager.)

I’m not very experienced with the forum, so if I messed up or need to provide more info, just let me know, I’m more than happy to do it.

Edit: I’m using Nvidia proprietary drivers, if it matters. Left display is HDMI, right is DP.

Edit 2: This was hidden. Perhaps I didn’t make it clear enough that the login thing happened directly as a result of this update. Or maybe I don’t understand what kind of bugs I’m supposed to report here. Either way, if this gets hidden again, I’d really appreciate an explanation if this gets hidden again so I can better participate in the future.

I have an RTX 260. When trying to load into a plasma Wayland session using the non-free driver, the login fails. Previously it would crash my device. So that is good! When trying to log in using the free driver, I can get to the desktop, but it freezes. The top 1/8th of my display was just a black bar even on x11 until I switched back to the non-free driver.