Then, I rebooted my system. Instead of getting the usual GDM’s login screen, I got the infamous “Something has gone wrong …blah blah … Contact a System Administrator”
Went to the journal to confirm:
Feb 12 16:09:01 manjaro-unstable gdm[448]: Gdm: Failed to list cached users: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name :1.11 was not provided by any .service files
Feb 12 16:09:01 manjaro-unstable login[1642]: pam_systemd(login:session): Failed to release session: Interrupted system call
So yeah, there’s no doubt that GDM broke for me with this update.
I haven’t checked yet about this issue upstream, but for now, I was able to get it back working by reverting anything gdm-plymouth related:
It’s not just you, it happened to me as well on my secondary laptop with an AMD APU using GNOME Wayland. I held off updating plymouth for awhile as I couldn’t figure out why it was happening. No one has posted any complaints for the gdm-plymouth & plymouth AUR packages, so I figured I’d push the plymouth update while I was updating gdm-plymouth.
Whatever is causing it, I’d prefer not to keep downgraded packages. Let’s see if it affects anyone else and and figure out what’s causing it.
EDIT: Just to be sure, make sure you’re using gdm.service, not gdm-plymouth.service:
I spent some time today playing around with packages. So far this is the last known combination that works for me without breakage:
sudo pacman -Qi gdm-plymouth libgdm-plymouth plymouth | grep -e 'Name\|Version'
Name : gdm-plymouth
Version : 41.3-2
Name : libgdm-plymouth
Version : 41.3-2
Name : plymouth
Version : 22.02.122-4
The only thing though is that I built libgdm-plymouth from the AUR .
It looks like the latest “stable” version for both gdm-plymouth and libgdm-plymouth available in the AUR is 41.3-2.
I took a look at the repo log on GitLab. Perhaps the problem is line 17 in the commit below?
PSA: The NVIDIA 510.54 drivers are pushed along with extramodules ONLY for kernels 5.10, 5.15, 5.16 & 5.17.
Those who are using 5.4, 4.19, 4.9, or any RT kernel will need to remove the old linuxXXX-nvidia 510.47.03 package, install nvidia-dkms and run mkinitcpio -P.
Reason being GCC 11.2.0 is out and the kernels were built with 11.1.0. With the next batch of kernel updates, extramodules will be built as per usual.
So I moved the file elsewhere, proceeded to update and it didn’t fail at the “checking for file conflicts” step this time, it updated properly, and then I checked and the file nvidia.shutdown was recreated.
I assume this is something that has been added in the packages updates, but I can’t figure where this file comes from. pacman -F /usr/lib/systemd/system-shutdown/nvidia.shutdown doesn’t output anything. What I’m sure is that it is exactly the same content as link above, and not my modified version which has different comment in the file (and that I moved elsewhere before update).
Does someone know if I’m hallucinating or if this file comes with a package/script from Manjaro?
