Bug#897975: gdm3: System fails to boot due to GDM restarting constantly.

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

Bug#897975: gdm3: System fails to boot due to GDM restarting constantly.

Mladen Mijatov
Package: gdm3
Version: 3.28.1-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

After recent update system is unable to boot due to GDM3 constantly restarting.
Journal contained message "IceLockAuthFile fail: Already exists" before GDM
exiting and starting againg.

Other than this I was unable to find any other issue.

Only solution I could find to make my system usable again is to install LigthDM



-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.16.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages gdm3 depends on:
ii  accountsservice                       0.6.45-1
ii  adduser                               3.117
ii  dconf-cli                             0.28.0-2
ii  dconf-gsettings-backend               0.28.0-2
ii  debconf [debconf-2.0]                 1.5.66
ii  gir1.2-gdm-1.0                        3.28.1-1
ii  gnome-session [x-session-manager]     3.28.1-1
ii  gnome-session-bin                     3.28.1-1
ii  gnome-settings-daemon                 3.28.1-1
ii  gnome-shell                           3.28.0-1+b1
ii  gnome-terminal [x-terminal-emulator]  3.28.0-1
ii  gsettings-desktop-schemas             3.28.0-1
ii  libaccountsservice0                   0.6.45-1
ii  libaudit1                             1:2.8.2-1
ii  libc6                                 2.27-3
ii  libcanberra-gtk3-0                    0.30-6
ii  libcanberra0                          0.30-6
ii  libgdk-pixbuf2.0-0                    2.36.11-2
ii  libgdm1                               3.28.1-1
ii  libglib2.0-0                          2.56.1-2
ii  libglib2.0-bin                        2.56.1-2
ii  libgtk-3-0                            3.22.29-3
ii  libkeyutils1                          1.5.9-9.2
ii  libpam-modules                        1.1.8-3.7
ii  libpam-runtime                        1.1.8-3.7
ii  libpam-systemd                        238-4
ii  libpam0g                              1.1.8-3.7
ii  librsvg2-common                       2.40.20-2
ii  libselinux1                           2.7-2+b2
ii  libsystemd0                           238-4
ii  libwrap0                              7.6.q-27
ii  libx11-6                              2:1.6.5-1
ii  libxau6                               1:1.0.8-1+b2
ii  libxcb1                               1.13-1
ii  libxdmcp6                             1:1.1.2-3
ii  lsb-base                              9.20170808
ii  mutter [x-window-manager]             3.28.1-2
ii  policykit-1                           0.105-20
ii  ucf                                   3.0038
ii  x11-common                            1:7.7+19
ii  x11-xserver-utils                     7.7+8

Versions of packages gdm3 recommends:
ii  at-spi2-core    2.28.0-2
ii  desktop-base    9.0.5
ii  x11-xkb-utils   7.7+4
ii  xserver-xephyr  2:1.19.6-1
ii  xserver-xorg    1:7.7+19
ii  zenity          3.28.1-1

Versions of packages gdm3 suggests:
pn  gnome-orca            <none>
pn  libpam-fprintd        <none>
ii  libpam-gnome-keyring  3.28.0.2-1

-- debconf information:
* shared/default-x-display-manager: lightdm
  gdm3/daemon_name: /usr/sbin/gdm3

Reply | Threaded
Open this post in threaded view
|

Bug#897975: [gdm3]

rastersoft
Package: gdm3
Version: 3.28.1-1

More info: it also fails when booting SID with kernel 4.9.0-6 (from
Debian Stable).


--- System information. ---
Architecture:
Kernel: Linux 4.16.0-1-amd64

Debian Release: buster/sid
500 unstable ftp.debian.org

