Bug 1089989

Summary: gdm fails to start, errors in pam/system setup
Product: [openSUSE] openSUSE Distribution Reporter: Andreas Jaeger <aj>
Component: GNOMEAssignee: E-mail List <gnome-bugs>
Status: RESOLVED INVALID QA Contact: E-mail List <qa-bugs>
Severity: Critical    
Priority: P5 - None CC: aj, behlert, fcrozat, fezhang, josef.moellers, systemd-maintainers, xiaoguang.wang, yfjiang
Version: Leap 15.0   
Target Milestone: ---   
Hardware: Other   
OS: Other   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: Yes
Marketing QA Status: --- IT Deployment: ---

Description Andreas Jaeger 2018-04-18 07:57:34 UTC
gdm does not start at all, from journalctl:


Apr 18 09:52:49 t450.site systemd[1]: Started Locale Service.
Apr 18 09:52:49 t450.site systemd[1]: Created slice User Slice of gdm.
Apr 18 09:52:49 t450.site systemd[1]: Starting User Manager for UID 457...
Apr 18 09:52:49 t450.site systemd[14954]: pam_unix(systemd-user:session): session opened for user gdm by (uid=0)
Apr 18 09:52:49 t450.site systemd-logind[1457]: New session c1013 of user gdm.
Apr 18 09:52:49 t450.site systemd[1]: Started Session c1013 of user gdm.
Apr 18 09:52:49 t450.site systemd[14954]: Failed to create /user.slice/user-457.slice/user@457.service/init.scope control group: Permission denied
Apr 18 09:52:49 t450.site systemd[14954]: Failed to allocate manager object: Permission denied
Apr 18 09:52:49 t450.site systemd[1]: Failed to start User Manager for UID 457.
Apr 18 09:52:49 t450.site systemd[1]: user@457.service: Unit entered failed state.
Apr 18 09:52:49 t450.site systemd[1]: user@457.service: Failed with result 'protocol'.
Apr 18 09:52:49 t450.site gdm-launch-environment][14950]: pam_systemd(gdm-launch-environment:session): Failed to create session: Start job for unit user@457.service failed with 'failed'
Apr 18 09:52:49 t450.site gdm-launch-environment][14950]: pam_unix(gdm-launch-environment:session): session opened for user gdm by (uid=0)
Apr 18 09:52:49 t450.site /usr/lib/gdm/gdm-wayland-session[14956]: dbus-daemon[14958]: [session uid=457 pid=14958] Activating service name='org.freedesktop.systemd1' requested by ':1.0' (uid
Apr 18 09:52:49 t450.site /usr/lib/gdm/gdm-wayland-session[14956]: dbus-daemon[14958]: [session uid=457 pid=14958] Activated service 'org.freedesktop.systemd1' failed: Process org.freedeskto
Apr 18 09:52:49 t450.site /usr/lib/gdm/gdm-wayland-session[14956]: Unable to register display with display manager
Apr 18 09:52:49 t450.site gdm-launch-environment][14950]: pam_unix(gdm-launch-environment:session): session closed for user gdm
Apr 18 09:52:49 t450.site systemd-logind[1457]: Removed session c1013.
Apr 18 09:52:49 t450.site systemd[1]: Removed slice User Slice of gdm.

This is after an update from Leap 42.3
Comment 1 Dr. Werner Fink 2018-04-18 08:09:13 UTC
I can second this as I've seen the repeating restart of gdm on Andreas laptop ... looks like systemd could not create files/directories below  /sys/fs/cgroup/systemd
Comment 2 Andreas Jaeger 2018-04-18 08:11:15 UTC
Following https://github.com/systemd/systemd/issues/6038 I did:

    rpm -e --no-deps gdm.
    Remove the gdm user, the gdm group and any files in /var/lib/gdm.
    Install gdm. This created a new gdm user with a different uid.

And I have a working setup again...
Comment 3 Andreas Jaeger 2018-04-18 08:13:02 UTC
So, I can login and have a working system - but still see the errors. I'm confused ;(

Will reboot now...
Comment 4 Dr. Werner Fink 2018-04-18 08:16:44 UTC
somehow strange ... does this depend on the ID number used for user gdm?

Andreas: which new number ... if any ... had been created now for user gdm.
Maybe there is a difference between system users and normal users
Comment 5 Dr. Werner Fink 2018-04-18 08:22:51 UTC
This is a blocker IMHO
Comment 6 Dr. Werner Fink 2018-04-18 08:24:07 UTC
Could also happen on SLES-15 (IMHO)
Comment 7 Dr. Werner Fink 2018-04-18 08:29:58 UTC
From ``journalctl -b 0 --unit display-manager.service''

