Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
Problem starting ~amd64 gdm (wayland), issue with pam?
View unanswered posts
View posts from last 24 hours
View posts from last 7 days

 
Reply to topic    Gentoo Forums Forum Index Desktop Environments
View previous topic :: View next topic  
Author Message
Sakaki
Guru
Guru


Joined: 21 May 2014
Posts: 409

PostPosted: Tue Nov 06, 2018 2:11 pm    Post subject: Problem starting ~amd64 gdm (wayland), issue with pam? Reply with quote

Hello,

I recently @world updated a ~amd64 systemd GNOME system, only to find that on reboot, gdm (using wayland) stalled out: I was just getting a rapidly flashing textual login screen. (gdm-3.26.2.1-r1, GNOME 3.26). journalctl -u gdm reports:

Code:
Nov 04 14:06:56 buildserver systemd[1]: Starting GNOME Display Manager...
Nov 04 14:06:56 buildserver systemd[1]: Started GNOME Display Manager.
Nov 04 14:06:58 buildserver /usr/libexec/gdm-wayland-session[4524]: dbus-daemon[4526]: [session uid=115 pid=4526] Activating service name='org.freedesktop.systemd1' requested by ':1.0' (uid=115 pid=4524 comm="/usr/libexec/gdm-wayland-session gnome-session --a")
Nov 04 14:06:58 buildserver /usr/libexec/gdm-wayland-session[4524]: dbus-daemon[4526]: [session uid=115 pid=4526] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1
Nov 04 14:06:58 buildserver /usr/libexec/gdm-wayland-session[4524]: Unable to register display with display manager
Nov 04 14:06:58 buildserver gdm[4358]: Child process -4524 was already dead.
Nov 04 14:06:58 buildserver gdm[4358]: Child process 4502 was already dead.
Nov 04 14:06:58 buildserver gdm[4358]: Unable to kill session worker process

... repeats MANY times ... followed by ...

Nov 04 14:07:21 buildserver gdm[4358]: Could not start command '/usr/libexec/gdm-session-worker': Too many open files


Control is returned (to the console) once the gdm respawn finally gives up, as above.

It's possible this is something I've messed up in my environment, but the machine in question is pretty vanilla.

I'll probably post a bug report once I've had a chance to look into this more fully, but in case anyone else has been affected by this, the update which, when reverted, fixed the issue was of sys-libs/pam to 1.3.1. Masking pam back to the stable 1.3.0-r2, everything worked again.
_________________
Regards,

sakaki
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Desktop Environments All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum