This is a wiki post; please edit as necessary.
Please, consider subscribing to the Testing Updates Announcements RSS feed
New issues:
In the last Testing Update we got reports of broken Nvidia drivers
Therefore the Nvidia driver got downgraded to 460.73.01 [production branch release] as requested here. People who had already updated to 465 series need to do a sudo pacman -Syyuu to get the proper drivers, as some of our Kernels got updated again with this update pack.
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
The php package has been updated to version 8.0. Please refer to the upstream migration guide. As some applications are not compatible with PHP 8 yet we provide a php7 package which can be installed alongside version 8. Packages that depend on PHP reflect this update and will require php7 if needed. You might need to update your configuration accordingly. PHP 7 binaries and configuration have the â7â suffix:
Note that support for php7 will be limited and likely be dropped in about a year depending on how soon the majority of applications will be compatible with version 8.
Google has announced that they are going to block everything but Chrome from accessing certain Google features (like Chrome sync) starting on March 15. This decision by Google is going to affect Archâs chromium package a bit earlier, on March 2, when Chromium 89 gets released.
We know for sure that data syncing will stop working (passwords, bookmarks, etc.). Other features such as geolocation or enhanced spell check might continue to function for a bit longer. Extensions integrating with Google Drive might misbehave and LibreOffice will lose access to documents stored there.
Other distros such as openSUSE and Fedora have already removed the soon-to-be-limited API keys from their Chromium 88 packages. Fedoraâs advisory provides a great deal of perspective on this and I also found this Hackaday post to be quite informative.
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.
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.
There seems to be a problem with the kernel 5.12 and X.org.
When I try to login to i3 with this kernel I get thrown back to tty1.
The last messages read
xf86EnableIOPorts: failed to set IOPL for I/O (Operation not permitted)
LX: Suspending AIGLX clients for VT switch(EE) Server terminated with error (1). Closing log file.y/.local/share/xorg/Xorg.0.log" for additional information.(EE) (II) AIGnextcloud: Fatal IO error 11 (Resursen tillfÀlligt otillgÀnglig) on X server :0.
clipit: Fatal IO error 11 (Resursen tillfÀlligt otillgÀnglig) on X server :0.
i3: Cannot open display
xinit: connection to X server lost
When I boot with kernel 5.11 or 5.10, no such problem occurs.
And I can start wayland (in my case sway) without any problem after booting kernel 5.12. In fact Iâm writing this in such a session.
EDIT: Sorry, forgot about the swedish in the error-message. It means Resources not available right now.
Had problems that I could solve easily. sudo pamac update
Following error messages:
Warnung: das Installieren von libjpeg-turbo (2.1.0-1) verletzt AbhĂ€ngigkeit von âlibjpeg-turbo=2.0.6â benötigt von lib32-libjpeg-turbo
FĂŒge lib32-libjpeg-turbo hinzu, um zu entfernen
Fehler: Vorgang konnte nicht erfolgreich vorbereitet werden:
Kann AbhĂ€ngigkeiten nicht erfĂŒllen:
das Entfernen von lib32-libjpeg-turbo verletzt AbhĂ€ngigkeit von âlib32-libjpegâ benötigt von lib32-gdk-pixbuf2,
wenn möglich, entferne lib32-gdk-pixbuf2 und versuche es erneut
das Entfernen von lib32-libjpeg-turbo verletzt AbhĂ€ngigkeit von âlib32-libjpegâ benötigt von lib32-libtiff,
wenn möglich, entferne lib32-libtiff und versuche es erneut
das Entfernen von lib32-libjpeg-turbo verletzt AbhĂ€ngigkeit von âlibjpeg.so=8-32â benötigt von lib32-libtiff,
wenn möglich, entferne lib32-libtiff und versuche es erneut
AbhĂ€ngigkeiten werden aufgelöstâŠ
Interne Konflikte werden ĂŒberprĂŒftâŠ
Fehler: Vorgang konnte nicht erfolgreich vorbereitet werden:
Kann AbhĂ€ngigkeiten nicht erfĂŒllen:
das Entfernen von lib32-libjpeg-turbo verletzt AbhĂ€ngigkeit von âlib32-libjpegâ benötigt von lib32-gdk-pixbuf2,
wenn möglich, entferne lib32-gdk-pixbuf2 und versuche es erneut
das Entfernen von lib32-libjpeg-turbo verletzt AbhĂ€ngigkeit von âlib32-libjpegâ benötigt von lib32-libtiff,
wenn möglich, entferne lib32-libtiff und versuche es erneut
das Entfernen von lib32-libjpeg-turbo verletzt AbhĂ€ngigkeit von âlibjpeg.so=8-32â benötigt von lib32-libtiff,
wenn möglich, entferne lib32-libtiff und versuche es erneut sudo pacman-mirrors --fasttrack 5 && sudo pacman -Syyu
No problems Update ran through.
Having issues with the aur since the update. I have aur support enabled and software mode ISNâT enabled but no aur packages are being found in pamac gui
warning: lib32-libva-mesa-driver: local (21.0.3-1.1) is newer than multilib (21.0.3-1)
warning: lib32-mesa: local (21.0.3-1.1) is newer than multilib (21.0.3-1)
Edit: Nevermind, I see that -2 is already in the repos. Iâll wait for that to sync to my mirrors.
Take that 
Arch 
(=still on 5.11.16).
