nvidia-390 fails to boot graphical display

Bug #1752053 reported by walkerstreet on 2018-02-27
This bug affects 142 people
Affects Status Importance Assigned to Milestone
mesa (Ubuntu)
nvidia-graphics-drivers-390 (Ubuntu)
xserver-xorg-video-nouveau (Ubuntu)

Bug Description

I'm using Bionic with the new 4.15 kernel. I've been using the nvidia-384 driver with no problem for a while. Today I issued "sudo apt-get upgrade" and I was prompted to upgrade the nvidia driver to the nvidia-390. After installing the driver and rebooting, I was only able to boot in to the tty terminal. The graphical display failed to boot. I have had similar problems with nvidia driver version 390 with Arch Linux and with Open Suse Tumbleweed.

Igor Mokrushin (mcmcc) wrote :

Same thing, after update and reboot I get only to console...

My notebook Asus ROG GL553VE with installed Kubuntu 18.04.

x15 (x15) wrote :

Same thing too. 18.04 Kubuntu with GTX 560, ASUS P6T Deluxe V2

Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in nvidia-graphics-drivers-390 (Ubuntu):
status: New → Confirmed
x15 (x15) wrote :

Before reboot there was no libGl....
After reboot the log says:

Parse error on line 5 of section OutputClass in file /usr/share/X11/xorg.conf.d/nvidia-drm-outputclass-ubuntu.conf "Option" is not a valid keyword in same section.
Problem parsing the config file
Error parsing the config file
Fatal server error:
no screens found(EE)

Igor Mokrushin (mcmcc) wrote :

This packages are broken, library files install in root directory /#...
Also, there is no replace of alternative symbolic links ones in /etc/alternatives, they remain from previous versions to non-existent files...

Alberto Milone (albertomilone) wrote :

The new driver is not going to work without libglvnd and xorg-server from bionic-proposed. Sorry for the inconvenience.

Changed in nvidia-graphics-drivers-390 (Ubuntu):
importance: Undecided → Critical
tags: added: regression-release
Steve Langasek (vorlon) wrote :

If it doesn't work without the libglvnd and xorg-server from bionic-proposed, then there should be versioned Depends: or versioned Breaks: expressing this. Alberto, can you make sure this is added in the next upload?

Brian Murray (brian-murray) wrote :

I had to install the following packages from bionic-proposed to get a working X session again.

libglvnd0, xserver-xorg-core, and libgl1-mesa-glx.

tags: added: rls-bb-incoming
Dejan V. (lnxsurf) wrote :

I have the same problem...

I tried to install
libglvnd0, xserver-xorg-core, and libgl1-mesa-glx

but it doesn't work for me...

walkerstreet (dbonner) wrote :

I added bionic-proposed and upgraded to the latest: libglvnd0, xserver-xorg-core, and libgl1-mesa-glx
After doing that, I get a blank screen. I have to Ctrl-Alt-F1 to go to tty console mode.
So the suggested fix did not work for me either.

I encountered a dead symbolic link for libvdpau.so:

$ ls -l /usr/lib/x86_64-linux-gnu/libvdpau_nvidia.so
lrwxrwxrwx 1 root root 31 Feb 22 18:50 /usr/lib/x86_64-linux-gnu/libvdpau_nvidia.so -> vdpau/libvdpau_nvidia.so.390.25

libvdpau_nvidia.so.390.25 is located in the same directory, not in the subdirectory vdpau: https://packages.ubuntu.com/bionic/amd64/libnvidia-decode-390/filelist

Which can be fixed using the following commands:
cd /usr/lib/x86_64-linux-gnu/
sudo ln -sf libvdpau_nvidia.so.390.25 libvdpau_nvidia.so

Chris (cmseuk) wrote :

I already have libglvnd0, xserver-xorg-core, and libgl1-mesa-glx installed. I am not using an nvidia driver or hardware and I have the same problem. Unable to boot into system.

Chris (cmseuk) wrote :

 "Started gnome display manager.....service link was shutdown. Tried to start xserver and got libGl.so not found error.

Chris (cmseuk) wrote :

I upgraded to proposed and the issue is fixed.

x15 (x15) wrote :

