Acknowledgement sent
to ingenit <ingenit@zoho.com>:
New Bug report received and forwarded. Copy sent to Debian GNOME Maintainers <pkg-gnome-maintainers@lists.alioth.debian.org>.
(Thu, 09 Aug 2012 22:27:04 GMT) (full text, mbox, link).
Package: gdm3
Version: 3.4.1-2
Severity: important
After updating from Squeeze to Wheezy, the gdm login screen never appears on
boot, instead, it ends up in a blank screen with the cursor spinning.
Moving the pointer works.
Switching to a virtual console works.
Entering a X session (ie. startx) from a virtual console works.
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 3.2.0-3-686-pae (SMP w/1 CPU core)
Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages gdm3 depends on:
ii accountsservice 0.6.21-6
ii adduser 3.113+nmu3
ii dconf-gsettings-backend 0.12.1-2
ii dconf-tools 0.12.1-2
ii debconf [debconf-2.0] 1.5.44
ii dpkg 1.16.4.3
ii gir1.2-freedesktop 1.32.1-1
ii gir1.2-glib-2.0 1.32.1-1
ii gnome-session [x-session-manager] 3.4.2.1-1
ii gnome-session-bin 3.4.2.1-1
ii gnome-session-fallback [x-session-manager] 3.4.2.1-1
ii gnome-settings-daemon 3.4.2-3
ii gnome-terminal [x-terminal-emulator] 3.4.1.1-1
ii gsettings-desktop-schemas 3.4.2-1
ii libaccountsservice0 0.6.21-6
ii libatk1.0-0 2.4.0-2
ii libattr1 1:2.4.46-8
ii libaudit0 1:1.7.18-1.1
ii libc6 2.13-33
ii libcairo-gobject2 1.12.2-2
ii libcairo2 1.12.2-2
ii libcanberra-gtk3-0 0.28-4
ii libcanberra0 0.28-4
ii libdbus-1-3 1.6.0-1
ii libdbus-glib-1-2 0.100-1
ii libfontconfig1 2.9.0-6
ii libgdk-pixbuf2.0-0 2.26.1-1
ii libglib2.0-0 2.32.3-1
ii libglib2.0-bin 2.32.3-1
ii libgtk-3-0 3.4.2-2
ii libpam-modules 1.1.3-7.1
ii libpam-runtime 1.1.3-7.1
ii libpam0g 1.1.3-7.1
ii libpango1.0-0 1.30.0-1
ii librsvg2-common 2.36.1-1
ii libselinux1 2.1.9-5
ii libupower-glib1 0.9.17-1
ii libwrap0 7.6.q-23
ii libx11-6 2:1.5.0-1
ii libxau6 1:1.0.7-1
ii libxdmcp6 1:1.1.1-1
ii libxklavier16 5.2.1-1
ii libxrandr2 2:1.3.2-2
ii lsb-base 4.1+Debian7
ii metacity [x-window-manager] 1:2.34.3-2
ii policykit-1-gnome 0.105-2
ii twm [x-window-manager] 1:1.0.6-1
ii upower 0.9.17-1
ii x11-common 1:7.7+1
ii x11-xserver-utils 7.7~3
ii xterm [x-terminal-emulator] 278-1
Versions of packages gdm3 recommends:
ii at-spi 1.32.0-1
ii desktop-base 7.0.0
ii gnome-icon-theme 3.4.0-2
ii x11-xkb-utils 7.7~1
pn xserver-xephyr <none>
ii xserver-xorg 1:7.7+1
ii zenity 3.4.0-2
Versions of packages gdm3 suggests:
ii gnome-mag 1:0.16.3-1
pn gnome-orca <none>
ii gnome-shell 3.4.1-8
ii gok 2.30.0-1
ii libpam-gnome-keyring 3.4.1-4
-- debconf information:
* shared/default-x-display-manager: gdm3
gdm3/daemon_name: /usr/sbin/gdm3
Information forwarded
to debian-bugs-dist@lists.debian.org, Debian GNOME Maintainers <pkg-gnome-maintainers@lists.alioth.debian.org>: Bug#684432; Package gdm3.
(Sun, 07 Oct 2012 22:36:04 GMT) (full text, mbox, link).
Acknowledgement sent
to paul.szabo@sydney.edu.au:
Extra info received and forwarded to list. Copy sent to Debian GNOME Maintainers <pkg-gnome-maintainers@lists.alioth.debian.org>.
(Sun, 07 Oct 2012 22:36:05 GMT) (full text, mbox, link).
I see the same problem, at version 3.4.1-3, after each reboot.
I can press Atl-Ctrl-Backspace to cause the X server to die, then X
and the greeter restart correctly.
Cheers, Paul
Paul Szabo psz@maths.usyd.edu.au http://www.maths.usyd.edu.au/u/psz/
School of Mathematics and Statistics University of Sydney Australia
Information forwarded
to debian-bugs-dist@lists.debian.org, Debian GNOME Maintainers <pkg-gnome-maintainers@lists.alioth.debian.org>: Bug#684432; Package gdm3.
(Mon, 05 Nov 2012 19:48:03 GMT) (full text, mbox, link).
Acknowledgement sent
to Anton Martchukov <anton@martchukov.com>:
Extra info received and forwarded to list. Copy sent to Debian GNOME Maintainers <pkg-gnome-maintainers@lists.alioth.debian.org>.
(Mon, 05 Nov 2012 19:48:03 GMT) (full text, mbox, link).
Package: gdm3
Version: 3.4.1-4
Followup-For: Bug #684432
I am facing the same problem during one of dist-upgrades. Attaching gdm
log files (with debug enabled in daemon.conf). Unfortunately I was
not able to digest a reason out of them.
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=ru_RU.utf8, LC_CTYPE=ru_RU.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages gdm3 depends on:
ii accountsservice 0.6.21-6
ii adduser 3.113+nmu3
ii dconf-gsettings-backend 0.12.1-2
ii dconf-tools 0.12.1-2
ii debconf [debconf-2.0] 1.5.46
ii dpkg 1.16.9
ii gir1.2-freedesktop 1.32.1-1
ii gir1.2-glib-2.0 1.32.1-1
ii gnome-session [x-session-manager] 3.4.2.1-3
ii gnome-session-bin 3.4.2.1-3
ii gnome-session-fallback [x-session-manager] 3.4.2.1-3
ii gnome-settings-daemon 3.4.2+git20120925.a4c817-1
ii gnome-terminal [x-terminal-emulator] 3.4.1.1-2
ii gsettings-desktop-schemas 3.4.2-1
ii libaccountsservice0 0.6.21-6
ii libatk1.0-0 2.4.0-2
ii libattr1 1:2.4.46-8
ii libaudit0 1:1.7.18-1.1
ii libc6 2.13-35
ii libcairo-gobject2 1.12.2-2
ii libcairo2 1.12.2-2
ii libcanberra-gtk3-0 0.28-5
ii libcanberra0 0.28-5
ii libdbus-1-3 1.6.8-1
ii libdbus-glib-1-2 0.100-1
ii libfontconfig1 2.9.0-7
ii libgdk-pixbuf2.0-0 2.26.1-1
ii libglib2.0-0 2.33.12+really2.32.4-3
ii libglib2.0-bin 2.33.12+really2.32.4-3
ii libgtk-3-0 3.4.2-4
ii libpam-modules 1.1.3-7.1
ii libpam-runtime 1.1.3-7.1
ii libpam0g 1.1.3-7.1
ii libpango1.0-0 1.30.0-1
ii librsvg2-common 2.36.1-1
ii libselinux1 2.1.9-5
ii libupower-glib1 0.9.17-1
ii libwrap0 7.6.q-24
ii libx11-6 2:1.5.0-1
ii libxau6 1:1.0.7-1
ii libxdmcp6 1:1.1.1-1
ii libxklavier16 5.2.1-1
ii libxrandr2 2:1.3.2-2
ii lsb-base 4.1+Debian7
ii metacity [x-window-manager] 1:2.34.3-3
ii mutter [x-window-manager] 3.4.1-5
ii policykit-1-gnome 0.105-2
ii upower 0.9.17-1
ii x11-common 1:7.7+1
ii x11-xserver-utils 7.7~3
ii xterm [x-terminal-emulator] 278-2
Versions of packages gdm3 recommends:
ii at-spi2-core 2.5.3-2
ii desktop-base 7.0.3
ii gnome-icon-theme 3.4.0-2
ii gnome-icon-theme-symbolic 3.4.0-2
ii x11-xkb-utils 7.7~1
ii xserver-xephyr 2:1.12.4-1
ii xserver-xorg 1:7.7+1
ii zenity 3.4.0-2
Versions of packages gdm3 suggests:
pn gnome-orca <none>
ii gnome-shell 3.4.2-2
pn gok <none>
ii libpam-gnome-keyring 3.4.1-5
-- Configuration Files:
/etc/gdm3/daemon.conf changed:
[daemon]
[security]
[xdmcp]
[greeter]
[chooser]
[debug]
Enable = true
-- debconf information:
* shared/default-x-display-manager: gdm3
gdm3/daemon_name: /usr/sbin/gdm3
Information forwarded
to debian-bugs-dist@lists.debian.org, Debian GNOME Maintainers <pkg-gnome-maintainers@lists.alioth.debian.org>: Bug#684432; Package gdm3.
(Mon, 05 Nov 2012 21:45:03 GMT) (full text, mbox, link).
Acknowledgement sent
to Anton Martchukov <anton@martchukov.com>:
Extra info received and forwarded to list. Copy sent to Debian GNOME Maintainers <pkg-gnome-maintainers@lists.alioth.debian.org>.
(Mon, 05 Nov 2012 21:45:03 GMT) (full text, mbox, link).
Based on IRC discussion the reason was identified to be
pam_selinux.so plugged through /etc/pam.d/gdm3-autologin
that produces:
gdm-welcome][5739]: DEBUG(+): GdmSessionWorker: received
pam message of type 2 with payload 'Would you like to enter
a security context? [N] '
interactive prompt. On my system selinux is in permissive
mode. gdm loaded fine after I relabeled file systems.
--
Anton Martchukov
http://www.martchukov.com
Information forwarded
to debian-bugs-dist@lists.debian.org, Debian GNOME Maintainers <pkg-gnome-maintainers@lists.alioth.debian.org>: Bug#684432; Package gdm3.
(Mon, 05 Nov 2012 23:03:06 GMT) (full text, mbox, link).
Acknowledgement sent
to paul.szabo@sydney.edu.au:
Extra info received and forwarded to list. Copy sent to Debian GNOME Maintainers <pkg-gnome-maintainers@lists.alioth.debian.org>.
(Mon, 05 Nov 2012 23:03:06 GMT) (full text, mbox, link).
> ... the reason was identified to be pam_selinux.so plugged through
> /etc/pam.d/gdm3-autologin ...
I do not use autologin. Instead I commented out the selinux lines
in /etc/pam.d/gdm3 and now the very first gdmgreeter (after reboot)
works. Thanks!
Thanks, Paul
Paul Szabo psz@maths.usyd.edu.au http://www.maths.usyd.edu.au/u/psz/
School of Mathematics and Statistics University of Sydney Australia
Information forwarded
to debian-bugs-dist@lists.debian.org, Debian GNOME Maintainers <pkg-gnome-maintainers@lists.alioth.debian.org>: Bug#684432; Package gdm3.
(Mon, 05 Nov 2012 23:21:03 GMT) (full text, mbox, link).
Acknowledgement sent
to Laurent Bigonville <bigon@debian.org>:
Extra info received and forwarded to list. Copy sent to Debian GNOME Maintainers <pkg-gnome-maintainers@lists.alioth.debian.org>.
(Mon, 05 Nov 2012 23:21:03 GMT) (full text, mbox, link).
To: paul.szabo@sydney.edu.au, 684432@bugs.debian.org
Cc: anton@martchukov.com
Subject: Re: Bug#684432: SELinux is the Reason
Date: Tue, 6 Nov 2012 00:16:40 +0100
Le Tue, 6 Nov 2012 09:59:05 +1100,
paul.szabo@sydney.edu.au a écrit :
> > ... the reason was identified to be pam_selinux.so plugged through
> > /etc/pam.d/gdm3-autologin ...
>
> I do not use autologin. Instead I commented out the selinux lines
> in /etc/pam.d/gdm3 and now the very first gdmgreeter (after reboot)
> works. Thanks!
The real fix for this issue, is to properly set the security context on
the /usr/sbin/gdm3 executable.
-rwxr-xr-x. 1 root root system_u:object_r:xdm_exec_t:s0 263592 oct 20 17:53 /usr/sbin/gdm3
You should check that you have at least the
package selinux-policy-default (2:2.20110726-11) installed and relabel
your filesystem (touch /.autorelabel && reboot).
Laurent Bigonville
Information forwarded
to debian-bugs-dist@lists.debian.org, Debian GNOME Maintainers <pkg-gnome-maintainers@lists.alioth.debian.org>: Bug#684432; Package gdm3.
(Mon, 05 Nov 2012 23:39:03 GMT) (full text, mbox, link).
Acknowledgement sent
to paul.szabo@sydney.edu.au:
Extra info received and forwarded to list. Copy sent to Debian GNOME Maintainers <pkg-gnome-maintainers@lists.alioth.debian.org>.
(Mon, 05 Nov 2012 23:39:03 GMT) (full text, mbox, link).
Sorry, seems I spoke too soon. After commenting out selinux from the
/etc/pam.d/gdm3 file I "know" I rebooted and seen the greeter come
alive. But then, on further reboots, it (again, still) does not work.
I still need Atl-Ctrl-Backspace to kill that very first X server, so
subsequent gdm-session-worker goes on to spawn gdm-simple-greeter.
Cheers, Paul
Paul Szabo psz@maths.usyd.edu.au http://www.maths.usyd.edu.au/u/psz/
School of Mathematics and Statistics University of Sydney Australia
Information forwarded
to debian-bugs-dist@lists.debian.org, Debian GNOME Maintainers <pkg-gnome-maintainers@lists.alioth.debian.org>: Bug#684432; Package gdm3.
(Mon, 28 Jan 2013 15:33:04 GMT) (full text, mbox, link).
Acknowledgement sent
to Daniel Karig <dk@diy-biogas.eu>:
Extra info received and forwarded to list. Copy sent to Debian GNOME Maintainers <pkg-gnome-maintainers@lists.alioth.debian.org>.
(Mon, 28 Jan 2013 15:33:04 GMT) (full text, mbox, link).
Subject: [gdm3] blank screen: Cannot find a free VT
Date: Mon, 28 Jan 2013 16:24:49 +0100
Package: gdm3
Version: 3.4.1-5
After dist-upgrade from squeeze to wheezy gdm3 offers no login prompt
anymore. Instead the screen stays blank, the cursor keeps spinning,
while X respawned multiple times. Maybe related to #681830.
Current gdm3 log shows
> Fatal server error:
> xf86OpenConsole: Cannot find a free VT
...
> (WW) xf86CloseConsole: KDSETMODE failed: Bad file descriptor
> (WW) xf86CloseConsole: VT_GETMODE failed: Bad file descriptor
> Server terminated with error (1). Closing log file.
See attached log for details.
> The real fix for this issue, is to properly set the security context
> on the /usr/sbin/gdm3 executable.
>
> -rwxr-xr-x. 1 root root system_u:object_r:xdm_exec_t:s0 263592 oct 20
> 17:53 /usr/sbin/gdm3
# ls -l /usr/sbin/gdm3
-rwxr-xr-x 1 root root 162456 Nov 26 14:46 /usr/sbin/gdm3
> You should check that you have at least the package
> selinux-policy-default (2:2.20110726-11) installed and relabel your
> filesystem (touch /.autorelabel && reboot).
# dpkg -l |grep selinux
ii libselinux1:i386 2.1.9-5 i386
ii python-selinux 2.1.9-5 i386
Python bindings to SELinux shared libraries
ii selinux-policy-default
2:2.20110726-12 all Strict and Targeted
variants of the SELinux policy
I switched to lightdm which works fine, except user switching (#683373).
The problem with gdm3 persists.
--- System information. ---
Architecture: i386
Kernel: Linux 3.2.0-4-686-pae
Debian Release: 7.0
500 testing 127.0.0.1
--- Package information. ---
Depends (Version) | Installed
=============================================-+-================
libaccountsservice0 (>= 0.6.8) | 0.6.21-8
libatk1.0-0 (>= 1.12.4) | 2.4.0-2
libattr1 (>= 1:2.4.46-8) | 1:2.4.46-8
libaudit0 (>= 1.7.13) | 1:1.7.18-1.1
libc6 (>= 2.4) | 2.13-37
libcairo-gobject2 (>= 1.10.0) | 1.12.2-2
libcairo2 (>= 1.10.0) | 1.12.2-2
libcanberra-gtk3-0 (>= 0.25) | 0.28-6
libcanberra0 (>= 0.2) | 0.28-6
libdbus-1-3 (>= 1.0.2) | 1.6.8-1
libdbus-glib-1-2 (>= 0.88) | 0.100-1
libfontconfig1 (>= 2.9.0) | 2.9.0-7.1
libgdk-pixbuf2.0-0 (>= 2.22.0) | 2.26.1-1
libglib2.0-0 (>= 2.30.0) | 2.33.12+really2.32.4-3
libgtk-3-0 (>= 3.0.0) | 3.4.2-5
libpam0g (>= 0.99.7.1) | 1.1.3-7.1
libpango1.0-0 (>= 1.14.0) | 1.30.0-1
libselinux1 (>= 1.32) | 2.1.9-5
libupower-glib1 (>= 0.9.0) | 0.9.17-1
libwrap0 (>= 7.6-4~) | 7.6.q-24
libx11-6 | 2:1.5.0-1
libxau6 | 1:1.0.7-1
libxdmcp6 | 1:1.1.1-1
libxklavier16 (>= 5.0) | 5.2.1-1
libxrandr2 (>= 2:1.2.99.3) | 2:1.3.2-2
dconf-gsettings-backend (>= 0.12.1-2) | 0.12.1-3
debconf (>= 0.5) | 1.5.49
OR debconf-2.0 |
gir1.2-freedesktop | 1.32.1-1
gir1.2-glib-2.0 | 1.32.1-1
adduser | 3.113+nmu3
libpam-modules (>= 0.72-1) | 1.1.3-7.1
libpam-runtime (>= 0.76-13.1) | 1.1.3-7.1
gnome-session-bin (>= 3.2) | 3.4.2.1-3
gnome-settings-daemon (>= 3.2) |
3.4.2+git20121218.7c1322-2 metacity (>=
1:2.34.2) | 1:2.34.3-4 policykit-1-gnome |
0.105-2 upower | 0.9.17-1
gnome-session | 3.4.2.1-3
OR x-session-manager |
OR x-window-manager |
OR x-terminal-emulator |
lsb-base (>= 3.2-14) | 4.1+Debian8
librsvg2-common | 2.36.1-1
accountsservice (>= 0.6.12) | 0.6.21-8
gsettings-desktop-schemas | 3.4.2-3
libglib2.0-bin (>= 2.26) | 2.33.12+really2.32.4-3
dconf-tools (>= 0.12.1-2) | 0.12.1-3
x11-common (>= 1:7.6+11) | 1:7.7+1
x11-xserver-utils | 7.7~3
Recommends (Version) | Installed
========================================-+-===========
zenity | 3.4.0-2
xserver-xephyr | 2:1.12.4-4
x11-xkb-utils | 7.7~1
xserver-xorg | 1:7.7+1
at-spi2-core | 2.5.3-2
gnome-icon-theme | 3.4.0-2
gnome-icon-theme-symbolic | 3.4.0-2
desktop-base (>= 6) | 7.0.3
0
Information forwarded
to debian-bugs-dist@lists.debian.org, Debian GNOME Maintainers <pkg-gnome-maintainers@lists.alioth.debian.org>: Bug#684432; Package gdm3.
(Mon, 11 Feb 2019 02:51:02 GMT) (full text, mbox, link).
Acknowledgement sent
to Mohd Tarmize bin Ahmad <tarmize.ahmad@sprm.gov.my>:
Extra info received and forwarded to list. Copy sent to Debian GNOME Maintainers <pkg-gnome-maintainers@lists.alioth.debian.org>.
(Mon, 11 Feb 2019 02:51:02 GMT) (full text, mbox, link).
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
Bug archived.
Request was from Debbugs Internal Request <owner@bugs.debian.org>
to internal_control@bugs.debian.org.
(Fri, 05 Dec 2025 07:28:13 GMT) (full text, mbox, link).
Debbugs is free software and licensed under the terms of the GNU General
Public License version 2. The current version can be obtained
from https://bugs.debian.org/debbugs-source/.