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 #893567,
regarding gdm3: Unable to input some special characters in password entry
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.)
--
893567: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893567
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: gdm3
Version: 3.28.0-1
Severity: important
After the update to 3.28.0-1 I'm unable to input some special characters in the
password entry, which means that I'm unable to login in my user.
I have a ~ in my password and gdm wont input it. I use "Portuguese (Brazil)"
input source so I have to double-tap the ~ for it to be inputed or press it
once and follow by a space. This would probably happen with the "English US
intl. with dead keys" too since it functions the same for those accents.
Also, I noticed that the "Login Screen" option in "Region & Language" tab in
gnome control center is set to "No input selected". It doesn't matter if I set
one, when I restart my computer if will loose it again. Don't know if that is
related.
-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (900, 'testing'), (500, 'unstable'), (500, 'stable'), (100,
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.14.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US.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.26.1-3
ii dconf-gsettings-backend 0.26.1-3
ii debconf [debconf-2.0] 1.5.66
ii gir1.2-gdm-1.0 3.28.0-1
ii gnome-session [x-session-manager] 3.27.92-1
ii gnome-session-bin 3.27.92-1
ii gnome-settings-daemon 3.26.2-1+b1
ii gnome-shell 3.27.92-2
ii gnome-terminal [x-terminal-emulator] 3.27.92-1
ii gsettings-desktop-schemas 3.27.92-1
ii libaccountsservice0 0.6.45-1
ii libaudit1 1:2.8.2-1
ii libc6 2.27-2
ii libcanberra-gtk3-0 0.30-6
ii libcanberra0 0.30-6
ii libgdk-pixbuf2.0-0 2.36.11-1
ii libgdm1 3.28.0-1
ii libglib2.0-0 2.54.3-2
ii libglib2.0-bin 2.54.3-2
ii libgtk-3-0 3.22.28-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-2
ii libpam0g 1.1.8-3.7
ii librsvg2-common 2.40.20-2
ii libselinux1 2.7-2+b1
ii libsystemd0 238-2
ii libwrap0 7.6.q-27
ii libx11-6 2:1.6.4-3
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 metacity [x-window-manager] 1:3.26.0-1
ii mutter [x-window-manager] 3.28.0-1
ii policykit-1 0.105-18
ii ucf 3.0038
ii x11-common 1:7.7+19
ii x11-xserver-utils 7.7+7+b1
ii xterm [x-terminal-emulator] 331-1
Versions of packages gdm3 recommends:
ii at-spi2-core 2.28.0-1
ii desktop-base 9.0.5
ii x11-xkb-utils 7.7+3+b1
ii xserver-xephyr 2:1.19.6-1
ii xserver-xorg 1:7.7+19
ii zenity 3.28.0-1
Versions of packages gdm3 suggests:
ii gnome-orca 3.26.0-5
pn libpam-fprintd <none>
ii libpam-gnome-keyring 3.20.1-2
-- 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 ---
