Workaround in #19 working for me so far on Ubuntu 19.04. Have done a reboot test and a powerup test so far.
Something I noticed earlier when the machine was stuck is that the machine was able to get to the point where I could ssh to it after the GUI hadn't started. The command below did bring up the GUI for me: $ sudo systemctl restart gdm3 or even $ /etc/init.d/gdm3 restart Not a better workaround, but may save from rebooting while you make the change for #19. $ cat /etc/issue.net Ubuntu 19.04 $ uname -a Linux ubuntu-am 5.0.0-15-generic #16-Ubuntu SMP Mon May 6 17:41:33 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux Here is my syslog, I do notice some activity from 'meta_kms_resources_init', mentioned in #19, in there.. Thanks for all you do! ** Attachment added: "syslog.1 from gdm3 crashing machine" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1798790/+attachment/5264671/+files/syslog_ubuntu1904.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1798790 Title: Ubuntu login screen never appears when using the Nvidia driver (and setting WaylandEnable=false fixes it) To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1798790/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
