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 .
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.
Please RTFT (Read This Fine Thread) first before reporting the same issues over and over again!
Update went smooth so far,
the only very little issue was
: lib32-libcanberra-pulse durch multilib/lib32-libcanberra ersetzen? [J/n]
:: libcanberra-pulse durch extra/libcanberra ersetzen? [J/n]
Löse Abhängigkeiten auf...
Suche nach in Konflikt stehenden Paketen...
Fehler: Konnte den Vorgang nicht vorbereiten (Kann Abhängigkeiten nicht erfüllen)
:: Installation von lib32-libcanberra (0.30+2+gc0620e4-4) verletzt Abhängigkeit 'lib32-libcanberra=0.30+2+gc0620e4-3', benötigt von lib32-libcanberra-gstreamer
:: Installation von libcanberra (0.30+2+gc0620e4-4) verletzt Abhängigkeit 'libcanberra=0.30+2+gc0620e4-3', benötigt von libcanberra-gstreamer
but deinstalling libcanberra-gstreamer and lib32-libcanberra-gstreamer manually solved it.
“:: Rozpoczynanie pełnej aktualizacji systemu…
:: Zastąpić lib32-libcanberra-pulse przez multilib/lib32-libcanberra? [T/n] T
:: Zastąpić libcanberra-pulse przez extra/libcanberra? [T/n] T
:: Zastąpić qca przez extra/qca-qt5? [T/n] T
rozwiązywanie zależności…
szukanie sprzecznych pakietów…
błąd: nie udało się przygotować transakcji (nie udało się rozwiązać zależności)
:: instalacja libcanberra (0.30+2+gc0620e4-4) uszkodzi zależności ‘libcanberra=0.30+2+gc0620e4-3’ wymagane przez libcanberra-gstreamer
błąd podczas instalowania paczek z repozytorium”
Edit: as pietlu wrote I deleted libcanberra-gstreamer and then update started.
WARNING: removing this orphans lib32-gstreamer. i believe this is a bug, because removing this package and it’s dependencies results in an unbootable system.
EDIT: I may have spoken too soon - i do indeed have a system that is failing to boot after update, but it appears to be due to a separate issue. After I fixed that, I was able to remove lib32-gstreamer (and it’s dependencies) without issue. Apologies for the false alarm. I can confirm this is safe to remove.
I had the same error 2 days back. @Yochanan [Manjaro Team] Suggested that it is okay to remove these two packages. I have linked the conversation in the above message. No problem from 2 days as on my system. Sorry I dont have any idea about orphan packages. Some other person might help you with that.
i indeed removed lib32-gstreamer as an orphan which set me in wild chase of more orphans appearing, some i felt couldnt be orphans if the system were to function.
installed lib32-gstreamer back (which makes it an explicit install) with all dependencies back and now no orphans. couldnt thank you enough in the nick of time.
I removed all that lib32- stuff, installed the update, added pavucontrol and steam-manjaro back, and everything that I’d removed, and then everything worked. I rebooted and it’s all good.
i did proceed to remove packages (solitary) libcanberra-gstreamer, lib32-libcanberra-gstreamer for the update to progress properly.
at the end of update, i was given the following list of orphans;
lib32-dconf 0.40.0-1
lib32-gstreamer 1.18.4-1
lib32-libgudev 236-1
lib32-libgusb 0.3.6-1
lib32-polkit 0.118-1
i did proceed to remove all these orphans, and on finding more packages orphaned (some which i thought were essential), thanks to @lectrode found that lib32-gstreamer is mandatory package and re-installed it.
would be great to know if, the other removed packages, that were initially orphaned were mandatory for system function as well. Thanks!
Removing lib32-libcanberra-gstreamer and libcanberra-gstreamer made the update run through but I’m now facing a huge amount of orphaned lib32- packages. Are those safe to remove?
