Bug#857995: respawn loop due to insufficient permissions

[Michael Biebl]

Am 17.03.2017 um 01:06 schrieb Michael Biebl:
> Am 17.03.2017 um 00:56 schrieb Michael Biebl:

>> To reproduce the problem:
>>
>> reboot, login, logout, switch to console, login as root, systemctl
>> restart gdm3.
>>
>> The result ist a constantly respawned gdm3.service which fails to start
>> properly due to insufficient permissions.
> 
> The constant respawns are done by systemd due to
> 
> Restart=always
> RestartSec=1s
> 
> in gdm.service

After further investigation, this particular information is incorrect,
it seems. It's not the main gdm3 process which dies. So the respawning
is not done by systemd, but by the main gdm process:

Running journalctl -b -1 -u gdm, I get

> Mai 02 13:29:52 pluto systemd[1]: Starting GNOME Display Manager...
> Mai 02 13:29:52 pluto systemd[1]: Started GNOME Display Manager.
> Mai 02 13:29:52 pluto gdm-launch-environment][755]: pam_unix(gdm-launch-environment:session): session opened for user Debian-gdm by (uid=0)
> Mai 02 13:30:00 pluto gdm-password][1509]: pam_unix(gdm-password:session): session opened for user michael by (uid=0)
> Mai 02 13:30:48 pluto systemd[1]: Stopping GNOME Display Manager...
> Mai 02 13:30:48 pluto gdm3[740]: GLib: g_hash_table_find: assertion 'version == hash_table->version' failed
> Mai 02 13:30:48 pluto systemd[1]: Stopped GNOME Display Manager.
> Mai 02 13:30:48 pluto systemd[1]: Starting GNOME Display Manager...
> Mai 02 13:30:48 pluto systemd[1]: Started GNOME Display Manager.
> Mai 02 13:30:48 pluto gdm-launch-environment][2286]: pam_unix(gdm-launch-environment:session): session opened for user Debian-gdm by (uid=0)
> Mai 02 13:30:48 pluto gdm3[2282]: GdmDisplay: display lasted 0.187789 seconds
> Mai 02 13:30:48 pluto gdm3[2282]: Child process -2290 was already dead.
> Mai 02 13:30:48 pluto gdm3[2282]: Child process 2286 was already dead.
> Mai 02 13:30:48 pluto gdm3[2282]: Unable to kill session worker process
> Mai 02 13:30:48 pluto gdm-launch-environment][2306]: pam_unix(gdm-launch-environment:session): session opened for user Debian-gdm by (uid=0)
> Mai 02 13:30:48 pluto gdm3[2282]: Child process -2309 was already dead.
> Mai 02 13:30:48 pluto gdm3[2282]: Child process 2306 was already dead.
> Mai 02 13:30:48 pluto gdm3[2282]: Unable to kill session worker process
> Mai 02 13:30:48 pluto gdm-launch-environment][2314]: pam_unix(gdm-launch-environment:session): session opened for user Debian-gdm by (uid=0)
> Mai 02 13:30:48 pluto gdm3[2282]: GdmDisplay: display lasted 0.128089 seconds
> Mai 02 13:30:48 pluto gdm3[2282]: Child process -2317 was already dead.
> Mai 02 13:30:48 pluto gdm3[2282]: Child process 2314 was already dead.
> Mai 02 13:30:48 pluto gdm3[2282]: Unable to kill session worker process

[and so on, until forcefully rebooting the system]

> Mai 02 13:30:50 pluto systemd[1]: Stopping GNOME Display Manager...
> Mai 02 13:30:51 pluto gdm3[2282]: GdmLocalDisplayFactory: Failed to issue method call: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying
> Mai 02 13:30:51 pluto gdm3[2282]: Child process -2518 was already dead.
> Mai 02 13:30:51 pluto gdm3[2282]: Child process 2515 was already dead.
> Mai 02 13:30:51 pluto systemd[1]: Stopped GNOME Display Manager.
> 

This means, we can't workaround this issue by dropping
Restart=always
from gdm.service


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-gnome-maintainers/attachments/20170502/19bfb16f/attachment.sig>