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!
That’s a bad idea with something as important as freetype2 as other packages may break. The latest Steam Beta fixes the issue or you can install steam-native as that is not affected.
Timeshift now complains about existing /etc/systemd/system/grub-btrfs.path - i installed grub-btrfs to use with snapper and use timeshift only for rsync-backups to an HDD. If i don’t understand it completely wrong, timeshift shouldn’t claim this file if grub-btrfs is installed explicitly?
I renamed the file, installed the update and replaced the timeshift-file with my original, hopefully that won’t be nessecary for every update now.
I’m glad that Plasma 5.22.5 fixed the bug where Yakuake flashes a solid color as it retracts, and the fix worked as advertised on my system. However, that annoying white flash bug when you close a terminal tab with CtrlD in Konsole and Yakuake is still not fixed on my end, despite having KDE Gear already upgraded to 21.08.1 with this update.
Edit: I forgot to mention that the crossfade effect when resizing/maximizing a window has made a comeback with the Plasma 5.22.5 update! It’s strange that I’m no longer used to seeing it at this point, since it took a while for that fix to be implemented.
I’ve got this issue as well. Installed steam-native which works. However, anyone know whether I can now uninstalled steam-manjaro without losing my library? I guess it just removes the client without removing the library data, but am I right?
The launcher of the package gnome-shell-extension-pop-shell stopped working for me after this update. The quickest way I found to fix it (although it might just be a very poor workaround) was to downgrade back to the previous version. This is the command I ran: sudo pacman -U /var/cache/pacman/pkg/gnome-shell-extension-pop-shell-1.2.0+119+gab87042-1-any.pkg.tar.zst
steam-manjarois Steam. Remove that and Steam is no longer installed. steam-native is just a shortcut to run Steam without the runtime and needed dependencies.
Removing a package never removes user data, your library and settings will be intact.
something bad
with steam , black screen on start , no game , no account visible , game can be selected by icons in menu bar and launched ( proton is on version 6.3-6)
Everything seems good with this update. Kernel 5.14 is a bit faster than 5.13 (possibly a placebo). And I don’t have any problems with steam-runtime or steam-native.
Edit:
Oh, I’m sorry. The second screenshot is steam-native. The steam-runtime browser turns out does broken with this update. But it’s OK. I always use steam-native anyway.
PS: No screenshot is a hoax, they said. (time GMT+7)