--- Package information. ---
Depends (Version) | Installed
============================================-+-===============
libaccountsservice0 (>= 0.6.37) | 0.6.45-1
libaudit1 (>= 1:2.2.1) | 1:2.8.3-1
libc6 (>= 2.14) |
libcanberra-gtk3-0 (>= 0.25) |
libcanberra0 (>= 0.2) |
libgdk-pixbuf2.0-0 (>= 2.22.0) |
libgdm1 (= 3.28.1-1) |
libglib2.0-0 (>= 2.39.4) |
libgtk-3-0 (>= 3.0.0) |
libkeyutils1 (>= 1.5.9) |
libpam0g (>= 0.99.7.1) |
libselinux1 (>= 1.32) |
libsystemd0 |
libwrap0 (>= 7.6-4~) |
libx11-6 |
libxau6 |
libxcb1 |
libxdmcp6 |
debconf (>= 0.5) |
OR debconf-2.0 |
gir1.2-gdm-1.0 (= 3.28.1-1) |
adduser |
libpam-modules (>= 0.72-1) |
libpam-runtime (>= 0.76-13.1) |
libpam-systemd |
gnome-session-bin (>= 3.10) |
gnome-settings-daemon (>= 3.24) |
gnome-shell (>= 3.19.92) |
gnome-session |
OR x-session-manager |
OR x-window-manager |
OR x-terminal-emulator |
lsb-base (>= 3.2-14) |
librsvg2-common |
accountsservice (>= 0.6.35) |
policykit-1 (>= 0.105-5~) |
gsettings-desktop-schemas |
libglib2.0-bin (>= 2.35.0) |
dconf-cli (>= 0.20) |
dconf-gsettings-backend (>= 0.20) |
ucf |
x11-common (>= 1:7.6+11) |
x11-xserver-utils |


Recommends (Version) | Installed
=============================-+-===========
zenity | 3.28.1-1
xserver-xephyr | 2:1.19.6-1
x11-xkb-utils | 7.7+4
xserver-xorg | 1:7.7+19
at-spi2-core | 2.28.0-3
desktop-base (>= 6) | 9.0.5


Suggests (Version) | Installed
=====================================-+-=============
libpam-gnome-keyring | 3.28.0.2-1
gnome-orca | 3.28.1-1
libpam-fprintd (>= 0.8.0-2) |

