Discussion:
Bug#940614: gdm3: GDM doesn't start (I see flickering on the console a few times until it decides it has failed)
Add Reply
Stefan Monnier
2019-09-17 19:40:02 UTC
Reply
Permalink
Package: gdm3
Version: 3.30.2-3
Severity: important

Dear Maintainer,

After the upgrade to Buster, I'm unable to get GDM3 working on this system (a thinkpad X201s).
It fails at start. I tried to change /etc/gdm3/daemon.conf to prevent use of Wayland,
but it made no noticeable difference.

I can start `xinit` from a root console login and it successfully launches the X xserver and the xterm.
I haven't found anything in the logs which gave me any hint at the origin of the problem (e.g.
the Xorg log in /var/lib/gdm3 doesn't have any EE lines, AFAICT).


Stefan


-- System Information:
Debian Release: 10.1
APT prefers stable
APT policy: (990, 'stable')
Architecture: i386 (i686)

Kernel: Linux 4.19.0-6-686-pae (SMP w/4 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=fr_CH.UTF-8, LC_CTYPE=fr_CH.UTF-8 (charmap=UTF-8), LANGUAGE=fr_CH.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.45-2
ii adduser 3.118
ii ctwm [x-window-manager] 3.7-4+b1
ii dconf-cli 0.30.1-2
ii dconf-gsettings-backend 0.30.1-2
ii debconf [debconf-2.0] 1.5.71
ii gir1.2-gdm-1.0 3.30.2-3
ii gnome-session [x-session-manager] 3.30.1-2
ii gnome-session-bin 3.30.1-2
ii gnome-settings-daemon 3.30.2-3
ii gnome-shell 3.30.2-9
ii gnome-terminal [x-terminal-emulator] 3.30.2-2
ii gsettings-desktop-schemas 3.28.1-1
ii libaccountsservice0 0.6.45-2
ii libaudit1 1:2.8.4-3
ii libc6 2.28-10
ii libcanberra-gtk3-0 0.30-7
ii libcanberra0 0.30-7
ii libgdk-pixbuf2.0-0 2.38.1+dfsg-1
ii libgdm1 3.30.2-3
ii libglib2.0-0 2.58.3-2+deb10u1
ii libglib2.0-bin 2.58.3-2+deb10u1
ii libgtk-3-0 3.24.5-1
ii libkeyutils1 1.6-6
ii libpam-modules 1.3.1-5
ii libpam-runtime 1.3.1-5
ii libpam-systemd 241-7~deb10u1
ii libpam0g 1.3.1-5
ii librsvg2-common 2.44.10-2.1
ii libselinux1 2.8-1+b1
ii libsystemd0 241-7~deb10u1
ii libwrap0 7.6.q-28
ii libx11-6 2:1.6.7-1
ii libxau6 1:1.0.8-1+b2
ii libxcb1 1.13.1-2
ii libxdmcp6 1:1.1.2-3
ii lsb-base 10.2019051400
ii metacity [x-window-manager] 1:3.30.1-2
ii mutter [x-window-manager] 3.30.2-7
ii policykit-1 0.105-25
ii procps 2:3.3.15-2
ii ucf 3.0038+nmu1
ii wmaker [x-window-manager] 0.95.8-3
ii x11-common 1:7.7+19
ii x11-xserver-utils 7.7+8
ii xfce4-session [x-session-manager] 4.12.1-6
ii xfce4-terminal [x-terminal-emulator] 0.8.7.4-2
ii xfwm4 [x-window-manager] 4.12.5-1
ii xterm [x-terminal-emulator] 344-1

Versions of packages gdm3 recommends:
ii at-spi2-core 2.30.0-7
ii desktop-base 10.0.2
ii x11-xkb-utils 7.7+4
ii xserver-xephyr 2:1.20.4-1
ii xserver-xorg 1:7.7+19
ii zenity 3.30.0-2

Versions of packages gdm3 suggests:
ii gnome-orca 3.30.1-1
pn libpam-fprintd <none>
ii libpam-gnome-keyring 3.28.2-5

-- debconf information:
gdm3/daemon_name: /usr/sbin/gdm3
* shared/default-x-display-manager: gdm3
Jeremy Bicha
2019-10-09 11:00:02 UTC
Reply
Permalink
My Gnome 3.34 on debian unstable started acting the same after gdm3 got
upgraded gdm3:amd64 (3.34.0-2, 3.34.1-1).
What I was doing before this was to try bumblebee to handle having both
intel and nvidia graphics card in this laptop. And then removing
bumblebee. Then doing a upgrade installed new version of gdm3. And now I
can not get the desktop up and running. And I have no idea how to
troubleshoot this.
gnome is now up at 3.34.1, mostly.
Jens, please file a separate bug. gnome-shell & mutter 3.34.1 were
just uploaded to unstable moments ago so maybe try those updates when
they're published. Reboot and then report the bug if you're still
affected.

Thanks,
Jeremy
philippe batailler
2019-10-10 09:10:01 UTC
Reply
Permalink
Package: gdm3
Version: 3.34.0-2
Followup-For: Bug #940614

Dear Maintainer,



* What led up to the situation?

An upgrade from testing

* What exactly did you do (or not do) that was effective (or
ineffective)?

apt upgrade

* What was the outcome of this action?

a black screen on reboot.

I tried lightdm : I only get a gnome terminal. no desktop. and i can not close
the session.
I can launch emacs firefox or reportbug...

Regards,



-- System Information:
Debian Release: bullseye/sid
APT prefers testing
APT policy: (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.2.0-3-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages gdm3 depends on:
ii accountsservice 0.6.45-2
ii adduser 3.118
ii dconf-cli 0.34.0-1
ii dconf-gsettings-backend 0.34.0-1
ii debconf [debconf-2.0] 1.5.73
ii gir1.2-gdm-1.0 3.34.0-2
ii gnome-session [x-session-manager] 3.30.1-2
ii gnome-session-bin 3.30.1-2
ii gnome-session-flashback [x-session-manager] 3.30.0-3
ii gnome-settings-daemon 3.30.2-3
ii gnome-shell 3.30.2-11
ii gnome-terminal [x-terminal-emulator] 3.34.0-1
ii gsettings-desktop-schemas 3.28.1-1
ii libaccountsservice0 0.6.45-2
ii libaudit1 1:2.8.5-2
ii libc6 2.29-2
ii libcanberra-gtk3-0 0.30-7
ii libcanberra0 0.30-7
ii libgdk-pixbuf2.0-0 2.38.2+dfsg-1
ii libgdm1 3.34.0-2
ii libglib2.0-0 2.62.0-3
ii libglib2.0-bin 2.62.0-3
ii libgtk-3-0 3.24.12-1
ii libkeyutils1 1.6-6
ii libpam-modules 1.3.1-5
ii libpam-runtime 1.3.1-5
ii libpam-systemd 242-7
ii libpam0g 1.3.1-5
ii librsvg2-common 2.44.14-1
ii libselinux1 2.9-2+b2
ii libsystemd0 242-7
ii libwrap0 7.6.q-28
ii libx11-6 2:1.6.8-1
ii libxau6 1:1.0.8-1+b2
ii libxcb1 1.13.1-2
ii libxdmcp6 1:1.1.2-3
ii lsb-base 11.1.0
ii lxqt-session [x-session-manager] 0.14.1-2
ii metacity [x-window-manager] 1:3.34.0-1
ii mutter [x-window-manager] 3.30.2-9
ii policykit-1 0.105-25
ii procps 2:3.3.15-2+b1
ii qterminal [x-terminal-emulator] 0.14.1-1
ii tilix [x-terminal-emulator] 1.8.1-1+b1
ii ucf 3.0038+nmu1
ii x11-common 1:7.7+19
ii x11-xserver-utils 7.7+8
ii xfce4-session [x-session-manager] 4.14.0-1+b1
ii xfwm4 [x-window-manager] 4.14.0-1
ii xterm [x-terminal-emulator] 349-1

Versions of packages gdm3 recommends:
ii at-spi2-core 2.34.0-3
ii desktop-base 10.0.3
ii x11-xkb-utils 7.7+4
ii xserver-xephyr 2:1.20.4-1
ii xserver-xorg 1:7.7+19
ii zenity 3.32.0-4

Versions of packages gdm3 suggests:
ii gnome-orca 3.34.0-2
pn libpam-fprintd <none>
ii libpam-gnome-keyring 3.34.0-1

-- Configuration Files:
/etc/gdm3/daemon.conf changed:
[daemon]
AutomaticLoginEnable=False
AutomaticLogin=phil
[security]
[xdmcp]
[chooser]
[debug]


-- debconf information:
* shared/default-x-display-manager: lightdm
gdm3/daemon_name: /usr/sbin/gdm3
Simon McVittie
2019-10-10 19:00:02 UTC
Reply
Permalink
Post by philippe batailler
a black screen on reboot.
ii gnome-shell 3.30.2-11
ii libgdm1 3.34.0-2
You are using testing/unstable, so please upgrade gnome-shell (and all
other GNOME packages) to at least the latest versions from testing.
There are known problems with having a mixture of GNOME 3.30 and 3.34
packages, which were fixed recently by tightening dependencies so that
this is less likely to happen.

If you still see this symptom, please open a *separate* bug, so that
your bug report about testing/unstable packages does not get mixed up
with Stefan Monnier's report about Debian 10 packages.

smcv
Philippe Batailler
2019-10-10 20:10:02 UTC
Reply
Permalink
Post by Simon McVittie
Post by philippe batailler
a black screen on reboot.
ii gnome-shell 3.30.2-11
ii libgdm1 3.34.0-2
You are using testing/unstable, so please upgrade gnome-shell (and all
other GNOME packages) to at least the latest versions from testing.
done.

Now, gnome version 3.30+2
gnome-shell 3.34.0-2

I can login with gdm3 but I get no desktop and another login page is
shown, and so on.
idem with lightdm.

I will open a separate bug report.

Regards,

Simon McVittie
2019-10-10 19:10:02 UTC
Reply
Permalink
Control: tags -1 + moreinfo
Post by Stefan Monnier
After the upgrade to Buster
A note to other people who might reply to this bug: if you are using
GNOME 3.34 in testing/unstable, or if you have any doubt about whether
the bug you're seeing is the same one Stefan reported, please report a
*separate* bug. Please reserve #940614 for discussion of the bug that
Stefan is seeing in Debian 10 'buster'.

(Normally I would retitle the bug according to a characteristic error
message, but there are no logs here yet, so I can't do that.)
Post by Stefan Monnier
I'm unable to get GDM3 working on this system (a thinkpad X201s).
It fails at start.
Sorry, this is not enough information for a developer to diagnose
problems. Please check the systemd journal (or syslog) and
attach log messages from there, along with your gdm3 configuration
(/etc/gdm3/daemon.conf) and any other information that seems potentially
relevant.

When reading the journal/syslog, please send everything from the point
at which gdm first tries to start to the point at which it "decides it
has failed".

If there is confidential/personal/otherwise sensitive information in your
log, you can censor it, but please make it obvious where you have done so
(replace it with XXXXXXX or similar).

If you try this with different configurations (e.g. Wayland and X11)
please indicate which log applies to which configuration.
Post by Stefan Monnier
I can start `xinit` from a root console login and it successfully launches the X xserver and the xterm.
I haven't found anything in the logs which gave me any hint at the origin of the problem (e.g.
the Xorg log in /var/lib/gdm3 doesn't have any EE lines, AFAICT).
I don't think the Xorg logs in /var/log/gdm3 and /var/log/Xorg* are
used any more. All gdm logging now goes to the systemd journal (and
from there to the syslog, if you have rsyslogd installed).

In Wayland mode there is no Xorg at all, only gnome-shell acting as the
Wayland compositor, with Xwayland as a compatibility layer for X11 apps.
Both of those log to the journal.
Post by Stefan Monnier
Architecture: i386 (i686)
It's possible that this is relevant: most people who test GNOME will have
done so on amd64 systems, so perhaps there is some i386-specific issue.

smcv
Loading...