I've able to run jwm (startx jwm) and rxvt. Firefox and konsole need libGl but Vialdi, OneTeam and Thunderbird work fine somehow....

Ive had this same problem. I have an nvidia 960m in my laptop using nvidia-390. After I upgraded, I got the “Option is not a valid keyword...” as well. For future refernce, you can get a rudamentary GUI
1. apt removing and apt purging all things nvidia then rebooting
2. At the GRUB screen, add “nomodeset” to the kernel parameters
3. Upon arriving at the lightdm login screen, switch to TTY 1 with ctrl + alt + F1 and chown the .Xauthority file to your_user:your_user
4. Switch back to the login with ctrl + alt + F7 and login like usual.

It’ll look ugly but it works. Tested on Unity.

Changed in nvidia-graphics-drivers-390 (Ubuntu):
assignee: nobody → Alberto Milone (albertomilone)

I haven’t fully upgraded to proposed yet but adding the symlink and the packages Alberto specified did not solve my problem.

Dejan V. (lnxsurf) wrote :

How did you install the proposed packages? I think I did but no change appeared.

Uncomment proposed repo in `/etc/apt/sources.list` then run `sudo apt update` then you can either install the packages you want specifically or you can `sudo apt upgrade` to update all of them at once.

Dejan V. (lnxsurf) wrote :

Hmm... I don't have any line commented. So would you print me the lines which I have to uncomment, please?

Sergei Beilin (saabeilin) wrote :

Updating to `proposed` did not help me. I've tried uninstalling/purging `nvidia-*` and installing it back, still having the black screen.

Tried to switch to Intel adapter using prime-select, it complains that it's not supported.

Purging nvidia-390 and installing nvidia-340 works (though Nvidia always runs on top clock, even on battery, overheating my knees, and always on 100% brightness)

Dell Latitude 6430, NV520.

@lnxsurf, “deb http://us.archive.ubuntu.com/ubuntu/ bionic-proposed multiverse main universe restricted” that line gets added to your sources file.

Dejan V. (lnxsurf) wrote :

Great! Thanks alot for your help.
I used “deb http://de.archive.ubuntu.com/ubuntu/ bionic-proposed multiverse main universe restricted"
Then I installed the mentioned packages but still it did not work.
After I executed "sudo apt dist-upgrade" everything got better. I could start my desktop again.

Confirmed on Unity for me, adding proposed and running sudo apt update && sudo apt upgrade works. I can boot fully with no problems into lightdm and unity runs fine after logon.

Chris McDonough (chrism-plope) wrote :

After having the same problem, I dist-upgraded to proposed and can confirm that it fixed it (I did an apt-get purge nividia* before the dist-upgrade then a apt-get install nvidia-384 after the dist-upgrade)/

One thing that this minor bug pointed out to me is that it has become inconvenient in the current strategy to revert to an older Nvidia driver version, as nvidia-384 is now a transitional package that depends on nvidia-390. Even after adding the graphics-driver ppa, it was not trivially possible to downgrade from 390. I understand the intent (upgrade folks to the latest proprietary thing without them needing to take extra action), but I sort of wonder whether the packages should be renamed so they don't match the graphics-driver ppa names, such that we could purge nvidia, then add the ppa, then do e.g. apt-get install nvidia-387 and actually get 387 instead of 390.

Nate Swanson (nswanson08) wrote :

The proposed repo with dist-uprade worked for me

walkerstreet (dbonner) wrote :

I have successfully installed the driver using the proposed repo packages on my laptop. I need to try my desktop again.
Does anyone know how to use nvidia prime-select and bumblebee/optirun with this driver. My laptop battery might drain fast using this mode.

Peter Silva (peter-bsqt) wrote :

tried the *proposed* recipe above. no luck for me:
as it is installing, it errors:

npacking nvidia-dkms-390 (390.25-0ubuntu1) over (390.25-0ubuntu1) ...
Setting up nvidia-dkms-390 (390.25-0ubuntu1) ...
dpkg: error: version '-' has bad syntax: revision number is empty
dpkg: error: version '-' has bad syntax: revision number is empty
update-initramfs: deferring update (trigger activated)
INFO:Enable nvidia

and the xorg doesn't find the nvidia driver on startup.

