This is a wiki post; please edit as necessary.
Please, consider subscribing to the Testing Updates Announcements RSS feed
New issues:
Nvidia drivers won’t work with GSync with some setups. It is known that some Monitors won’t work with the new 470.74 driver. We recommend to disable that feature for now, until Nvidia will fix it. They are tracking it via internal bug number 3382581.
freetype2 update might result in font characters becoming squares. Don’t worry, a relogin to your UI should fix it. We recommend to do the update in a TTY. Affected UIs so far: Gnome, Phosh, Cinnamon.
Re-enable any per-user enabled `pipewire-media-session.service` manually
You should re-enable any per-user pipewire-media-session.service manually to establish a new service alias for pipewire-session-manager.service added with 0.3.38.
We recommend to switch over to Nouveau drivers if your card is mentioned here and the feature you need is not in red TO DOhere 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
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:
For GRUB:
Open a terminal or a TTY
Open /etc/default/grub in your favourite CLI editor (nano vi, emacs`)
Find the line: GRUB_CMDLINE_LINUX_DEFAULT="
Add amdgpu.dc=0
Save
Execute sudo update-grub and reboot
For systemd-boot:
Open a terminal or a TTY
Open /boot/loader/entries/manjarolinux5.10.conf in your favourite CLI editor (nano vi, emacs`)
Add amdgpu.dc=0 to the end of the line options
Save & reboot
For rEFInd:
Open a terminal or a TTY
Open /boot/refind_linux.conf in your favourite CLI editor (nano vi, emacs`)
Find the line: "Boot using default options" "root=
Add amdgpu.dc=0
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:
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")
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
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.
Please RTFT (Read This Fine Thread) first before reporting the same issues over and over again!
Dolphin I had set to open on it’s own desktop was opening on all desktops after the reboot, fixed it by setting it once again to only open on it’s desktop.
Whoogle was fine before the update, after the update it will not run. When I check it’s status using systemctl status whoogle I get.
I would also add that when I launched Pamac to see the updates in today’s testing update it did not find them, but when I launched Konsole and used Topgrade it found them without issue.
The XRender backend was removed in Plasma 5.23, see this commit. Also see this bug report asking for a toggle for software-based rendering. Possible workaround, which I haven’t tried personally:
As a workaround for those that need it, users may add LIBGL_ALWAYS_SOFTWARE=true and GALLIUM_DRIVER=llvmpipe to $HOME/.config/plasma-workspace/env/path.sh. This is however, both unfriendly and not well documented, whereas a checkbox in the settings app would be obvious and user-friendly.
Strange. I always install kernels with their respective headers and dkms never fails except in case of RC kernels where there are some changes that prevent Nvidia modules to be built as usual.
I just installed both the LTS and the 5.14 kernels and switched to the 5.14 kernel and neither seems to be an issue. I went through kernel under system settings in Plasma to install.
I use ThinkPad, I close the laptop lid down (which will close the screen but not lock it) and reopened it, and the desktop will blink and look like this. I need to refresh it.
On first boot after the update, Plasma forgot the location of my three monitors, my one and only panel did not spawn, and I could not right click on the desktop on any monitor. But, executing reboot in a terminal fixed it. Once rebooted and logged in, my panel was there and I could rearrange my monitors to their proper location.
Otherwise, all good on my Nvidia + Wayland machine! I’m so impressed with how quickly all KDE contributors are making the Wayland experience so much smoother
Does further reboot w/o updates preserves the monitor location settings?
If preserves, than update procedure triggered a partial settings reset, which could be planned by a package developers to fix possible lacks of newer version caused by leaving older settings values/settings structures.
I had a small hiccup, which I was able to fix. GTK3 apps were using the Breeze theme in a KDE Xorg session, but the Adwaita theme was being used in Wayland. I had to manually go in System Settings and change my GTK theme to Adwaita, then back to Breeze. Now it respects the setting.
EDIT: Google Chrome does not display window buttons correctly when using --ozone-platform=wayland. Here is how the buttons look.
Here is how they look with --ozone-platform=x11. This is how they should look with Wayland also.
MPV no longer gets window decorations in a Plasma Wayland session.
Edit: This is a strange quirk too. If I have fs=yes in my mpv.conf, it won’t get window decorations upon leaving full screen. Starting mpv with fs=no gives it window decorations.
Announcement for PipeWire users:
