xorg-server 1.20.12-1 doesn’t work with HDMI connected external monitor on Nvidia laptop. Login attempt hangs at SDDM greeter. Loging in without external monitor wors. Connecting HDMI later afrer logged in brings you back to SDDM greeter.
Workaround: downgrade xorg-server* to 1.20.11-1.
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
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!
If we have xwayland 21.1.2-1 and nvidia 470 on this branch. Does that mean that we have everything in place to have working Wayland on Manjaro Gnome with nvidia graphics?
With xorg-server 1.20.12-1 my HDMI connected external monitor stopped working.
I can boot and log in with disconnected HDMI. When I connect the HDMI monitor I get back to SDDM greeter and when I try to login again the screen hangs at load animation. Here Xorg.0.log from that session.
If I boot with connected HDMI and login at SDDM the screen hangs at load animation as well.
After downgrading
You can,in KDE I have tested NVIDIA with Wayland on a optimus laptop and it work,but not very smooth in games yet at least for me,I don’t know if XWayland makes a difference though.
Can confirm,it crashes when I’m on hybrid mode on a optimus laptop,but it doesn’t crash when i’m on NVIDIA mode only.
My Gnome Extensions no longer work after the update. Turning on extensions like Dash to Panel does nothing. Refreshing the Extensions page flips the toggles of extensions back to the “OFF” status.
and then I had to add the plugins myself (it did not load them automatically, neither after restarting it).
The settings of my preset were simply ignored: I had to set all values again, plugin by plugin.
If I set a plugin to “Bypass”, the next time I start the app (even when the service is still running) that plugin is activated again - that is: the bypass setting is not kept.
I had to un-load those plugins completely.
Also, I had to clean up the old .desktop file in ~/.config/autostart and have EasyEffects create the new one from the setting menu (“Start Service at Login”).
For those having the Nvidia module warning, can you reply about the mkinitcpio.conf file? Do you have the Nvidia modules defined in there? I don’t, and I don’t have the warning about this, so maybe it is related? in /etc/mkinitcpio.conf I have MODULES=() (maybe those who don’t have the issue can also tell their configuration too). I also disabled the fallback images generation but I don’t think it is relevant as you have the warning on the normal image apparently.
Are you using nvidia with plasma or gnome on wayland? If you’re on plasma, can you tell me what you did. I’m experiencing glitches with the taskbar and the minimizing of some windows.
After applying the update and reboot, I have the following warnings in journal:
Jul 12 13:04:15 systemd-udevd[577]: vboxnetctl: /usr/lib/udev/rules.d/60-vboxdrv.rules:3 Only network interfaces can be renamed, ignoring NAME="vboxnetctl".
Jul 12 13:04:15 systemd-udevd[557]: vboxdrv: /usr/lib/udev/rules.d/60-vboxdrv.rules:1 Only network interfaces can be renamed, ignoring NAME="vboxdrv".
Jul 12 13:04:15 systemd-udevd[564]: vboxdrvu: /usr/lib/udev/rules.d/60-vboxdrv.rules:2 Only network interfaces can be renamed, ignoring NAME="vboxdrvu".
Jul 12 13:04:16 systemd-udevd[575]: vboxdrv: /usr/lib/udev/rules.d/60-vboxdrv.rules:1 Only network interfaces can be renamed, ignoring NAME="vboxdrv".
Jul 12 13:04:16 systemd-udevd[573]: vboxnetctl: /usr/lib/udev/rules.d/60-vboxdrv.rules:3 Only network interfaces can be renamed, ignoring NAME="vboxnetctl".
Jul 12 13:04:16 systemd-udevd[558]: vboxdrvu: /usr/lib/udev/rules.d/60-vboxdrv.rules:2 Only network interfaces can be renamed, ignoring NAME="vboxdrvu".