Renaud Lepage (cybik) wrote :

I managed to fix my setup by using the Graphics Drivers PPA (https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa) and forcing the install of version 390.25-0ubuntu0~gpu18.04.1 (apt-get install nvidia-390=390.25-0ubuntu0~gpu18.04.1 or something). I suspect version 390.25-0ubuntu1 is broken.

Brian Murray (brian-murray) wrote :

For the development release of Ubuntu it is not recommended to install the packages from -proposed because they have not passed automated testing yet. I only installed the exact packages I needed and then disabled -proposed. Here's the full set of packages I installed incase I missed one.

Start-Date: 2018-02-27 10:58:32
Commandline: apt-get install nvidia-driver-390
Requested-By: bdmurray (1000)
Install: nvidia-compute-390:amd64 (390.25-0ubuntu1, automatic), libnvidia-encode-390:amd64 (390.25-0ubuntu1, automatic), xserver-xorg-video-nvidia-390:amd64 (390.25-0ubuntu1, automatic), libnvidia-fbc1-390:amd64 (390.25-0ubuntu1, automatic), libnvidia-decode-390:amd64 (390.25-0ubuntu1, automatic), nvidia-compute-no-dkms-390:amd64 (390.25-0ubuntu1, automatic), libnvidia-cfg1-390:amd64 (390.25-0ubuntu1, automatic), nvidia-utils-390:amd64 (390.25-0ubuntu1, automatic), libnvidia-fbc1-390-i386:i386 (390.25-0ubuntu1, automatic), libnvidia-ifr1-390-i386:i386 (390.25-0ubuntu1, automatic), nvidia-compute-utils-390:amd64 (390.25-0ubuntu1, automatic), libnvidia-ifr1-390:amd64 (390.25-0ubuntu1, automatic), nvidia-driver-390:amd64 (390.25-0ubuntu1), libnvidia-encode-390-i386:i386 (390.25-0ubuntu1, automatic), screen-resolution-extra:amd64 (0.17.2, automatic), libnvidia-decode-390-i386:i386 (390.25-0ubuntu1, automatic), nvidia-settings:amd64 (384.69-0ubuntu1, automatic)
End-Date: 2018-02-27 10:58:38

Start-Date: 2018-02-27 11:12:22
Commandline: apt-get install libgl1-mesa-glx
Requested-By: bdmurray (1000)
Install: libegl1:amd64 (1.0.0-2ubuntu1, automatic), libgl1:amd64 (1.0.0-2ubuntu1, automatic), libopengl0:amd64 (1.0.0-2ubuntu1, automatic), libgles2:amd64 (1.0.0-2ubuntu1, automatic), libglvnd-dev:amd64 (1.0.0-2ubuntu1, automatic), libglx0:amd64 (1.0.0-2ubuntu1, automatic), libglvnd-core-dev:amd64 (1.0.0-2ubuntu1, automatic), libglx-mesa0:amd64 (18.0.0~rc4-1ubuntu1, automatic)
Upgrade: libgles2-mesa:amd64 (17.3.3-0ubuntu1, 18.0.0~rc4-1ubuntu1), libegl1-mesa-dev:amd64 (17.3.3-0ubuntu1, 18.0.0~rc4-1ubuntu1), libglapi-mesa:amd64 (17.3.3-0ubuntu1, 18.0.0~rc4-1ubuntu1), mesa-common-dev:amd64 (17.3.3-0ubuntu1, 18.0.0~rc4-1ubuntu1), libegl1-mesa:amd64 (17.3.3-0ubuntu1, 18.0.0~rc4-1ubuntu1), libwayland-egl1-mesa:amd64 (17.3.3-0ubuntu1, 18.0.0~rc4-1ubuntu1), libgles2-mesa-dev:amd64 (17.3.3-0ubuntu1, 18.0.0~rc4-1ubuntu1), libgl1-mesa-dev:amd64 (17.3.3-0ubuntu1, 18.0.0~rc4-1ubuntu1), libgl1-mesa-glx:amd64 (17.3.3-0ubuntu1, 18.0.0~rc4-1ubuntu1)
End-Date: 2018-02-27 11:12:26

Bruce Pieterse (octoquad) wrote :