--
Nos leemos
                         RASTER    (Linux user #228804)
[hidden email]              http://www.rastersoft.com

Reply | Threaded
Open this post in threaded view
|

Bug#897975: gdm3: System fails to boot due to GDM restarting constantly.

Oscar Andreasson
In reply to this post by Mladen Mijatov
Hi,

I'm having the same issue and removing the. ICEAuthority* files fixed the issue here as well.

Thank you for the fix Philipp ūüėČ.

On Mon, 07 May 2018 11:08:14 +0200 Philipp Falk <[hidden email]> wrote:

> Package: gdm3
> Version: 3.22.3-3+deb9u1
> Severity: wishlist
>
> Dear Maintainer,
>
> I just wanted to confirm that I also encountered this bug on a debian
> stable installation.
>
> I also see the "ICELockAuthFile fail: Already exists" message in
> the systemd journal.
>
> Removing /var/lib/gdm3/.ICEAuthority* and restarting
> gdm.service fixed the issue temporarily until the next reboot.
>
> If wayland is enabled via /etc/gdm3/daemon.conf, gdm3 comes up after
> some waiting time (around two minutes) on a cold boot.
>
> -- System Information:
> Debian Release: 9.4
> Architecture: amd64 (x86_64)
>
> Kernel: Linux 4.9.0-6-amd64
> 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  awesome [x-window-manager]            4.0-1
> ii  dconf-cli                             0.26.0-2+b1
> ii  dconf-gsettings-backend               0.26.0-2+b1
> ii  debconf [debconf-2.0]                 1.5.61
> ii  fluxbox [x-window-manager]            1.3.5-2+b2
> ii  fvwm [x-window-manager]               1:2.6.7-3
> ii  gir1.2-gdm-1.0                        3.22.3-3+deb9u1
> 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-2+deb9u2
> ii  gnome-shell                           3.22.3-3
> ii  gnome-terminal [x-terminal-emulator]  3.22.2-1
> ii  gsettings-desktop-schemas             3.22.0-1
> ii  icewm [x-window-manager]              1.3.8+mod+20161220-1
> ii  libaccountsservice0                   0.6.43-1
> ii  libaudit1                             1:2.6.7-2
> ii  libc6                                 2.24-11+deb9u3
> ii  libcanberra-gtk3-0                    0.30-3
> ii  libcanberra0                          0.30-3
> ii  libgdk-pixbuf2.0-0                    2.36.5-2+deb9u2
> ii  libgdm1                               3.22.3-3+deb9u1
> ii  libglib2.0-0                          2.50.3-2
> ii  libglib2.0-bin                        2.50.3-2
> ii  libgtk-3-0                            3.22.11-1
> ii  libkeyutils1                          1.5.9-9
> ii  libpam-modules                        1.1.8-3.6
> ii  libpam-runtime                        1.1.8-3.6
> ii  libpam-systemd                        232-25+deb9u2
> ii  libpam0g                              1.1.8-3.6
> ii  librsvg2-common                       2.40.16-1+b1
> ii  libselinux1                           2.6-3+b3


Sent from my Huawei Mobile
Reply | Threaded
Open this post in threaded view
|

Bug#897975: [gdm3]

rastersoft
In reply to this post by Mladen Mijatov
Hi:

I'm compiling it, but is there a way of easily create a .deb package
with the compiled code? (there seems to be debian/control files, so it
seems to be something quite straight up...)

El 14/4/19 a las 16:36, Iain Lane escribió:

> Hi,
>
> Sorry for the delay. Niels pointed me at this bug, which is suspiciously
> similar to one we saw on Ubuntu around the same time ...
>
> On Wed, Jun 13, 2018 at 01:43:18PM +0200, rastersoft wrote:
>> After several tests, I started to suspect that the problem could be in the
>> firmware loading: my hypothesis is that when I use my SSD hard disk, the
>> loading is so fast that the graphic card is still not available when GDM
>> tries to boot in Wayland mode, so it fails and tries again in X11 mode. At
>> this moment it has ended loading the firmware as is available, so this mode
>> succeeds, but without offering Wayland because that failed before. If I
>> enter a session and exit, GDM is reloaded and this time the Wayland mode
>> works because the graphics card's firmware is already loaded.
>>
>> To test this I renamed /usr/sbin/gdm3 to /usr/sbin/gdm3_bin, and created a
>> little script at /usr/sbin/gdm3 that waits 3 seconds before launching the
>> true gdm3. With this quick and dirty hack everything works fine: GDM3 is
>> always shown after booting, and I have Wayland available.
>>
>> Of course, this is not a true solution: the system should wait until the
>> graphics card is fully available before continuing loading, and not just
>> "add a delay". But I think it proofs that there is some kind of race
>> condition during boot.
> Your theory is right - GDM is starting up before the DRM devices that it
> needs are available, and it doesn't handle that very well. We have a
> workaround in place in Ubuntu which seems to have fixed the bug.  There
> is actually a logind boolean property "CanGraphical" for this, that was
> introduced so display managers like GDM can wait before they start up.
> But the branch to make GDM respect this property[0] isn't yet merged
> because it is a bit unreliable so far.
>
> So I cherry-picked the Ubuntu workaround to a branch on salsa. Would you
> be able to try it please? (Test built but not tried it myself yet, so
> sorry if there's some stupid mistake.)
>
>    https://salsa.debian.org/gnome-team/gdm/commits/wip/gdm-wait-for-drm
>
> I can't test this myself. Apparently none of my machines are capable of
> tickling this bug. :(
>
> Cheers,
>
--
Nos leemos
                         RASTER    (Linux user #228804)
[hidden email]              http://www.rastersoft.com