Your message dated Mon, 24 Nov 2025 12:29:07 -0500 with message-id <CAAajCMbvz=jVeLBNOgvc53X3pbs3yWBps1=0xvof3ummxpq...@mail.gmail.com> and subject line closing old gdm3 bugs has caused the Debian Bug report #730862, regarding gdm3 fails with the "Oh No! Something went wrong" message with Xephyr and vncserver 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.) -- 730862: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=730862 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: gdm3 Version: 3.8.4-6 Severity: normal Tags: upstream Dear Maintainer, *** Please consider answering these questions, where appropriate *** gdm3 works well on a real display. However I get the "Oh No! Something went wrong" message when I use it with Xephyr or vncserver. (I use GDM 3.8.4) To get the problem: 1) edit /etc/gdm3/daemon.conf to add [xdmcp] Enable = true 2) then do: Xephyr -query localhost :1 Best regards Christophe -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.10-3-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages gdm3 depends on: ii accountsservice 0.6.34-2 ii adduser 3.113+nmu3 ii dconf-cli 0.18.0-1 ii dconf-gsettings-backend 0.18.0-1 ii debconf [debconf-2.0] 1.5.52 ii fluxbox [x-window-manager] 1.3.5-1 ii fvwm [x-window-manager] 1:2.6.5.ds-3 ii gir1.2-gdm3 3.8.4-6 ii gnome-session [x-session-manager] 3.8.4-3 ii gnome-session-bin 3.8.4-3 ii gnome-session-flashback [x-session-manager] 3.6.2-2 ii gnome-settings-daemon 3.8.5-2 ii gnome-shell 3.8.4-5 ii gnome-terminal [x-terminal-emulator] 3.10.1-1 ii gsettings-desktop-schemas 3.8.2-2 ii libaccountsservice0 0.6.34-2 ii libatk1.0-0 2.10.0-2 ii libaudit1 1:2.3.2-2 ii libc6 2.17-93 ii libcairo-gobject2 1.12.16-2 ii libcairo2 1.12.16-2 ii libcanberra-gtk3-0 0.30-2 ii libcanberra0 0.30-2 ii libgdk-pixbuf2.0-0 2.28.2-1 ii libgdm1 3.8.4-6 ii libglib2.0-0 2.36.4-1 ii libglib2.0-bin 2.36.4-1 ii libgtk-3-0 3.8.4-1 ii libpam-modules 1.1.3-9 ii libpam-runtime 1.1.3-9 ii libpam-systemd 204-5 ii libpam0g 1.1.3-9 ii libpango-1.0-0 1.36.0-1 ii libpangocairo-1.0-0 1.36.0-1 ii librsvg2-common 2.40.0-1 ii libselinux1 2.2.1-1 ii libwrap0 7.6.q-24 ii libx11-6 2:1.6.2-1 ii libxau6 1:1.0.8-1 ii libxdmcp6 1:1.1.1-1 ii libxrandr2 2:1.4.1-1 ii lsb-base 4.1+Debian12 ii metacity [x-window-manager] 1:2.34.13-1 ii miwm [x-window-manager] 1.1-3 ii mutter [x-window-manager] 3.8.4-2 ii terminator [x-terminal-emulator] 0.97-2 ii twm [x-window-manager] 1:1.0.6-1 ii upower 0.9.23-2+b1 ii x11-common 1:7.7+4 ii x11-xserver-utils 7.7+1 ii xterm [x-terminal-emulator] 297-1 Versions of packages gdm3 recommends: ii at-spi2-core 2.10.1-1 ii desktop-base 7.0.3 ii gnome-icon-theme 3.10.0-1 ii gnome-icon-theme-symbolic 3.10.1-1 ii x11-xkb-utils 7.7~1 ii xserver-xephyr 2:1.14.3-4 ii xserver-xorg 1:7.7+4 ii zenity 3.8.0-1 Versions of packages gdm3 suggests: pn gnome-orca <none> ii libpam-gnome-keyring 3.8.2-2 -- Configuration Files: /etc/gdm3/daemon.conf changed: [daemon] [security] [xdmcp] Enable = true [greeter] [chooser] [debug] -- 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 ---