I've installed the packages from proposed and I can see that X can now load the nvidia module, but out of curiosity, would it cause:

org.gnome.Shell.desktop[4934]: /usr/bin/gnome-shell: error while loading shared libraries: libEGL.so.1: cannot open shared object file: No such file or directory

Due to that the following occurs:

gnome-session-binary[4911]: Unrecoverable failure in required component org.gnome.Shell.desktop
gnome-session[4911]: gnome-session-binary[4911]: CRITICAL: We failed, but the fail whale is dead. Sorry....
gnome-session-binary[4911]: WARNING: App 'org.gnome.Shell.desktop' respawning too quickly
gnome-session-binary[4911]: CRITICAL: We failed, but the fail whale is dead. Sorry....

$ locate -e libEGL.so.1

Any ideas, or should this specific library problem be reported against gnome-shell?

Brian Murray (brian-murray) wrote :

 $ dpkg -S /usr/lib/x86_64-linux-gnu/libEGL.so.1
libegl1:amd64: /usr/lib/x86_64-linux-gnu/libEGL.so.1

So install libegl1.

Francois Thirioux (fthx) wrote :

Maybe it's not the place to do that but could it be possible that an Ubuntu developer tell us what are the changes in this new driver & packaging ?
Questions :
- will it be possible to use Wayland running Nvidia ?
- will it be possible to change GPU without rebooting ?
- will it be possible to do like Nouveau, I mean launch an app using the discrete GPU (right click menu) ?
- how can we now switch GPU on an Optimus configuration ?
Ubuntuforums dev section :

Alberto Milone (albertomilone) wrote :

@walkerstreet: disabling the dGPU won't work, because of logind:

@Peter Silva: that is not an actual error. You are going to need the new xserver and the new libglvnd from bionic-proposed.

walkerstreet (dbonner) wrote :

My desktop computer won't display the X desktop on my monitor after installing the new driver with the Bionic-proposed packages. I get a blank screen except for a tty cursor in the top left corner of the screen. I can view the X desktop remotely using Teamviewer though, which is really wierd. Typing nvidia-smi verifies that driver 390.25 is installed and running. I have 2 nvidia 1080Ti cards. Since the new driver is unusable on my desktop, I have reverted back to nvidia-384. Does anyone have any suggestions as to how I can get the new driver to display the X desktop on my monitor?

Peter Silva (peter-bsqt) wrote :

I now have drivers from bionic proposed, the problem I had before
was that I had attempted to manually correc nvidia-drm-outputclass-ubuntu.conf by commenting out the lines which had caused errors before,
and re-installing wasn't overwriting it.
I returned it to default state. I can now get the lightdm up.

on xorg.0.log it seems to load now, I get to the login dialog,
but none of my sessions will load ( I just go back to the lightdm dialog.) there are no errors, it just dumps me back at the lightdm
screen. I added a bunch of -desktop packages to see if it was an
environment thing. The failure to login happens with *ubuntu*, *unity (default)*, *Ubuntu on Wayland*. With *mate* it doesn't exist, but I get a screen with a single icon, and no other elements of a desktop, so I can only open

Try switching to a TTY when the lightdm screen comes up and running “chown your_user:your_user .Xauthority” then try to login with lightdm.

Peter Silva (peter-bsqt) wrote :

OK, video is back now: apt-install ubuntu-mate-desktop fixed something.
It was already installed, but doing it again tickled something. I logged into
mater, and there was half a dozen core dumps of various components, and then
everything started working. (I don´t actually use mate, it was just trying
to see if issue was related to desktop environment in use.) I logged out, and now everything is now normal again.

now I can log in again, with the same environment I had before the problem.
I´ve now commented out bionic proposed from /etc/apt/sources.list
stuff looks ok.

Bruce Pieterse (octoquad) wrote :

Thanks Brian,

Looks like libegl1 landed today. Picked it up with a normal apt update and everything is good again.

Chris McDonough (chrism-plope) wrote :

Downgraded from proposed using pins and after a dist-upgrade it works, thanks!

Changed in nvidia-graphics-drivers-390 (Ubuntu):
status: Confirmed → Incomplete
assignee: Alberto Milone (albertomilone) → nobody
Changed in mesa (Ubuntu):
status: New → Incomplete
Changed in nvidia-graphics-drivers-390 (Ubuntu):
status: Incomplete → Fix Released
Changed in mesa (Ubuntu):
status: Incomplete → Fix Released
Changed in xserver-xorg-video-nouveau (Ubuntu):
status: New → Invalid
127 comments hidden view all 207 comments
Mathew Garland (kromosome) wrote :

Ubuntu 18.04
Mate & XFCE
Running Nvidia 390 - NVIDIA Corporation GM107M [GeForce GTX 850M] (rev a2)

Same issue faced here. Initially everything was running well until I tried installing the CUDA libraries for Machine Learning purposes. This was the start of this disaster.

This Issue should be considered a show stopper!

masato-hi (masato-hi) wrote :
Download full text (5.4 KiB)

I am using Google Translate because English is not very good.
I am sorry if there is content difficult to understand.

$ uname -srvpio
Linux 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 18:02:16 UTC 2018 x86_64 x86_64 GNU/Linux

$ nvidia-smi
Fri Jul 13 14:12:01 2018
| NVIDIA-SMI 390.67 Driver Version: 390.67 |
| GPU Name Persistence-M| Bus-Id Disp.A | Volatile Uncorr. ECC |
| Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. |
| 0 GeForce 940MX Off | 00000000:01:00.0 Off | N/A |
| N/A 47C P0 N/A / N/A | 726MiB / 2004MiB | 4% Default |


If you are using a NVIDIA GPU built-in laptop please try the following method.

Execute `prime-select query`.
If the output is not `nvidia`, execute `prime-select nvidia` and restart it.

Please execute `lshw -C display`.

■ *-display UNCLAIMED If is a device of `vendor: Intel Corporation`
If `nomodeset` or `i915.modeset=0` is included in GRUB_CMDLINE_LINUX_DEFAULT or GRUB_CMDLINE_LINUX in `/etc/default/grub`, delete it, run update-grub and restart it.

■ *-display UNCLAIMED If is a device of `vendor: NVIDIA Corporation`
If `nomodeset` or `nvidia-drm.modeset=0` is included in GRUB_CMDLINE_LINUX_DEFAULT or GRUB_CMDLINE_LINUX in `/etc/default/grub`, delete it, run update-grub and restart it.

If `inxi` is not installed, please run `apt-get install -y inxi`.

Please execute `inxi -G`.

If `drivers: nvidia` is displayed, you need to add the following to `/etc/X11/xorg.conf`.
Section "Device"
    Identifier "intel"
    Driver "modesetting"
    Option "AccelMethod" "None"

If `drivers: modesetting,nvidia` is displayed, please delete or comment out `Monitor "Monitor 0"` from `Section "Screen"` including `Device "nvidia"`.
Section "Screen"
    Identifier "intel"
    Device "intel"
    Monitor "Monitor 0"

Section "Screen"
    Identifier "nvidia"
    Device "nvidia"
# Monitor "Monitor 0"
    DefaultDepth 24
    Option "AllowEmptyInitialConfiguration" "on"
    Option "IgnoreDisplayDevices" "CRT"
    Option "ConstrainCursor" "off"
    SubSection "Display"
        Depth 24
        Modes "nvidia-auto-select"
Then restart it or execute `service gdm3 restart`.
that's all.

This problem is caused by the fact that nvidia-xconfig generated /etc/X11/xorg.conf does not include the loading of the modesetting driver, and the monitor output is connected to the nvidia device.
(I am not familiar with X11 so I do not know if that is correct)

Perhaps the smallest /etc/X11/xorg.conf that solves this problem is:
(BusID varies depending on the environment)
Section "ServerLayout"
    Identifier "layout"
    Screen 0 "nvidia"
    Inactive "intel"

Section "Device"
    Identifier "intel"
    Driver "m...


Nguyen Xuan Viet (vietnx) wrote :

Solution in #123 did not work for me, even with higher sleep time.
So I have to switch back to lightdm.

Artyom (artyom-szasa) wrote :

I think I have the same issue.
Difference is that everything worked as charm until I've updated some non-nvidia packages. Since then I'm stuck to uning nouveau as none of the workarounds worked.