Apr 18 10:26:34 t450.site systemd[1]: Starting X Display Manager...
Apr 18 10:26:34 t450.site display-manager[2215]: /etc/vconsole.conf available
Apr 18 10:26:34 t450.site display-manager[2215]: KEYMAP: de-latin1-nodeadkeys
Apr 18 10:26:34 t450.site display-manager[2215]: Command: localectl set-keymap de-latin1-nodeadkeys
Apr 18 10:26:34 t450.site display-manager[2215]: I: Using systemd /usr/share/systemd/kbd-model-map mapping
Apr 18 10:26:34 t450.site display-manager[2215]: Starting service gdm..done
Apr 18 10:26:34 t450.site systemd[1]: Started X Display Manager.
Apr 18 10:26:34 t450.site gdm[2284]: Child process -2368 was already dead.
Apr 18 10:26:34 t450.site gdm[2284]: Child process 2362 was already dead.
Apr 18 10:26:34 t450.site gdm[2284]: Unable to kill session worker process
Apr 18 10:26:34 t450.site gdm[2284]: Child process -2386 was already dead.
Apr 18 10:26:34 t450.site gdm[2284]: Child process 2381 was already dead.
Apr 18 10:26:34 t450.site gdm[2284]: Unable to kill session worker process
Apr 18 10:26:35 t450.site gdm[2284]: Child process -2400 was already dead.
Apr 18 10:26:35 t450.site gdm[2284]: Child process 2395 was already dead.
Apr 18 10:26:35 t450.site gdm[2284]: Unable to kill session worker process
Apr 18 10:26:35 t450.site gdm[2284]: Child process -2414 was already dead.
Apr 18 10:26:35 t450.site gdm[2284]: Child process 2409 was already dead.
Apr 18 10:26:35 t450.site gdm[2284]: Unable to kill session worker process
Apr 18 10:26:35 t450.site gdm[2284]: Child process -2428 was already dead.
Apr 18 10:26:35 t450.site gdm[2284]: Child process 2423 was already dead.
Apr 18 10:26:35 t450.site gdm[2284]: Unable to kill session worker process
Apr 18 10:26:35 t450.site gdm[2284]: Child process -2440 was already dead.
Apr 18 10:26:35 t450.site gdm[2284]: Child process 2437 was already dead.
Apr 18 10:26:35 t450.site gdm[2284]: Unable to kill session worker process
Apr 18 10:26:35 t450.site gdm[2284]: Child process -2452 was already dead.
Apr 18 10:26:35 t450.site gdm[2284]: Child process 2449 was already dead.
Apr 18 10:26:35 t450.site gdm[2284]: Unable to kill session worker process
Apr 18 10:26:35 t450.site gdm[2284]: Child process -2464 was already dead.
Apr 18 10:26:35 t450.site gdm[2284]: Child process 2461 was already dead.
Apr 18 10:26:35 t450.site gdm[2284]: Unable to kill session worker process
Apr 18 10:26:35 t450.site gdm[2284]: Child process -2476 was already dead.
Apr 18 10:26:35 t450.site gdm[2284]: Child process 2473 was already dead.
Apr 18 10:26:35 t450.site gdm[2284]: Unable to kill session worker process
Apr 18 10:26:35 t450.site gdm[2284]: Child process -2488 was already dead.
Apr 18 10:26:35 t450.site gdm[2284]: Child process 2485 was already dead.
Apr 18 10:26:35 t450.site gdm[2284]: Unable to kill session worker process
Apr 18 10:26:35 t450.site gdm[2284]: Child process -2500 was already dead.
Apr 18 10:26:35 t450.site gdm[2284]: Child process 2497 was already dead.
Apr 18 10:26:35 t450.site gdm[2284]: Unable to kill session worker process
Apr 18 10:26:35 t450.site gdm[2284]: Child process -2512 was already dead.
Apr 18 10:26:35 t450.site gdm[2284]: Child process 2509 was already dead.
Apr 18 10:26:35 t450.site gdm[2284]: Unable to kill session worker process
Apr 18 10:26:35 t450.site gdm[2284]: Child process -2524 was already dead.
Apr 18 10:26:35 t450.site gdm[2284]: Child process 2521 was already dead.
Apr 18 10:26:35 t450.site gdm[2284]: Unable to kill session worker process
Apr 18 10:26:35 t450.site gdm[2284]: Child process -2536 was already dead.
Apr 18 10:26:35 t450.site gdm[2284]: Child process 2533 was already dead.
Apr 18 10:26:35 t450.site gdm[2284]: Unable to kill session worker process
Apr 18 10:26:35 t450.site gdm[2284]: Child process -2548 was already dead.
Apr 18 10:26:35 t450.site gdm[2284]: Child process 2545 was already dead.
Apr 18 10:26:35 t450.site gdm[2284]: Unable to kill session worker process
Apr 18 10:26:35 t450.site gdm[2284]: Child process -2560 was already dead.
Apr 18 10:26:35 t450.site gdm[2284]: Child process 2557 was already dead.
[...]
Apr 18 10:26:58 t450.site gdm[2284]: Child process -6380 was already dead.
Apr 18 10:26:58 t450.site gdm[2284]: Child process 6377 was already dead.
Apr 18 10:26:58 t450.site gdm[2284]: Unable to kill session worker process
Apr 18 10:27:00 t450.site gdm[2284]: GLib: g_variant_new_string: assertion 'string != NULL' failed
Apr 18 10:27:00 t450.site gdm[2284]: GLib: g_variant_new_string: assertion 'string != NULL' failed
Apr 18 10:27:01 t450.site gdm[2284]: GLib: g_variant_new_string: assertion 'string != NULL' failed
Apr 18 10:27:01 t450.site gdm[2284]: GLib: g_variant_new_string: assertion 'string != NULL' failed
Apr 18 10:27:02 t450.site gdm[2284]: GLib: g_variant_new_string: assertion 'string != NULL' failed
Apr 18 10:27:04 t450.site gdm[2284]: Child process -7210 was already dead.
Apr 18 10:27:04 t450.site gdm[2284]: Child process 7207 was already dead.
Apr 18 10:27:04 t450.site gdm[2284]: Unable to kill session worker process
Apr 18 10:27:04 t450.site gdm[2284]: Child process -7222 was already dead.
Apr 18 10:27:04 t450.site gdm[2284]: Child process 7219 was already dead.
Apr 18 10:27:04 t450.site gdm[2284]: Unable to kill session worker process
Apr 18 10:27:04 t450.site gdm[2284]: Child process -7234 was already dead.
[...]
Apr 18 10:27:11 t450.site gdm[2284]: Unable to kill session worker process
Apr 18 10:27:11 t450.site gdm[2284]: Child process -8457 was already dead.
Apr 18 10:27:11 t450.site gdm[2284]: Child process -8457 was already dead.
Apr 18 10:27:12 t450.site gdm[2284]: Could not start command '/usr/lib/gdm/gdm-session-worker': Too many open files
Apr 18 10:27:12 t450.site gdm[2284]: GLib: g_child_watch_add_full: assertion 'pid > 0' failed
Apr 18 10:27:12 t450.site gdm[2284]: Child process -8469 was already dead.
Apr 18 10:27:12 t450.site gdm[2284]: Child process 8466 was already dead.
Apr 18 10:27:12 t450.site gdm[2284]: Unable to kill session worker process
Comment 8 Dr. Werner Fink 2018-04-18 08:31:30 UTC
Now fronm ``journalctl -b 0'' including systemd as well:

Apr 18 10:27:11 t450.site systemd-logind[1214]: New session c503 of user gdm.
Apr 18 10:27:11 t450.site systemd[1]: Started Session c503 of user gdm.
Apr 18 10:27:11 t450.site gdm-launch-environment][8442]: pam_systemd(gdm-launch-environment:session): Failed to create session: Start job for unit user@457.servi
Apr 18 10:27:11 t450.site gdm-launch-environment][8442]: pam_unix(gdm-launch-environment:session): session opened for user gdm by (uid=0)
Apr 18 10:27:11 t450.site /usr/lib/gdm/gdm-wayland-session[8445]: dbus-daemon[8447]: [session uid=457 pid=8447] Activating service name='org.freedesktop.systemd1
Apr 18 10:27:11 t450.site /usr/lib/gdm/gdm-wayland-session[8445]: dbus-daemon[8447]: [session uid=457 pid=8447] Activated service 'org.freedesktop.systemd1' fail
Apr 18 10:27:11 t450.site /usr/lib/gdm/gdm-wayland-session[8445]: Unable to register display with display manager
Apr 18 10:27:11 t450.site gdm-launch-environment][8442]: pam_unix(gdm-launch-environment:session): session closed for user gdm
Apr 18 10:27:11 t450.site systemd-logind[1214]: Removed session c503.
Apr 18 10:27:11 t450.site systemd[1]: Removed slice User Slice of gdm.
Apr 18 10:27:11 t450.site gdm[2284]: Child process -8445 was already dead.
Apr 18 10:27:11 t450.site gdm[2284]: Child process 8442 was already dead.
Apr 18 10:27:11 t450.site gdm[2284]: Unable to kill session worker process
Apr 18 10:27:11 t450.site systemd[1]: Created slice User Slice of gdm.
Apr 18 10:27:11 t450.site systemd[1]: user@457.service: Start request repeated too quickly.
Apr 18 10:27:11 t450.site systemd[1]: Failed to start User Manager for UID 457.
Apr 18 10:27:11 t450.site systemd[1]: user@457.service: Failed with result 'protocol'.
Apr 18 10:27:11 t450.site systemd-logind[1214]: New session c504 of user gdm.
Apr 18 10:27:11 t450.site systemd[1]: Started Session c504 of user gdm.
Apr 18 10:27:11 t450.site gdm-launch-environment][8454]: pam_systemd(gdm-launch-environment:session): Failed to create session: Start job for unit user@457.servi
Apr 18 10:27:11 t450.site gdm-launch-environment][8454]: pam_unix(gdm-launch-environment:session): session opened for user gdm by (uid=0)
Apr 18 10:27:11 t450.site /usr/lib/gdm/gdm-wayland-session[8457]: dbus-daemon[8459]: [session uid=457 pid=8459] Activating service name='org.freedesktop.systemd1
Apr 18 10:27:11 t450.site /usr/lib/gdm/gdm-wayland-session[8457]: dbus-daemon[8459]: [session uid=457 pid=8459] Activated service 'org.freedesktop.systemd1' fail
Apr 18 10:27:11 t450.site /usr/lib/gdm/gdm-wayland-session[8457]: Unable to register display with display manager
Apr 18 10:27:11 t450.site gdm-launch-environment][8454]: pam_unix(gdm-launch-environment:session): session closed for user gdm
Apr 18 10:27:11 t450.site gdm[2284]: Child process -8457 was already dead.
Apr 18 10:27:11 t450.site systemd-logind[1214]: Removed session c504.
Apr 18 10:27:11 t450.site systemd[1]: Removed slice User Slice of gdm.
Apr 18 10:27:11 t450.site gdm[2284]: Child process -8457 was already dead.
Apr 18 10:27:12 t450.site systemd[1]: Created slice User Slice of gdm.
Apr 18 10:27:12 t450.site systemd[1]: user@457.service: Start request repeated too quickly.
Apr 18 10:27:12 t450.site systemd[1]: Failed to start User Manager for UID 457.
Apr 18 10:27:12 t450.site systemd[1]: user@457.service: Failed with result 'protocol'.
Apr 18 10:27:12 t450.site systemd-logind[1214]: New session c505 of user gdm.
Apr 18 10:27:12 t450.site systemd[1]: Started Session c505 of user gdm.
Comment 9 Dr. Werner Fink 2018-04-18 08:34:45 UTC
t450:~ # systemctl  status user@457.serviceuser@457.service - User Manager for UID 457
   Loaded: loaded (/etc/systemd/system/user@.service; static; vendor preset: disabled)
   Active: failed (Result: protocol) since Wed 2018-04-18 10:33:40 CEST; 32s ago
  Process: 19887 ExecStart=/usr/lib/systemd/systemd --user (code=exited, status=1/FAILURE)
 Main PID: 19887 (code=exited, status=1/FAILURE)

