Thanks. I think I can see the problem now.

The first thing that happens is that gdm3 tries to start a Wayland login
screen ('gnome-shell' process) and fails because the Nvidia driver
doesn't support KMS:

Oct 23 11:59:14 efthimios-GA-78LMT-USB3 gnome-shell[1688]: 
meta_kms_resources_init failed: Calling drmModeGetResources() failed, assuming 
we have no outputs
Oct 23 11:59:14 efthimios-GA-78LMT-USB3 gnome-shell[1688]: Failed to create 
backend: No GPUs with outputs found

That is not a bug. What it should do next (and does on my machine) is
then try again to start the login screen using X instead. However I
can't see that in your log. You might have something odd installed or
preventing the fallback from working.

Please:

1. Report the bug to the gdm developers here:

   https://gitlab.gnome.org/GNOME/gdm/issues

   and then tell us the new bug ID.

2. Try this as a workaround: edit /etc/gdm3/custom.conf and uncomment
the line:

   #WaylandEnable=false

-- 
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:
  Incomplete
Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  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     : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to