nVIDIA GeForce GTX 1060 6GB

What worked fine before update:
kernel 4.15.x-x with nvidia 390 (ubuntu repository)
kernel 4.17.x with nvidia 396 (ppa)

After the update it worked one more time with 4.15.x with
options nvidia_390_drm modeset=1
in /etc/modprobe.d/xxxx.conf

Since after next reboot nothing has worked except purge-ing nvidia and switching to nouveau...

Attaching apt log for that update. mono was updated as well adding a lot of noise, but the relevant part seems to be grub:

Kibontás előkészítése: .../14-grub-efi-amd64_2.02-2ubuntu8.2_amd64.deb ...
Kibontás: grub-efi-amd64 (2.02-2ubuntu8.2) e helyett: 2.02-2ubuntu8.1 ...
Kibontás előkészítése: .../15-grub2-common_2.02-2ubuntu8.2_amd64.deb ...
Kibontás: grub2-common (2.02-2ubuntu8.2) e helyett: 2.02-2ubuntu8.1 ...
Kibontás előkészítése: .../16-grub-efi-amd64-signed_1.93.3+2.02-2ubuntu8.2_amd64.deb ...
Kibontás: grub-efi-amd64-signed (1.93.3+2.02-2ubuntu8.2) e helyett: 1.93.2+2.02-2ubuntu8.1 ...
Kibontás előkészítése: .../17-grub-efi-amd64-bin_2.02-2ubuntu8.2_amd64.deb ...
Kibontás: grub-efi-amd64-bin (2.02-2ubuntu8.2) e helyett: 2.02-2ubuntu8.1 ...
Kibontás előkészítése: .../18-grub-common_2.02-2ubuntu8.2_amd64.deb ...
Kibontás: grub-common (2.02-2ubuntu8.2) e helyett: 2.02-2ubuntu8.1 ...

i.e. grub was updated from 2.02-2ubuntu8.1 to 2.02-2ubuntu8.2.

Not sure if any of these can help, but for me nvidia has been completely broken since this update. Since then I'm constantly getting the following lines in kern.log (egrep -i '(nvidia|nvrm)'):

kernel: [ 1.675561] NVRM: loading NVIDIA UNIX x86_64 Kernel Module 396.24.10 Tue Jul 10 10:00:18 PDT 2018 (using threaded interrupts)
kernel: [ 1.682807] nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for UNIX platforms 396.24.10 Tue Jul 10 08:53:56 PDT 2018
kernel: [ 1.685191] [drm] [nvidia-drm] [GPU ID 0x00000100] Loading driver
kernel: [ 2.543799] nvidia-modeset: Allocated GPU:0 (GPU-ca4d2121-189c-752b-9cba-302ed81038d4) @ PCI:0000:01:00.0
kernel: [ 2.595623] [drm] Initialized nvidia-drm 0.0.0 20160202 for 0000:01:00.0 on minor 0
kernel: [ 3.244611] nvidia-uvm: Loaded the UVM driver in 8 mode, major device number 236
kernel: [ 5.310256] NVRM: GPU at PCI:0000:01:00: GPU-ca4d2121-189c-752b-9cba-302ed81038d4
kernel: [ 5.310259] NVRM: Xid (PCI:0000:01:00): 61, 0ac0(2f10) 00000000 00000000
kernel: [ 12.366052] nvidia-modeset: WARNING: GPU:0: Lost display notification (0:0x00000000); continuing.
kernel: [ 15.124364] nvidia-modeset: ERROR: GPU:0: Idling display engine timed out: 0x0000987d:0:0

Layke (layke1123) wrote :

So I was able to get everything working on 16.04 with nvidia-384. I tried many a different things on 18.04 with nvidia-390 and nvidia-396 but no luck including using proposed Bionic Beaver but no luck. If I can help report anything though I'd be glad to post it if you tell me what you need from my system. I hope this bug is fixed soon. 18.04 LTS is an improvement on 16.04 LTS I thought from my brief exposure to the system. This setup seems to run slower compared to Bionic Beaver.

siyman (siyman) wrote :

