Your message dated Thu, 6 Nov 2025 18:10:28 -0500 with message-id <CAAajCMbEGeU1s25jpEe8X6shc3ORJcSDUw=so-RFXNkWy=d...@mail.gmail.com> and subject line closing ancient gdm3 bugs has caused the Debian Bug report #778559, regarding gdm3: Login temporarily unavailable if the previous user failed login 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.) -- 778559: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778559 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: gdm3 Version: 3.14.1-3 Severity: important Dear Maintainer, * What led up to the situation? I was implementing restrictions on login times for my users using pam_time.so First, I enabled the pam_time.so by appending the following to /etc/pam.d/gdm-password account required pam_time.so Second, I added the following line to /etc/security/time.conf *;*;demo;Su1130-2130 * What was the outcome of this action? The user 'demo' can login during the time specified, but during the times not specified, login fails almost instantly, with the message: "Sorry, that didn't work. Please try again." This is the expected outcome. However, at this point, I then clicked on "Cancel" to bring me back to the user list. This worked as expected and I clicked on my user to login, but it just brought me to a blank screen as if the login widget were still loading. After about 10 to 30 seconds, I saw the login widget appear for brief moment with a message under the password box. I was unable to read the message because it disappeared too quickly. I was then taken back to the user list where I clicked on 'laverne' again and was able to log in normally. * What outcome did you expect instead? I expected that, after failure, I would be able to choose any user and log in normally. * Reproducibility It seems like I can reproduce the bug with the following steps. 1) Chose any user from the GDM user list 2) Make the login fail (by using an incorrect password) 3) Click "Cancel" or use the <ESC> key to return to the user list. 4) Chose any user. (Including the one that just failed) -Laverne -- System Information: Debian Release: 8.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.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.37-3+b1 ii adduser 3.113+nmu3 ii dconf-cli 0.22.0-1 ii dconf-gsettings-backend 0.22.0-1 ii debconf [debconf-2.0] 1.5.55 ii gir1.2-gdm3 3.14.1-3 ii gnome-session [x-session-manager] 3.14.0-2 ii gnome-session-bin 3.14.0-2 ii gnome-settings-daemon 3.14.2-2 ii gnome-shell 3.14.2-3+b1 ii gnome-terminal [x-terminal-emulator] 3.14.1-1 ii gsettings-desktop-schemas 3.14.1-1 ii libaccountsservice0 0.6.37-3+b1 ii libaudit1 1:2.4-1+b1 ii libc6 2.19-15 ii libcanberra-gtk3-0 0.30-2.1 ii libcanberra0 0.30-2.1 ii libgdk-pixbuf2.0-0 2.31.1-2+b1 ii libgdm1 3.14.1-3 ii libglib2.0-0 2.42.1-1 ii libglib2.0-bin 2.42.1-1 ii libgtk-3-0 3.14.5-1 ii libpam-modules 1.1.8-3.1 ii libpam-runtime 1.1.8-3.1 ii libpam-systemd 215-12 ii libpam0g 1.1.8-3.1 ii librsvg2-common 2.40.5-1 ii libselinux1 2.3-2 ii libsystemd0 215-12 ii libwrap0 7.6.q-25 ii libx11-6 2:1.6.2-3 ii libxau6 1:1.0.8-1 ii libxdmcp6 1:1.1.1-1+b1 ii libxrandr2 2:1.4.2-1+b1 ii lsb-base 4.1+Debian13+nmu1 ii metacity [x-window-manager] 1:3.14.3-1 ii mutter [x-window-manager] 3.14.2-1 ii policykit-1 0.105-8 ii ucf 3.0030 ii x11-common 1:7.7+7 ii x11-xserver-utils 7.7+3+b1 ii xterm [x-terminal-emulator] 312-1 Versions of packages gdm3 recommends: ii at-spi2-core 2.14.0-1 ii desktop-base 8.0.2 ii gnome-icon-theme 3.12.0-1 ii gnome-icon-theme-symbolic 3.12.0-1 ii x11-xkb-utils 7.7+1 ii xserver-xephyr 2:1.16.4-1 ii xserver-xorg 1:7.7+7 ii zenity 3.14.0-1 Versions of packages gdm3 suggests: ii gnome-orca 3.14.0-3 ii libpam-gnome-keyring 3.14.0-1+b1 -- Configuration Files: /etc/gdm3/PreSession/Default changed: PATH="/usr/bin:$PATH" synclient RTCornerButton=2 /etc/gdm3/daemon.conf changed: [daemon] [security] [xdmcp] [greeter] IncludeAll = true [chooser] [debug] /etc/pam.d/gdm-password changed: auth requisite pam_nologin.so auth required pam_succeed_if.so user != root quiet_success @include common-auth auth optional pam_gnome_keyring.so @include common-account session [success=ok ignore=ignore module_unknown=ignore default=bad] pam_selinux.so close session required pam_loginuid.so session [success=ok ignore=ignore module_unknown=ignore default=bad] pam_selinux.so open session optional pam_keyinit.so force revoke session required pam_limits.so session required pam_env.so readenv=1 session required pam_env.so readenv=1 envfile=/etc/default/locale @include common-session session optional pam_gnome_keyring.so auto_start @include common-password account required pam_time.so -- debconf information: gdm3/daemon_name: /usr/sbin/gdm3 * shared/default-x-display-manager: 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 ---