Apr 18 10:33:46 t450.site systemd[1]: user@457.service: Failed with result 'protocol'.
Apr 18 10:33:47 t450.site systemd[1]: user@457.service: Start request repeated too quickly.
Apr 18 10:33:47 t450.site systemd[1]: Failed to start User Manager for UID 457.
Apr 18 10:33:47 t450.site systemd[1]: user@457.service: Failed with result 'protocol'.
Apr 18 10:33:47 t450.site systemd[1]: user@457.service: Start request repeated too quickly.
Apr 18 10:33:47 t450.site systemd[1]: Failed to start User Manager for UID 457.
Apr 18 10:33:47 t450.site systemd[1]: user@457.service: Failed with result 'protocol'.
Apr 18 10:33:47 t450.site systemd[1]: user@457.service: Start request repeated too quickly.
Apr 18 10:33:47 t450.site systemd[1]: Failed to start User Manager for UID 457.
Apr 18 10:33:47 t450.site systemd[1]: user@457.service: Failed with result 'protocol'.
Comment 10 Dr. Werner Fink 2018-04-18 08:43:47 UTC
It turns out that after some debugging there was a file /etc/systemd/system/user@.service with

diff -up /usr/lib/systemd/system/user@.service /etc/systemd/system/user@.service
--- /usr/lib/systemd/system/user@.service       2018-03-15 10:20:48.000000000 +0100
+++ /etc/systemd/system/user@.service   2015-11-19 13:30:14.601940157 +0100
@@ -16,5 +16,4 @@ Type=notify
 ExecStart=-/usr/lib/systemd/systemd --user
 Slice=user-%i.slice
 KillMode=mixed
-Delegate=yes
-TasksMax=infinity
+Delegate=no

which had crashed gdm due missing permissions for control group controllers
Comment 11 Andreas Jaeger 2018-04-18 08:50:42 UTC
Thanks Werner!
Comment 12 Andreas Jaeger 2018-04-18 08:53:50 UTC
*** Bug 1088366 has been marked as a duplicate of this bug. ***