I am affected by this bug, too. Using an nVidia GTX 660 with legacy nvidia-340 (both mainline as well as graphics-driver ppa) my system is working as before. Switching to 390 or even 396 leaves me at a blinking cursor DM both on sddm and gdm3. The only DM I could use has been lightdm but only after I chowned the .Xauthority file of my user home dir whilst it was running (sadly this is a no go for me as I rely on multi user sessions which do not work anymore since the upgrade to bionic).

1 comments hidden view all 207 comments
Omar Alvarez (osurfer3) wrote :

I am also having this issue, system fully updated, nvidia-driver-396, GTX 1050Ti, kernel 4.15.0-33-generic. Also happens with nvidia-driver-390. The fix for me was #123:

sudo service gdm stop ; sleep 5 ; sudo service gdm start

This is definitely not fixed.

Tom (tom-lorinthe) wrote :

It remains weird that a complete ciritical-show-stopping bug receives no attention from the true experts... What are we doing wrong to report it here?

NiBu (niko-buzki) wrote :

After upgrading from 18.04 to 18.10 the gnome freezes after GDM login.

Saeed Tabrizi (saeed.tabrizi) wrote :

After upgrading from 18.04 to 18.10 the freezes before login. (nvidia-driver-390)

After upgrading from 18.04 to 18.10 the freezes before login. (nvidia-driver-390)

ccdisle (sim-blk) wrote :

After upgrading from 18.04 to 18.10 the freezes before login. (nvidia-driver-390)

Melvin1981 (melvis) wrote :

New install ubuntu 18.10. Nvidia-390, nvidia-410 freezes before login.
Only purge drivers makes system back to boot

Saeed Tabrizi (saeed.tabrizi) wrote :

After upgrading from 18.04 to 18.10 the freezes before login. (nvidia-driver-390)

ccdisle (sim-blk) wrote :

Yes this is exactly the problem I have. Every-time I install the Nvidia-drivers the machine won't boot up it hangs and displays

 "Failed to connect to lvmetad. Falling back to device scanning. /dev/mapper/ubuntu--vg--root"

I even tried installing earlier drivers -340 or 361 . The problem persists.

The only time it boots up is when I purge the Nvidia drivers.

This started soon after I upgraded to 18.10.

Pinni (t-pinhammer) wrote :

Same problem here.

Melvin1981 (melvis) wrote :

Texted to NVidia support about the issue. Got reply

Your case is being escalated to our Level 2 Tech Support group. The Level 2 agents will review the case notes and may attempt to recreate your issue or find a workaround solution if possible. As this process may take some time we ask that you be patient and a Level 2 tech will contact you as soon they can to help resolve your issue.

Timo Aaltonen (tjaalton) wrote :

this bug is closed, if you are seeing issues with current versions please file a new bug instead of posting here

Tom (tom-lorinthe) wrote :

@tjaalton ... funny, >185 persons report they have same issue here without any solution.. and then bug reports get closed without reference to where to duplicate all reports ? ))

Do you have bug number where we can copy and paste this to ?

Solution found with NVidia support.
GDM3 causing Ubuntu 18.10 to "freeze" before login screen
After remove GDM3 and LightDM installation Ununtu booted as usually

I would say workaround not solution

Please try, in the /etc/gdm3/custom.conf, uncomment WaylandEnable=false and Nvidia driver will work with gdm3.

OMG! Where u were all this time?! Thank you very much!

:) You're welcome.

ccdisle (sim-blk) wrote :

I just tested this. It worked for me as well. Thanks, Nebojša.

ccdisle (sim-blk) wrote :

Uncommenting "WaylandEnable=false " worked.

Removing gdm3 did not work, I just got redirected to a tty3 login shell.

Thanks again

You're welcome, Ccdisle.

I didn’t need to remove GDM3, but installing LightDM (and switching to it) fixed it for me. Well, I should say it was a workaround, anyway...

