I will try the Wayland parameter option, but for what it's worth, the only way I've been able to recover so far is to boot off a USB thumb drive, mount my actual boot drive, download and run boot-repair. When I reboot, I finally get a grub menu and can institute the usual menu- driven repairs from there. The full boot-repair report can be found at https://paste.ubuntu.com/p/34RRkD365G/.
-- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1798790 Title: Ubuntu login screen sometimes doesn't appear on a single GPU Nvidia system (and setting WaylandEnable=false fixes it) Status in gdm: Fix Released Status in gdm3 package in Ubuntu: Fix Released Status in gnome-session package in Ubuntu: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Status in mutter package in Ubuntu: Invalid Status in gdm3 source package in Eoan: Fix Released Status in gnome-session source package in Eoan: Fix Released Status in gnome-shell source package in Eoan: Fix Released Status in mutter source package in Eoan: Invalid 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
