systemd-homed-service disabled (default - was like that at first)
exapsy systemd[1108]: pam_systemd_home(systemd_user:account): systemd-homed is not available: Unit dbus-org-freedesktop-home1.servce not found
exapsy systemd[1108]: PAM failed: Authentication service cannot retrieve authentication info
exapsy systemd[1108]: user@120.service: Failed to set up PAM session: Operation not permitted
exapsy systemd[1108]: user@120.service: Failed at step PAM spawning /usr/lib/systemd/systemd: Operation not permitted
systemd-homed service enabled
exapsy systemd[1108]: pam_systemd_home(systemd_user:account): Not a user managed by systemd-homed: No home for user gdm known
exapsy systemd[1108]: PAM failed: Authentication service cannot retrieve authentication info
exapsy systemd[1108]: user@120.service: Failed to set up PAM session: Operation not permitted
exapsy systemd[1108]: user@120.service: Failed at step PAM spawning /usr/lib/systemd/systemd: Operation not permitted
Removing pam_systemd_home.so from /etc/pam.d/system-auth and any other file
Placing pam_unix.so as [success=1 default=ignore] instead of pam_systemd_home.so and reorder it to be first
Reinstalling systemd
Reinstalling gdm
Reinstalling systemd-homed
Restarting sudo systemctl restart user@120.service results in the same errors
Removing ~/.profile (mv ~/.profile ~/.profile.bk)
I really dont wanna format right now, I want just peace (not having to re-setup literally everything) and to finally solve this and get some piece of troubleshooting knowledge.
System information
$ uname -a
Linux exapsy 5.10.68-1-MANJARO #1 SMP PREEMPT Wed Sep 22 12:29:47 UTC 2021 x86_64 GNU/Linux
In the error log there is a line unix_chkpwd[842]: could not obtain user info (gdm) I’m not sure what this means and if there is a issue with the gdm user, that could maybe explain gdm not starting. What is the status of the gdm service?
How have you reinstalled gdm? there is gdm-plymouth & gdm available.
From a announcement from stable update thread: on gdm and gdm-plymouth:
Log into your system via tty and depending on your use of Plymouth or bootsplash-systemd choose a option from this post
○ gdm.service - GNOME Display Manager
Loaded: error (Reason: Unit gdm.service failed to load properly, please adjust/correct and reload service manager: File exists)
Active: inactive (dead)
Sep 30 23:19:24 exapsy systemd[1]: gdm.service: Two services allocated for the same bus name org.gnome.DisplayManager, refusing operation.
I reinstalled gdm-plymouth as well pacman -S gdm-plymouth libgdm-plymouth with no success
It feels going forward and back again, I hope someone with more knowledge of the boot process steps in and helps out and that you can get this fixed and sorry that I could not help you.
I’m on Wayland and i’m experiencing a similar issue since last update: at every boot GDM seems to works as expected but, after selecting user, at the password prompt it crashes and i get a blank screen.
After switching to TTY2 and back to TTY1, GDM restarts and works well.
This happens every time with my usual setup: laptop with closed lid connected to a external monitor.
I tried booting with external monitor disconnected and with integrated display the login was ok. So i tried just setting the external monitor as “primary” in Gnome Settings, but nothing changed.
Tried also reinstalling gdm.
I don’t use Plymouth and don’t have splash kernel flag.
I see a lot of errors in my journalctl -b 0 but i am not able to find what causes them, even comparing before and after switching to TTY2.
I hope to get some suggestion to try further to resolve this without just wait for the next update like
like reported by @Chrysostomus, and then rebooted.
The issue is still there, but at a first impression i have to wait longer for GDM to crash: about 10 seconds, which is enough to accomplish login
