gdm doesn't start on a fresh installation of Cosmic Desktop
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gdm3 (Ubuntu) |
Critical
|
Marco Trevisan (Treviño) | |||
Cosmic |
Critical
|
Marco Trevisan (Treviño) | |||
kmod (Ubuntu) |
Undecided
|
Unassigned | |||
Cosmic |
Undecided
|
Unassigned | |||
linux (Ubuntu) |
Undecided
|
Unassigned | |||
Cosmic |
Undecided
|
Unassigned | |||
xorg-server (Ubuntu) |
Critical
|
Unassigned | |||
Cosmic |
Critical
|
Unassigned | |||
xserver-xorg-video-fbdev (Ubuntu) |
Undecided
|
Unassigned | |||
Cosmic |
Undecided
|
Unassigned |
Bug Description
ubuntu cosmic desktop 20180925
After installation gdm fails to start and there is only a black screen with a blinking cursor on the top left of the screen.
gdm3 can be started manually from a tty.
Switching to another tty then back also starts gdm.
It happens on bare metal and VM.
Originally, when this issue happened there was a plymouth crash reported in bug 1794292 but this issue is still happening without the plymouth crash.
ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: gdm3 3.30.0-0ubuntu2
ProcVersionSign
Uname: Linux 4.18.0-7-generic x86_64
ApportVersion: 2.20.10-0ubuntu11
Architecture: amd64
Date: Tue Sep 25 13:54:45 2018
InstallationDate: Installed on 2018-09-25 (0 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180925)
ProcEnviron:
TERM=linux
PATH=(custom, no user)
LANG=fr_FR.UTF-8
SHELL=/bin/bash
SourcePackage: gdm3
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile.
Related branches
- Ubuntu Desktop: Pending requested 2018-10-16
-
Diff: 312 lines (+196/-14)6 files modifieddebian/changelog (+9/-0)
debian/patches/series (+1/-0)
debian/patches/ubuntu/gdm3.service-wait-for-drm-device-before-trying-to-start-i.patch (+169/-0)
debian/patches/ubuntu_config_error_dialog.patch (+5/-5)
debian/patches/ubuntu_nvidia_prime.patch (+5/-5)
debian/patches/ubuntu_revert_nvidia_wayland_blacklist.patch (+7/-4)
Jean-Baptiste Lallement (jibel) wrote : | #1 |
Jean-Baptiste Lallement (jibel) wrote : | #2 |
Iain Lane (laney) wrote : | #3 |
marco's going to look at this
for what it's worth, I tried with today's daily and didn't manage to reproduce (virt-manager/qemu, cosmic host, qxl)
Changed in gdm3 (Ubuntu): | |
assignee: | nobody → Marco Trevisan (Treviño) (3v1n0) |
Changed in gdm3 (Ubuntu Cosmic): | |
importance: | Undecided → Critical |
Jean-Baptiste Lallement (jibel) wrote : | #4 |
Lowering because it is not reproducible. It seems that first boot takes a lot of time but eventually gdm will start.
Changed in gdm3 (Ubuntu Cosmic): | |
importance: | Critical → High |
Jean-Baptiste Lallement (jibel) wrote : | #5 |
reproduced again.
Changed in gdm3 (Ubuntu Cosmic): | |
importance: | High → Critical |
Ubuntu QA Website (ubuntuqa) wrote : | #6 |
This bug has been reported on the Ubuntu ISO testing tracker.
A list of all reports related to this bug can be found here:
http://
tags: | added: iso-testing |
Launchpad Janitor (janitor) wrote : | #7 |
Status changed to 'Confirmed' because the bug affects multiple users.
Changed in gdm3 (Ubuntu): | |
status: | New → Confirmed |
Łukasz Zemczak (sil2100) wrote : | #8 |
I have reproduced it running the beta image on a local kvm instance. Command line used:
kvm -cdrom cosmic-
Got the black screen + blinking cursor on first boot. Trying to see if gdm will eventually start.
Marco Trevisan (Treviño) (3v1n0) wrote : | #9 |
Still I can't find a way to reproduce this here...
Using that command fails here as probably my user isn't part of libvirtd or something similar (I'm getting qemu-system-x86_64: failed to initialize KVM: Permission denied).
While installing from virt-manager seem to work properly.
If you've machines with reproducible results, sharing an image (shrinked) would be the only way I think.
Jean-Baptiste Lallement (jibel) wrote : | #10 |
@Marco, can you try to deselect "Download updates" and select "Minimal installation"?
Jean-Baptiste Lallement (jibel) wrote : | #11 |
There is also the crash reported in bug 1794292 when this happens. Not sure if it's related or not
description: | updated |
tags: | added: rls-cc-incoming |
tags: |
added: rls-cc-tracking removed: rls-cc-incoming |
Marco Trevisan (Treviño) (3v1n0) wrote : | #12 |
Jean-Baptiste, that's what I did... It's the 4th time now. But still, no way to reproduce here (in a bionic host, if that matters).
Any kvm config I should set?
Marco Trevisan (Treviño) (3v1n0) wrote : | #13 |
Soooo... Running from kvm itself it seems that this is reproducible but seems related to some lower level issue (both using sil's command and adding -vga qxl):
journalctl: https:/
xorg.log: https:/
In both wayland and xorg tries to get a drm device, but that's not set..
Generally when using `-vga gxl` this issue is happening in a randomic way, while it's 100% happening when using the default vga (std, or just not passing it) that is actually using vbe.
So, the weird thing here is that with the same kvm vga configurations, we get a working session when just booting from the cdrom.
For some reason it looks like that the vbe driver for X isn't even tried in this case; compare Xorg.log above with the one when booting from livecd: https:/
Then I think this is indeed not a gdm bug per se.
Changed in gdm3 (Ubuntu Cosmic): | |
status: | Confirmed → Won't Fix |
Marco Trevisan (Treviño) (3v1n0) wrote : | #14 |
FYI to reproduce I've done this:
# Create the disk
qemu-img create -f qcow2 /tmp/disk.qcow2 10G
# Boot from the iso and install
kvm -drive if=virtio,
# After install... Then run with just:
kvm -drive if=virtio,
As said passing `-vga std` is optional, but I never got issues with `-vga vmware`, while it sometimes fails also with `-vga qxl`
# Can pass -netdev user,id=
Marco Trevisan (Treviño) (3v1n0) wrote : | #15 |
Ah, one more thing to notice, if starting in recovery mode from grub, and then resuming the run, it was always working (with std vga too).
Thus this looks like a race in initializing the things that xorg needs to initialize vbe driver
Changed in gdm3 (Ubuntu): | |
status: | Confirmed → Won't Fix |
Changed in xorg (Ubuntu Cosmic): | |
importance: | Undecided → Critical |
Timo Aaltonen (tjaalton) wrote : | #16 |
The difference between live-image and installed system is that the live-image session doesn't have /dev/fb0 around while an installed system does (by efifb). I've no idea why that is.
but for some reason fbdev fails to use that device set up by efifb
Timo Aaltonen (tjaalton) wrote : | #17 |
and compared to Debian, our kernel doesn't seem to enable bochs-drm because of an old bug
https:/
which probably should be re-enabled by now
Changed in linux (Ubuntu Cosmic): | |
status: | New → Confirmed |
Timo Aaltonen (tjaalton) wrote : | #18 |
while enabling bochs-drm just works around the actual bug, I think it's best for cosmic at this stage
Timo Aaltonen (tjaalton) wrote : | #19 |
and again comparing to Debian, it doesn't have efifb messing around at any stage, though it's enabled in the kernel config
Launchpad Janitor (janitor) wrote : | #20 |
Status changed to 'Confirmed' because the bug affects multiple users.
Changed in xorg-server (Ubuntu Cosmic): | |
status: | New → Confirmed |
Changed in xorg-server (Ubuntu): | |
status: | New → Confirmed |
affects: | xorg (Ubuntu Cosmic) → xorg-server (Ubuntu Cosmic) |
Michael (cerberus-ace) wrote : | #22 |
Hi - new here, can confirm that this issue also occurs when logging out. Black screen and hardware completely unresponsive. How can I contribute my system details?
Launchpad Janitor (janitor) wrote : | #23 |
Status changed to 'Confirmed' because the bug affects multiple users.
Changed in kmod (Ubuntu): | |
status: | New → Confirmed |
Changed in xorg-server (Ubuntu): | |
status: | New → Confirmed |
Timo Aaltonen (tjaalton) wrote : | #25 |
I've moved linux/kmod tasks to enable bochs-drm to bug 1795857
Changed in linux (Ubuntu Cosmic): | |
status: | Confirmed → Invalid |
Changed in kmod (Ubuntu Cosmic): | |
status: | Confirmed → Invalid |
Timo Aaltonen (tjaalton) wrote : | #26 |
the issue seen with kvm -vga std is a regression in x-x-v-fbdev 0.5.0, same thing happens on bionic if that version is used there. It doesn't have a huge number of commits, so it should be easy to bisect.
Timo Aaltonen (tjaalton) wrote : | #27 |
well, bisected already, will discuss with upstream tomorrow
Daniel van Vugt (vanvugt) wrote : | #28 |
@jibel, as a workaround can you please test if switching VTs kicks the machine into action? Just Alt+F2, Alt+F1, and maybe then the login screen will appear. If that works for you then maybe we can declare bug 1795637 a duplicate of this one.
Launchpad Janitor (janitor) wrote : | #29 |
This bug was fixed in the package xserver-
---------------
xserver-
* revert-
with gfxpayload=keep. (LP: #1794280)
-- Timo Aaltonen <email address hidden> Thu, 04 Oct 2018 10:11:49 +0300
Changed in xserver-xorg-video-fbdev (Ubuntu Cosmic): | |
status: | New → Fix Released |
Marco Trevisan (Treviño) (3v1n0) wrote : | #30 |
It still seem to crash in my kvm installation:
ubuntu@
xserver-
Installed: 1:0.5.0-1ubuntu1
Candidate: 1:0.5.0-1ubuntu1
Version table:
*** 1:0.5.0-1ubuntu1 500
500 http://
100 /var/lib/
See attached journalctl that includes the Xorg.log
It's also weird that using `std` driver works in live, while not once installed.
Xavier Guillot (valeryan-24) wrote : | #31 |
Hi,
I have the same problem since 3 weeks on a fresh install of Ubuntu Cosmic, with Wayland session enabled by default : 2/3 of the time, login screen doesn't appear and screen remains black, pushing power button makes Ubuntu background visible again and computer stops.
I join some Auth.log since 17th September, here is an extract - will do some further tests :
Session c1 logged out. Waiting for processes to exit.
Unregistered Authentication Agent for unix-session:c1 (system bus name :1.35, object path /org/freedeskto
Removed session c1.
session closed for user gdm
session opened for user root by (uid=1000)
Executing command [USER=root] [TTY=unknown] [CWD=/home/
Operator of unix-session:2 successfully authenticated as unix-user:
asked to register item /org/freedeskto
[system] Failed to activate service 'org.bluez': timed out (service_
Registered Authentication Agent for unix-session:2 (system bus name :1.190 [/usr/bin/
New seat seat0.
pam_unix(
New session c1 of user gdm.
session opened for user gdm by (uid=0)
gdm-launch-
Session c1 logged out. Waiting for processes to exit.
Removed session c1.
pam_unix(
New session c2 of user gdm.
pam_systemd(
session closed for user gdm
session opened for user gdm by (uid=0)
pam_unix(
Session c2 logged out. Waiting for processes to exit.
Removed session c2.
systemd: pam_unix(
systemd-
systemd-
systemd-
Will Cooke (willcooke) wrote : | #32 |
Could be related to this:
https:/
description: | updated |
description: | updated |
Changed in gdm3 (Ubuntu): | |
status: | Won't Fix → Incomplete |
Changed in gdm3 (Ubuntu Cosmic): | |
status: | Won't Fix → Incomplete |
Launchpad Janitor (janitor) wrote : | #33 |
This bug was fixed in the package gdm3 - 3.30.1-1ubuntu5
---------------
gdm3 (3.30.1-1ubuntu5) cosmic; urgency=medium
* Remove accidental addition of Install/Alias info in gdm service file.
-- Adam Conrad <email address hidden> Tue, 16 Oct 2018 14:06:38 -0600
Changed in gdm3 (Ubuntu Cosmic): | |
status: | Incomplete → Fix Released |
Sebastien Bacher (seb128) wrote : | #34 |
the bug got fixed in xorg, there is no need to target an xorg fix to cosmic
Changed in xorg-server (Ubuntu Cosmic): | |
status: | Confirmed → Invalid |
tags: | added: cscc |
journal from a failed boot