Your message dated Thu, 6 Nov 2025 18:04:45 -0500
with message-id
<caaajcmzr+tpiylq1ykax3weok0kkilssqounu+duqnsh2_y...@mail.gmail.com>
and subject line closing ancient gdm3 bugs
has caused the Debian Bug report #646180,
regarding gdm3 occasionally spawns X continuously when the previous X session
terminates
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.)
--
646180: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=646180
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: gdm3
Version: 3.0.4-4
Severity: important
After upgrading gdm3, I logged out to log in again. But when starting fvwm
via my .xsession file, my fvwm config file wasn't read (and no errors were
shown in .xsession-errors -- this is where fvwm errors are usually written).
I'm not sure whether gdm3 is the culprit here, but perhaps it provided an
incorrect environment...
Then I quit fvwm, but X wasn't restarted. The Xorg.0.log file says at the
end (at the same time fvwm terminated): "Server terminated successfully".
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1,
'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.0.0-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=POSIX, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages gdm3 depends on:
ii accountsservice 0.6.15-1
ii adduser 3.113
ii dconf-gsettings-backend 0.7.5-3
ii debconf [debconf-2.0] 1.5.41
ii fvwm [x-window-manager] 1:2.5.30.ds-1
ii gconf2 2.32.4-1
ii gnome-session [x-session-manager] 3.0.2-3
ii gnome-session-bin 3.0.2-3
ii gnome-session-fallback [x-session-manager] 3.0.2-3
ii gnome-terminal [x-terminal-emulator] 3.0.1-1
ii gsettings-desktop-schemas 3.0.1-1
ii libaccountsservice0 0.6.15-1
ii libatk1.0-0 2.2.0-2
ii libattr1 1:2.4.46-3
ii libaudit0 1.7.18-1
ii libc6 2.13-21
ii libcairo-gobject2 1.10.2-6.1
ii libcairo2 1.10.2-6.1
ii libcanberra-gtk3-0 0.28-3
ii libcanberra0 0.28-3
ii libdbus-1-3 1.4.16-1
ii libdbus-glib-1-2 0.98-1
ii libfontconfig1 2.8.0-3
ii libfreetype6 2.4.6-2
ii libgconf2-4 2.32.4-1
ii libgdk-pixbuf2.0-0 2.24.0-1
ii libglib2.0-0 2.28.8-1
ii libglib2.0-bin 2.28.8-1
ii libgtk-3-0 3.0.12-2
ii libpam-modules 1.1.3-4
ii libpam-runtime 1.1.3-4
ii libpam0g 1.1.3-4
ii libpango1.0-0 1.29.4-2
ii librsvg2-common 2.34.1-2
ii libselinux1 2.1.0-1
ii libupower-glib1 0.9.14-1
ii libwrap0 7.6.q-21
ii libx11-6 2:1.4.4-2
ii libxau6 1:1.0.6-3
ii libxdmcp6 1:1.1.0-3
ii libxklavier16 5.1-2
ii libxrandr2 2:1.3.2-2
ii lsb-base 3.2-28
ii metacity [x-window-manager] 1:2.34.1-1
ii mlterm [x-terminal-emulator] 3.0.8-2
ii policykit-1-gnome 0.102-2
ii rxvt-unicode [x-terminal-emulator] 9.12-1
ii twm [x-window-manager] 1:1.0.6-1
ii upower 0.9.14-1
ii xterm [x-terminal-emulator] 276-1
Versions of packages gdm3 recommends:
ii at-spi 1.32.0-1
ii desktop-base 6.0.7
ii gnome-icon-theme 3.2.1.2-1
ii gnome-power-manager 3.0.2-2
ii gnome-settings-daemon 3.0.3-3
ii x11-xkb-utils 7.6+4
ii xserver-xephyr 2:1.11.1.901-2
ii xserver-xorg 1:7.6+9
ii zenity 3.2.0-1
Versions of packages gdm3 suggests:
ii gnome-mag <none>
ii gnome-orca <none>
ii gok <none>
ii libpam-gnome-keyring 3.0.3-2
ii metacity 1:2.34.1-1
-- 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ích
--- End Message ---
