Your message dated Sun, 9 Nov 2025 18:07:02 -0500
with message-id 
<caaajcmzeawhbb7e2vxri1qxlxxh9zrq5ldqjzgfpnrgyzgy...@mail.gmail.com>
and subject line closing old gdm3 bugs
has caused the Debian Bug report #778990,
regarding gdm3 login crashes when logging in to gnome-shell
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.)


-- 
778990: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778990
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: gdm3
Version: 3.14.1-3
Severity: normal

Dear Maintainer,


I upgraded my system from Wheezy to Jessie a few months ago, but as of a few 
weeks I cannot
log in to gnome-shell from gdm3 anymore. Changing the session to Gnome on 
Wayland does log 
me in to a Wayland session, but the normal Gnome login causes a segfault:

pool[3144]: segfault at 198 ip 00007fc31a3c24a4 sp 00007fc315857d58 error 4 in 
libc-2.19.so[7fc31a346000+19f000]

The strange thing is that sometimes it's in libc, and sometimes it's in 
freetype.
I tried logging in into a fresh account, but that doesn't change anything. A 
fresh install on
a separate disk does not have the problem.

Curiously, going to tty1 and running startx gets me a gnome-shell just fine.
Gnome-session, however does not work from a tty to start a gnome session.

I have asked around on IRC, but after plenty of digging nothing has come up, 
and segfaults point to a code or linking error. Aside from the segfault I
don't get anything useful in the logs to point me to the origin of this bug.

If this was reported earlier on, I could not find it in the current bug list,
and if this is a configuration error, I'm sorry for reporting a bug, however,
a configuration error should ofcourse not lead to constant segfaults, which
would be a bug by itself.

Thanks.

-- System Information:
Debian Release: 8.0
  APT prefers testing-updates
  APT policy: (500, 'testing-updates'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.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-13
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-11
ii  libpam0g                              1.1.8-3.1
ii  librsvg2-common                       2.40.5-1
ii  libselinux1                           2.3-2
ii  libsystemd0                           215-11
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/Init/Default [Errno 2] No such file or directory: 
u'/etc/gdm3/Init/Default'
/etc/gdm3/PostLogin/Default.sample [Errno 2] No such file or directory: 
u'/etc/gdm3/PostLogin/Default.sample'
/etc/gdm3/PostSession/Default [Errno 2] No such file or directory: 
u'/etc/gdm3/PostSession/Default'
/etc/gdm3/PreSession/Default [Errno 2] No such file or directory: 
u'/etc/gdm3/PreSession/Default'
/etc/gdm3/Xsession [Errno 2] No such file or directory: u'/etc/gdm3/Xsession'
/etc/gdm3/daemon.conf [Errno 2] No such file or directory: 
u'/etc/gdm3/daemon.conf'

-- 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Ă­cha

--- End Message ---

Reply via email to