Your message dated Thu, 6 Nov 2025 18:23:43 -0500
with message-id
<caaajcmyisu8nkqxma6xp8q0cdypipa9j2xhxdr1stczqo6-...@mail.gmail.com>
and subject line closing old gdm3 bugs
has caused the Debian Bug report #851072,
regarding gdm3: barfs if x-x-i-evdev|mouse|synaptics is installed on Linux 4.x
kernel host
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.)
--
851072: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851072
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: gdm3
Version: 3.22.1-1
Severity: important
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
If xserver-xorg-input-[evdev|mouse|synaptics] are installed on an host running
current X, GDM3 fails to start. Removing those allows GDM to start again.
- -- System Information:
Debian Release: stretch/sid
APT prefers testing
APT policy: (1111, 'testing'), (1011, 'stable')
Architecture: i386 (i586)
Kernel: Linux 3.16.0-4-586
Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (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.43-1
ii adduser 3.115
ii dconf-cli 0.26.0-2
ii dconf-gsettings-backend 0.26.0-2
ii debconf [debconf-2.0] 1.5.59
ii gir1.2-gdm-1.0 3.22.1-1
ii gnome-session [x-session-manager] 3.22.2-1
ii gnome-session-bin 3.22.2-1
ii gnome-settings-daemon 3.22.1-1
ii gnome-shell 3.22.2-1
ii gnome-terminal [x-terminal-emulator] 3.22.1-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-1
ii libc6 2.24-8
ii libcanberra-gtk3-0 0.30-3
ii libcanberra0 0.30-3
ii libgdk-pixbuf2.0-0 2.36.2-1
ii libgdm1 3.22.1-1
ii libglib2.0-0 2.50.2-2
ii libglib2.0-bin 2.50.2-2
ii libgtk-3-0 3.22.5-1
ii libkeyutils1 1.5.9-9
ii libpam-modules 1.1.8-3.4
ii libpam-runtime 1.1.8-3.4
ii libpam-systemd 232-8
ii libpam0g 1.1.8-3.4
ii librsvg2-common 2.40.16-1
ii libselinux1 2.6-3
ii libsystemd0 232-8
ii libwrap0 7.6.q-26
ii libx11-6 2:1.6.4-2
ii libxau6 1:1.0.8-1
ii libxdmcp6 1:1.1.2-1.1
ii lsb-base 9.20161125
ii mutter [x-window-manager] 3.22.2-2
ii policykit-1 0.105-17
ii ucf 3.0036
ii x11-common 1:7.7+18
ii x11-xserver-utils 7.7+7
ii xterm [x-terminal-emulator] 327-2
Versions of packages gdm3 recommends:
ii at-spi2-core 2.22.0-5
ii desktop-base 8.0.2
ii x11-xkb-utils 7.7+3
ii xserver-xephyr 2:1.19.0-3
ii xserver-xorg 1:7.7+18
ii zenity 3.22.0-1
Versions of packages gdm3 suggests:
ii gnome-orca 3.22.2-1
ii libpam-gnome-keyring 3.20.0-3
- -- debconf information:
gdm3/daemon_name: /usr/sbin/gdm3
* shared/default-x-display-manager: gdm3
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEEyJACx3qL7GpObXOQrh+Cd8S017YFAlh2uCAACgkQrh+Cd8S0
17amEw//SCT1kfvE4uABRCpl4wu3W5HS/WaoS1ceOpMVOvICfjxpsGO/bjBRXAen
/+wNWOvmZ++NQlmaXIA+7+v7CeSiLWxGbwBAneCkb9bT2epCmS4ScJ5YHsFmDMkx
DRDrMAT0BpxgfEeraivDivt8hpYfPJdWqLjgiXWXIGOKVQjbTHy7nS8+fG8Lzrp1
yAWA4Vvk+NWfmGOyg+ofEus/Y8Zrqi3g0+MXuNhjLzsaG4kndHsPGy0sa0cr5Xpj
B5v3ocofjWt+CoYS4yWKYSJCUtdPys/JSvfXtcfqEX6lagIyYUbs1R0RQe+AHOQp
XHSozrPZ5bwmaf4oMzR4Yi8yb+tZh40Vbxzh+IldaP0F91GCH0NVvLJ5K9zDhD24
Q2/JvM2A3Cf4omXAowZIWW7xBmpYj171O8b2Rl+0ce4qj/ajrrJpOmK+IFRJi2xq
hZUmkuAdalXMk+FB2Jyiq4P9UdQQJUuhClNp4zRDk1diG7lv0/3tOWmjoV1hGsHQ
H2Wd3U+VfTWYT83RR67X36I9ZeZlVygvqtFSNio3h5zQr/i3svTIK3Yr7txBBZA7
Az1/ud2I0jQKkLYt9wEz7nQ0Jpcgiecp8HOH9Y19F6VoguzOPoKG7etC4xSOWmTe
R4rVma3oO2CIICkpaiPUVgtAQcksD+5kKqXLolkQZ1iIJR9GhJ0=
=GIre
-----END PGP SIGNATURE-----
--- 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 ---
