[Expired for gdm3 (Ubuntu) because there has been no activity for 60
days.]
** Changed in: gdm3 (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878838
[Expired for gnome-shell (Ubuntu) because there has been no activity for
60 days.]
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[Expired for nvidia-graphics-drivers-440 (Ubuntu) because there has been
no activity for 60 days.]
** Changed in: nvidia-graphics-drivers-440 (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Thanks for not getting dragged down in my stupidity. I spent some more
time on this, and haven't figured out how I did something so dumb, but I
was missing vmwgfx.ko because I was missing the linux-modules-extras
package for -29 and -31. With that in place, all's well. Sorry for the
noise, just
Mike,
That would probably be a different bug. Maybe bug 1861609. Regardless,
please open a new bug so we can investigate.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878838
Title:
[nvidia]
Apologies if this is completely irrelevant, but I've also started
experiencing a black screen after login on Focal. This is in a
VirtualBox VM using the VMSVGA driver, so absolutely no Nvidia
involvement (Intel HD4600 on the host). After setting the GDM debug
option, I also see the failure to jump
Thanks, the log has
gdm-launch-environment][807]: GdmSessionWorker: couldn't finalize jump
to VT 1: Interrupted system call
unsure what is creating the problem exactly though
** Changed in: gdm3 (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a
With debug enabled, I restarted the computer and followed the same steps
with workaround. Attached logs.
** Attachment added: "logs by 'journalctl -b 0'"
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1878838/+attachment/5372016/+files/journaldebug.txt
--
You received this bug
Thank you for your bug report. Could you add your 'journalctl -b 0' log
after triggering the issue?
It would also be useful to get a log with debug enabled in
/etc/gdm3/custom.conf
** Changed in: gdm3 (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you
