SOLVED (MAYBE)

For me, it's not nVidia, it's not WaylandEnable. It may be the "Started
bpfilter" message, which I earlier thought was nothing. I don't know
beans about this, but I checked, and bpfilter is a recent replacement
for iptables in many Linux distros, and it's handled in the linux
kernel. Casting about for perhaps an alternate to gnome display manager
3, I found that SLiM had high user ratings, and one of the suggested
advantages was it didn't require systemd (the system startup daemon,
which historically has had a running conflict with kernel developers,
maybe bpfilter.) On the gamble that this bootup hang might be caused by
a kernel-systemd conflict, I enabled networking in recovery mode and ran
'apt install slim' to install alternate display manager SLiM. the
installation prompted me to choose SLiM or GDM as the default, I chose
SLiM, and was able to boot Cosmic finally. If I run into any issues
further on, I'll post here.

If you already have an alternate display manager installed, you can
switch with "sudo dpkg-reconfigure gdm" and select the alt dm.

Anyway, this might be a last, desperate workaround for the "bpfilter
hang," if all the other solutions didn't work for you.

-- 
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 18.10 login screen never appears when using the Nvidia driver

Status in gdm3 package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  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/ubuntu/+source/gdm3/+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

Reply via email to