Your message dated Thu, 6 Nov 2025 18:16:44 -0500
with message-id
<caaajcmacrwvjkig+pho7tq88hwgrsvkkf0mj3eickup_1h1...@mail.gmail.com>
and subject line closing old gdm3 bugs
has caused the Debian Bug report #898698,
regarding gdm3: GDM logon fails for some users: "Could not finalize jump to vt1"
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 [email protected]
immediately.)
--
898698: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898698
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: gdm3
Version: 3.28.1-1
Severity: important
Some users after logging on are returned to the login screen after a few
seconds. In /var/log/syslog I find:
GdmSessionWorker: couldn't finalize jump to VT 1: Unterbrechung während des
Betriebssystemaufrufs
(that's "Interruption during the operating system call")
I have already deleted everything related to session and session state for
those users, but this doesn't seem to make a difference. So I am pretty lost
where to search further. This is observed both with the Wayland and the X
session of GNOME
-- System Information:
Debian Release: buster/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.16.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8),
LANGUAGE=de_DE.UTF-8 (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.1-1
ii gnome-terminal [x-terminal-emulator] 3.28.1-2
ii gsettings-desktop-schemas 3.28.0-1
ii libaccountsservice0 0.6.45-1
ii libaudit1 1:2.8.3-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.30-1
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-3
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
-- Configuration Files:
/etc/gdm3/daemon.conf changed:
[daemon]
[security]
[xdmcp]
[chooser]
[debug]
Enable=true
-- debconf information:
* shared/default-x-display-manager: gdm3
gdm3/daemon_name: /usr/sbin/gdm3
--- End Message ---
--- Begin Message ---
There have been many changes to Debian since this bug was originally
reported. If you are still experiencing this issue with Debian 13 (or
with Debian 12 or Testing or Unstable), please report a new bug.
Thank you,
Jeremy Bícha
--- End Message ---
