Your message dated Sun, 29 Jan 2023 15:49:08 +0000
with message-id <Y9aVdLxfBKFAO3/j...@momentum.pseudorandom.co.uk>
and subject line Re: Bug#897975: restarts in a loop: IceLockAuthFile fail:
Already exists (race condition?)
has caused the Debian Bug report #897975,
regarding gdm3: restarts in a loop: IceLockAuthFile fail: Already exists (race
condition?)
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
897975: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897975
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
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
--- End Message ---
--- Begin Message ---
Version: 40.1-2
On Sun, 11 Dec 2022 at 09:32:28 -0500, Jeremy Bicha wrote:
> fixed 897975 40.1-2
On Fri, 18 Nov 2022 at 00:05:57 +0100, Alban Browaeys wrote:
> The wayland issue should be gone in bookworm/sid.
> As stated in https://gitlab.gnome.org/GNOME/gdm/-/issues/103,
> https://gitlab.gnome.org/GNOME/gdm/-/merge_requests/128 is merged (in
> gdm 40).
> It supersedes https://gitlab.gnome.org/GNOME/gdm/merge_requests/37
I'm marking this bug as closed in bookworm on the basis of this information
(the "fixed" command doesn't actually mark the bug as closed).
It might be possible to backport !128 to bullseye, but I'll leave that
for another time; I think we'd need input from someone who can reproduce
the issue relatively reliably, to test a backport.
> I cannot tell about the initial gdm3 "ICELockAuthFile fail: Already
> exists" Xorg related issue. It seems unrelated.
If there is still an issue in testing/unstable with similar symptoms,
please open a new bug report with as much information as possible so that
we can track it independently of what was fixed in !128.
Thanks,
smcv
--- End Message ---
