`sudo killall -9 gdm` immediately fixes the "unresponsive" problem for
me. But you have to SSH into the box to do this, which is an extreme
bandaid
The screen remains blank even moving the mouse around for a few minutes,
and pressing ESC a couple times.
The monitor shows as "no input"
--
You re
Thank you for reporting this bug to Ubuntu.
Ubuntu 19.04 (disco) reached end-of-life on January 23, 2020.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: mutter (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/182
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gdm3 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/18245
This problem is probably related to:
"Following Mutter's 3.32.1 release, meanwhile, the developers have now
hard-enforced a requirement that graphics drivers on the system either
support OpenGL 2.1 or OpenGL ES 2.0 as a minimum."
[https://www.phoronix.com/scan.php?page=news_item&px=GNOME-Shell-
M
I will follow up ASAP. The plot continues to thicken. I tried a
different set of hardware today with a B43 chipset and it didn't seem to
be effected. But that board has only DVI and VGA outputs whereas the
effected board with a G43 chipset has DVI and HDMI. I'd been using HDMI
so now I ran another
That sounds like a different bug; the login screen never appearing.
Although both bugs might end up benefiting from a single fix.
I wonder if you could log that as a new bug, so that other people
experiencing the same symptoms don't get confused?...
> Then the first boot will be OK but each subse
Sadly /var/crash is empty, and errors.ubuntu.com + whoopsie-id just
displays a blank page. Also applying the workaround from bug 994921 does
not result in creating a crash report.
I started testing Ubuntu Disco 20190416 tonight and knowing what I know
now I can say with certainty that the easiest
Thanks. This appears to be the most interesting part of the log I can
see:
Apr 15 22:22:50 lance-desktop gnome-shell[865]: Failed to initialize
accelerated iGPU/dGPU framebuffer sharing: No matching EGL configs
Apr 15 22:22:50 lance-desktop gnome-shell[865]: Failed to apply DRM plane
transform 0
Based on those most recent results I ran "dpkg-reconfigure grub-pc" and
removed "quiet splash". Now it boots to the gdm3 screen every time. So
maybe something to do with how plymouth hands off the boot process to
gdm3? Or how quickly that hand off is completed?
--
You received this bug notificati
** Summary changed:
- Ubuntu Disco boots to or logs out to black screen
+ With AutomaticLogin enabled, logging out lands me on a black screen that's
unresponsive to any keyboard input
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to g
11 matches
Mail list logo
