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 Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1798790 Title: Ubuntu login screen never appears when using the Nvidia driver (and setting WaylandEnable=false fixes it) Status in gdm: New Status in gdm3 package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in gdm3 source package in Eoan: Confirmed Status in mutter source package in Eoan: Confirmed Bug description: https://gitlab.gnome.org/GNOME/gdm/issues/483 formerly https://gitlab.gnome.org/GNOME/gdm/issues/435 --- The boot process hangs with the last message being "started bpfilter". There is unusual Network activity during that time. The light of the WiFi adapter is blinking a lot. I am not sure the problem is with the gdm3 package. As a matter of fact, I would remove it and let someone more experienced to set it. I'm afraid I might break something, though. The specific steps or actions you took that caused you to encounter the problem: 1. Boot Ubuntu 18.10 with the Nvidia proprietary drivers installed. The behavior you expected: I expected Ubuntu 18.10 to boot normally. The behavior you actually encountered: The computer gets stuck in a command-like environment with the last message being "started bpfilter". You can't type any commands. I have found that uninstalling the Nvidia proprietary drivers by going into recovery mode fixes the issue. Booting with the earlier kernel doesn't fix the issue. Installing the earlier v.340 driver also doesn't fix the issue. This (https://askubuntu.com/questions/1032639/ubuntu-18-04-stuck-in- boot-after-starting-gnome-display-manager-on-intel-graphic) seems relevant. This is where I found the "solution". To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1798790/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
