Debian Bug report logs - #857995
respawn loop due to insufficient permissions

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Michael Biebl <biebl@debian.org>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: respawn loop due to insufficient permissions

Date: Fri, 17 Mar 2017 00:56:29 +0100

[Message part 1 (text/plain, inline)]

Package: gdm3
Version: 3.22.1-2
Severity: serious


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.

In this case systemd-logind is used and the gdm login session runs
wayland.
I suspect there is an interaction problem between gdm and logind, the
latter is responsible for handling the device permissions.

I originally noticed the problem when the gdm binary segfaulted on a
upgrade, which triggered the same behaviour.

I'm marking this as RC. gdm should recover properly from a segfaulting
binary and even more so a controlled restart should work.

Attached is the journal log.



-- System Information:
Debian Release: 9.0
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (200, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages gdm3 depends on:
ii  accountsservice                       0.6.43-1
ii  adduser                               3.115
ii  dconf-cli                             0.26.0-2+b1
ii  dconf-gsettings-backend               0.26.0-2+b1
ii  debconf [debconf-2.0]                 1.5.60
ii  gir1.2-gdm-1.0                        3.22.1-2
ii  gnome-session [x-session-manager]     3.22.3-1
ii  gnome-session-bin                     3.22.3-1
ii  gnome-settings-daemon                 3.22.2-1
ii  gnome-shell                           3.22.3-2
ii  gnome-terminal [x-terminal-emulator]  3.22.1-2
ii  gsettings-desktop-schemas             3.22.0-1
ii  i3-wm [x-window-manager]              4.13-1
ii  konsole [x-terminal-emulator]         4:16.12.0-1
ii  kwin-x11 [x-window-manager]           4:5.8.5-2
ii  libaccountsservice0                   0.6.43-1
ii  libaudit1                             1:2.6.7-1
ii  libc6                                 2.24-9
ii  libcanberra-gtk3-0                    0.30-3
ii  libcanberra0                          0.30-3
ii  libgdk-pixbuf2.0-0                    2.36.5-2
ii  libgdm1                               3.22.1-2
ii  libglib2.0-0                          2.50.3-1
ii  libglib2.0-bin                        2.50.3-1
ii  libgtk-3-0                            3.22.9-4
ii  libkeyutils1                          1.5.9-9
ii  libpam-modules                        1.1.8-3.5
ii  libpam-runtime                        1.1.8-3.5
ii  libpam-systemd                        233-4
ii  libpam0g                              1.1.8-3.5
ii  librsvg2-common                       2.40.16-1+b1
ii  libselinux1                           2.6-3
ii  libsystemd0                           233-4
ii  libwrap0                              7.6.q-26
ii  libx11-6                              2:1.6.4-3
ii  libxau6                               1:1.0.8-1
ii  libxcb1                               1.12-1
ii  libxdmcp6                             1:1.1.2-3
ii  lsb-base                              9.20161125
ii  mutter [x-window-manager]             3.22.3-2
ii  openbox [x-window-manager]            3.6.1-4
ii  plasma-workspace [x-session-manager]  4:5.8.6-2
ii  policykit-1                           0.105-17
ii  sakura [x-terminal-emulator]          3.4.0-3
ii  ucf                                   3.0036
ii  x11-common                            1:7.7+18
ii  x11-xserver-utils                     7.7+7+b1
ii  xterm [x-terminal-emulator]           327-2

Versions of packages gdm3 recommends:
ii  at-spi2-core    2.22.0-5+b1
ii  desktop-base    9.0.2
ii  x11-xkb-utils   7.7+3+b1
ii  xserver-xephyr  2:1.19.3-1
ii  xserver-xorg    1:7.7+18
ii  zenity          3.22.0-1+b1

Versions of packages gdm3 suggests:
pn  gnome-orca            <none>
ii  libpam-gnome-keyring  3.20.0-3

-- debconf information excluded

[gdm3-respawn-loop.txt (text/plain, attachment)]

Message #10 received at 857995@bugs.debian.org (full text, mbox, reply):

From: Michael Biebl <biebl@debian.org>

To: 857995@bugs.debian.org

Subject: Re: Bug#857995: respawn loop due to insufficient permissions

Date: Fri, 17 Mar 2017 01:06:55 +0100

[Message part 1 (text/plain, inline)]

Am 17.03.2017 um 00:56 schrieb Michael Biebl:
> Package: gdm3
> Version: 3.22.1-2
> Severity: serious
> 
> 
> 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


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

[signature.asc (application/pgp-signature, attachment)]

Message #17 received at 857995@bugs.debian.org (full text, mbox, reply):

From: Jeremy Bicha <jbicha@ubuntu.com>

To: 857995@bugs.debian.org

Subject: Re: Bug#857995: respawn loop due to insufficient permissions

Date: Thu, 23 Mar 2017 07:10:05 -0400

By the way, the constant respawn is really annoying when I install
stretch on VirtualBox.

I use the latest stretch testing netboot iso to install. Then I need
to boot to a command line with Internet so I can install
virtualbox-guest-x11 from sid (in order to be able to use a graphical
desktop because Debian Security doesn't want VirtualBox in stretch).
But first I have to wait 5 minutes for gdm to stop trying to load
(effectively a Denial of Service) before I can use a virtual terminal.

Thanks,
Jeremy Bicha

Message #22 received at 857995@bugs.debian.org (full text, mbox, reply):

From: Michael Biebl <biebl@debian.org>

To: 857995@bugs.debian.org, Jeremy Bicha <jbicha@ubuntu.com>

Subject: Re: Bug#857995: respawn loop due to insufficient permissions

Date: Sun, 30 Apr 2017 18:01:45 +0200

[Message part 1 (text/plain, inline)]

On Thu, 23 Mar 2017 07:10:05 -0400 Jeremy Bicha <jbicha@ubuntu.com> wrote:
> By the way, the constant respawn is really annoying when I install
> stretch on VirtualBox.
> 
> I use the latest stretch testing netboot iso to install. Then I need
> to boot to a command line with Internet so I can install
> virtualbox-guest-x11 from sid (in order to be able to use a graphical
> desktop because Debian Security doesn't want VirtualBox in stretch).
> But first I have to wait 5 minutes for gdm to stop trying to load
> (effectively a Denial of Service) before I can use a virtual terminal.

Yeah, noticed this as well. Pretty sucky user experience.
Since virtualbox is no longer available in stretch, as an alternative,
you can use xserver-xorg-legacy.

Might be a good idea if d-i installed that automatically if it detects a
VBox environment.

Michael


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

[signature.asc (application/pgp-signature, attachment)]

Message #27 received at 857995@bugs.debian.org (full text, mbox, reply):

From: Michael Biebl <biebl@debian.org>

To: 857995@bugs.debian.org

Subject: Re: Bug#857995: respawn loop due to insufficient permissions

Date: Tue, 2 May 2017 13:43:50 +0200

[Message part 1 (text/plain, inline)]

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?

[signature.asc (application/pgp-signature, attachment)]

Message #32 received at 857995@bugs.debian.org (full text, mbox, reply):

From: Michael Biebl <biebl@debian.org>

To: 857995@bugs.debian.org

Subject: Re: Bug#857995: respawn loop due to insufficient permissions

Date: Tue, 2 May 2017 14:12:54 +0200

[Message part 1 (text/plain, inline)]

Am 02.05.2017 um 13:43 schrieb Michael Biebl:

> 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:

Which seems to be a result of the session scope of Debian-gdm not being
stopped when the gdm service is stopped, so if you run systemctl stop
gdm.service, the session scope is still running, along with all its
processes:

> │ └─user-109.slice
> │   ├─user@109.service
> │   │ ├─at-spi-dbus-bus.service
> │   │ │ ├─5156 /usr/lib/at-spi2-core/at-spi-bus-launcher
> │   │ │ ├─5161 /usr/bin/dbus-daemon --config-file=/usr/share/defaults/at-spi2/accessibility.conf --nofork --print-address 3
> │   │ │ └─5163 /usr/lib/at-spi2-core/at-spi2-registryd --use-gnome-session
> │   │ ├─dbus.service
> │   │ │ ├─5133 /usr/bin/dbus-daemon --session --address=systemd: --nofork --nopidfile --systemd-activation
> │   │ │ └─5174 /usr/lib/x86_64-linux-gnu/gconf/gconfd-2
> │   │ ├─xdg-permission-store.service
> │   │ │ └─5180 /usr/lib/flatpak/xdg-permission-store
> │   │ └─init.scope
> │   │   ├─5126 /lib/systemd/systemd --user
> │   │   └─5127 (sd-pam)
> │   └─session-c4.scope
> │     ├─5122 gdm-session-worker [pam/gdm-launch-environment]
> │     ├─5131 /usr/lib/gdm3/gdm-wayland-session gnome-session --autostart /usr/share/gdm/greeter/autostart
> │     ├─5135 /usr/lib/gnome-session/gnome-session-binary --autostart /usr/share/gdm/greeter/autostart
> │     ├─5143 /usr/bin/gnome-shell
> │     ├─5149 /usr/bin/Xwayland :1024 -rootless -noreset -listen 4 -listen 5 -displayfd 6
> │     ├─5169 /usr/bin/pulseaudio --start --log-target=syslog
> │     ├─5172 /usr/lib/x86_64-linux-gnu/pulse/gconf-helper
> │     └─5189 /usr/lib/gnome-settings-daemon/gnome-settings-daemon

As a workaround, I added
ExecStopPost=/bin/loginctl kill-user Debian-gdm
to gdm.service. This seems enough to make
systemctl restart gdm.service
work


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

[signature.asc (application/pgp-signature, attachment)]

Message #39 received at 857995-close@bugs.debian.org (full text, mbox, reply):

From: Michael Biebl <biebl@debian.org>

To: 857995-close@bugs.debian.org

Subject: Bug#857995: fixed in gdm3 3.22.3-2

Date: Tue, 09 May 2017 22:19:12 +0000

Source: gdm3
Source-Version: 3.22.3-2

We believe that the bug you reported is fixed in the latest version of
gdm3, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 857995@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Michael Biebl <biebl@debian.org> (supplier of updated gdm3 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Tue, 09 May 2017 23:51:57 +0200
Source: gdm3
Binary: gdm3 libgdm1 libgdm-dev gir1.2-gdm-1.0
Architecture: source
Version: 3.22.3-2
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers <pkg-gnome-maintainers@lists.alioth.debian.org>
Changed-By: Michael Biebl <biebl@debian.org>
Description:
 gdm3       - GNOME Display Manager
 gir1.2-gdm-1.0 - GObject introspection data for the GNOME Display Manager
 libgdm-dev - GNOME Display Manager (development files)
 libgdm1    - GNOME Display Manager (shared library)
Closes: 857995
Changes:
 gdm3 (3.22.3-2) unstable; urgency=medium
 .
   [ Laurent Bigonville ]
   * d/p/stop-greeter-explicitly-when-finishing-display.patch: Properly stop
     the greeter processes when restarting gdm, this fixes the respawn loop and
     allow gdm to restart properly (Closes: #857995)
 .
   [ Michael Biebl ]
   * Setup pulseaudio to run as systemd user service for Debian-gdm.
     Otherwise, if we start pulseaudio within the session, the idle-timeout of
     pulseaudio will prevent the old session scope to be properly terminated
     when the gdm service is restarted and the old logind session will remain
     in state "closing".
Checksums-Sha1:
 1d820a721b649172e4039da32ca2ae20f9168a3b 3082 gdm3_3.22.3-2.dsc
 62002292378bb200e2c346f51d8fab007e81864e 86296 gdm3_3.22.3-2.debian.tar.xz
 aa5982e46cbcde02ff0dffe9f7282eab70fd3b24 16463 gdm3_3.22.3-2_source.buildinfo
Checksums-Sha256:
 8bede4ecad4cb6d2df5f4d02acd1b0d4d942f98db875309263487c591dd8feb2 3082 gdm3_3.22.3-2.dsc
 56b143197a07bd4657e82e407e292c4c2f1266f827982b159f35e0598512e9ec 86296 gdm3_3.22.3-2.debian.tar.xz
 6ccd3e9a875d1c9764404af5af7f92c596c2cd9081bdb60a11b8d3c3462aa94c 16463 gdm3_3.22.3-2_source.buildinfo
Files:
 035824498a2185409a012033e254ff18 3082 gnome optional gdm3_3.22.3-2.dsc
 36e49ccf180e479e73d827c4335b7fad 86296 gnome optional gdm3_3.22.3-2.debian.tar.xz
 a352cff43c2e1c33c1f3063f13b3f97d 16463 gnome optional gdm3_3.22.3-2_source.buildinfo

-----BEGIN PGP SIGNATURE-----

iQJFBAEBCAAvFiEECbOsLssWnJBDRcxUauHfDWCPItwFAlkSPLARHGJpZWJsQGRl
Ymlhbi5vcmcACgkQauHfDWCPItwe6BAAlr03oBgrAECHTGtptZ9IxnvFY/MO2PQm
HFRbmZwedn5PoNoqpBQnvtR2nm2vgwf592EL21UlZBWtZGLadrBe3BlmUqm2fQiC
+Jsk57ATUO4/3Km5I0+3V+0aYHvcHVbGVpu/ktWdkGEwgY6It53GtXP2OYj3hIZ8
MctcQvmff7i0W1KdCH0l0iQKLKNi48tBOa7K1fq7ORzFuLSo9N1SiuR3674vxWea
bWa81sPZxVnkgqjzhnfkkxvS0L5jazKDNUtbUhmFkNyVuiVto1NIQEKCvwFpDX1T
c9857AW7T02t6cN8EBj7KnEB16SN6MmlGV/q4v/Qzrx1QDobQQ0R1Xo54uw0RByf
Dg2gbeAEsxE1e8GKPthAZ6zpbb+j2EHv64+x1agkfbaOLCnvVb3E5HPu1xJdFZcG
Yma1c9xmupMnB1FB/9aHqe5cg1LljBmYhVF7zZy1bc+0hYLE/yyZuWShvcrky/xS
Ur79x+p0A3ZBtWF+o3Fnl9mgHaBjhn6pZRic+URjQzM8OK5EjFiZ2mHzsOtVDKlu
a9ipXe1yH0DeZBUxtOjoF1+1X1xo1+Gs2N2qKcan+4vR9hQ1CRxDpaXOKJDpjE+r
75v1x9ZVTEgEMj8BklA0vzD3z+wuu+fnwWsjUjeOvzRa02+FKu9Yom/BZccvLIsd
FE9u0SYROtE=
=2sPM
-----END PGP SIGNATURE-----

Send a report that this bug log contains spam.