I had the same issues with gdm3, it simply would not start after installing ubuntu-desktop. However, I had done manual edits to at least one /etc/pam.d/common-* file, in which case pam-auth-update aborts if "-force" is not specified.
My theory on the real problem is that pam-auth-update is run during some package installs and it would have added pam_systemd to /etc/pam.d/common-session. I fixed it by adding this line to /etc/pam.d/gdm-launch-environment: session optional pam_systemd.so The gdm3 service just keeps trying to start gdm-x-session over and over again, flooding syslog. Gdm-x-session: Could not register display: GDBus.Error.AccessDenied: No display available Gdm3: GdmManager: Error while retrieving session id for sender: Error getting session id from systemd: No data available Gdm3: GdmManager: trying to register new display Gdm-x-session: could not fetch environment: GDBus.Error.Spawn.ChildExited: Process 1 exited with status 1 usr/lib/gdm3/gdm-x-session: dbus-daemon: Activated service '1' failed: Process 1 exited with status 1
This error in syslog finally lead me to my solution: (EE) systemd-logind: failed to get session: PID 10023 does not belong to any known sessionĪs a result of that error, gdm-x-session fails further along in the gdm3 start up process and aborts: /usr/lib/gdm3/gdm-x-session: dbus-daemon: Activating service name='1' requested by ':1.0' (uid=136 pid=2849 comm="/usr/lib/gdm3/gdm-x-session gnome-session -autost" label="unconfined")
0 kommentar(er)