> On Oct 24, 2018, at 11:56 PM, ccdisle <email address hidden> wrote:
> Uncommenting "WaylandEnable=false " worked.
> Removing gdm3 did not work, I just got redirected to a tty3 login shell.
> Thanks again
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1752053
> Title:
> nvidia-390 fails to boot graphical display
> Status in mesa package in Ubuntu:
> Fix Released
> Status in nvidia-graphics-drivers-390 package in Ubuntu:
> Fix Released
> Status in xserver-xorg-video-nouveau package in Ubuntu:
> Invalid
> Bug description:
> I'm using Bionic with the new 4.15 kernel. I've been using the
> nvidia-384 driver with no problem for a while. Today I issued "sudo
> apt-get upgrade" and I was prompted to upgrade the nvidia driver to
> the nvidia-390. After installing the driver and rebooting, I was only
> able to boot in to the tty terminal. The graphical display failed to
> boot. I have had similar problems with nvidia driver version 390 with
> Arch Linux and with Open Suse Tumbleweed.
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+subscriptions

Wei (weiwanse) wrote :

I had the same problem after upgrading to 18.10. Uncommenting "WaylandEnable=false" worked.

Simon Brereton (sbrereton63) wrote :

The uncommenting #WaylandEnable=false worked a treat for me as with the previous posters. This is the answer to this problem and needs pinning to the thread!

bblrlo (bblrlo-gmail) wrote :

On KUbuntu 18.04 same problem with card GT630M and 390,396 nvidia drivers
#lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.1 LTS
Release: 18.04
Codename: bionic
# cat /etc/X11/default-display-manager

Skander Guarbàa (skope) wrote :

Guys ..
I have Nvidia 1050ti with nvidia-390 driver installed.

When i boot am on 900 resolution instead of a 1920x1080 normal resolution.

Anyone got a solution for that ??

Thanks in advance.

Alexey Sys (alexey107) wrote :

Uncommenting "WaylandEnable=false" worked for me in 18.10 fresh install and applying nvidia-390

Wayne Bell (kingramze) wrote :

Same issue with Nvidia Geforce GTX 1060 6 GB - wouldn't work with 390, 396, 410, or 415 drivers. Only Nouveau under Ubuntu 18.10 (upgraded from beta and previously 18.04 as original install)

Resolved by switching to lightdm and booting into Cinnamon Desktop instead of Gnome. Mate works as well.
Also uncommented "WaylandEnable=false" for future possible use of gdm3 and gnome desktop.

Can someone either mark this as "not fixed" or "won't fix" since it's clearly not resolved.

Daniel van Vugt (vanvugt) wrote :

Please note this bug is closed, so generally will be ignored by developers.

If you have any ongoing problems please consider joining one of these open bugs instead:


or log a new bug by running the command:

  ubuntu-bug gdm3

Only if the original reporter would like this bug reopened should it be reopened.

Michael Lazin (microlaser) wrote :

I am running ubuntu 18.04 and using the low latency kernel rather than the default kernel. Since the "upgrade" to nvidia 390 it looks like the kernel module is actually missing from my filesystem. Running dmesg | grep nvidia and modprobe | grep nvidia tells me the nvidia driver is not loaded. When I try to load it with modprobe it's not in the proper path so it can't load. I tried reverting the nvidia driver and the kernel but the kernel module is still mysteriously missing. I'm going to reinstall with ubuntu studio 18.10 because this update has basically destroyed the functionality of my desktop. I need 1920x1068 resolution and that's not an option with the xrandr command without the nvidia driver. I did not check to see of nouveau was loaded as a kernel module, I just gotta reinstall. I hope this helps someone.

Gert Kruger (hgkrug1) wrote :

I have a NVIDIA Corporation GP107 [GeForce GTX 1050] card and ubuntu 19.04 installed. After installing the lastest Nvidia driver-430, the dektop GUI is lost when you reboot (18.10 gave the same issue). I tried many proposed solutions, including the one above. Nothing worked.
I finally found a solution for this Nvidia driver issue (on ubuntu 18 and 19). See instructions at the top at https://ubuntuforums.org/showthread.php?t=2419319&highlight=nvidia+drivers, it worked for me!

Alexander Trufanov (truf) wrote :

Faced with this problem in Lenovo G780, NVIDIA 635M and nvidia-driver-390 package

Operating System: Kubuntu 19.04
KDE Plasma Version: 5.15.4
Kernel Version: 5.0.0-29-generic

Addition of "WaylandEnable=false" to /usr/share/lightdm/lightdm.conf.d/90-nvidia.conf resolved the problem.

Displaying first 40 and last 40 comments. View all 207 comments or add a comment.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.