[Bug 1752053] [NEW] nvidia-390 fails to boot graphical display

[walkerstreet]

Public bug reported:

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.

** Affects: nvidia-graphics-drivers-390 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752053

Title:
nvidia-390 fails to boot graphical display

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1752053/+subscriptions

[Igor Mokrushin]

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

My notebook Asus ROG GL553VE with installed Kubuntu 18.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752053

Title:
nvidia-390 fails to boot graphical display

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1752053/+subscriptions

[x15]

Same thing too. 18.04 Kubuntu with GTX 560, ASUS P6T Deluxe V2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752053

Title:
nvidia-390 fails to boot graphical display

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1752053/+subscriptions

[Launchpad Bug Tracker]

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

** Changed in: nvidia-graphics-drivers-390 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752053

Title:
nvidia-390 fails to boot graphical display

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1752053/+subscriptions

[x15]

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)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752053

Title:
nvidia-390 fails to boot graphical display

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1752053/+subscriptions

[Igor Mokrushin]

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...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752053

Title:
nvidia-390 fails to boot graphical display

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1752053/+subscriptions

[Alberto Milone]

The new driver is not going to work without libglvnd and xorg-server
from bionic-proposed. Sorry for the inconvenience.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752053

Title:
nvidia-390 fails to boot graphical display

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1752053/+subscriptions

[Brian Murray]

** Changed in: nvidia-graphics-drivers-390 (Ubuntu)
Importance: Undecided => Critical

** Tags added: regression-release
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752053

Title:
nvidia-390 fails to boot graphical display

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1752053/+subscriptions

[Steve Langasek]

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?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752053

Title:
nvidia-390 fails to boot graphical display

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1752053/+subscriptions

[Brian Murray]

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
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752053

Title:
nvidia-390 fails to boot graphical display

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1752053/+subscriptions

[Dejan V.]

Hi,
I have the same problem...

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

but it doesn't work for me...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752053

Title:
nvidia-390 fails to boot graphical display

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1752053/+subscriptions

[walkerstreet]

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.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752053

Title:
nvidia-390 fails to boot graphical display

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1752053/+subscriptions

[seahawk1986]

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
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752053

Title:
nvidia-390 fails to boot graphical display

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1752053/+subscriptions

[Chris]

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.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752053

Title:
nvidia-390 fails to boot graphical display

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1752053/+subscriptions

[Chris]

"Started gnome display manager.....service link was shutdown. Tried to
start xserver and got libGl.so not found error.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752053

Title:
nvidia-390 fails to boot graphical display

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1752053/+subscriptions

[Chris]

I upgraded to proposed and the issue is fixed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752053

Title:
nvidia-390 fails to boot graphical display

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1752053/+subscriptions

[x15]

I've able to run jwm (startx jwm) and rxvt. Firefox and konsole need
libGl but Vialdi, OneTeam and Thunderbird work fine somehow....
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752053

Title:
nvidia-390 fails to boot graphical display

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1752053/+subscriptions

[Thomas O'Keeffe]

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.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752053

Title:
nvidia-390 fails to boot graphical display

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1752053/+subscriptions

[Brian Murray]

** Changed in: nvidia-graphics-drivers-390 (Ubuntu)
Assignee: (unassigned) => Alberto Milone (albertomilone)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752053

Title:
nvidia-390 fails to boot graphical display

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1752053/+subscriptions

[Thomas O'Keeffe]

I haven’t fully upgraded to proposed yet but adding the symlink and the
packages Alberto specified did not solve my problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752053

Title:
nvidia-390 fails to boot graphical display

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1752053/+subscriptions

[Dejan V.]

How did you install the proposed packages? I think I did but no change
appeared.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752053

Title:
nvidia-390 fails to boot graphical display

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1752053/+subscriptions

[Thomas O'Keeffe]

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.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752053

Title:
nvidia-390 fails to boot graphical display

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1752053/+subscriptions

[Dejan V.]

Hmm... I don't have any line commented. So would you print me the lines
which I have to uncomment, please?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752053

Title:
nvidia-390 fails to boot graphical display

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1752053/+subscriptions

[Sergei Beilin]

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.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752053

Title:
nvidia-390 fails to boot graphical display

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1752053/+subscriptions

[Thomas O'Keeffe]

@lnxsurf, “deb http://us.archive.ubuntu.com/ubuntu/ bionic-proposed
multiverse main universe restricted” that line gets added to your
sources file.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752053

Title:
nvidia-390 fails to boot graphical display

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1752053/+subscriptions

[Dejan V.]

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.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752053

Title:
nvidia-390 fails to boot graphical display

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1752053/+subscriptions

[Thomas O'Keeffe]

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.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752053

Title:
nvidia-390 fails to boot graphical display

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1752053/+subscriptions

[Chris McDonough]

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.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752053

Title:
nvidia-390 fails to boot graphical display

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1752053/+subscriptions

[Nate Swanson]

The proposed repo with dist-uprade worked for me
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752053

Title:
nvidia-390 fails to boot graphical display

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1752053/+subscriptions

[walkerstreet]

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.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752053

Title:
nvidia-390 fails to boot graphical display

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1752053/+subscriptions

[Peter Silva]

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.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752053

Title:
nvidia-390 fails to boot graphical display

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1752053/+subscriptions

[Renaud Lepage]

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.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752053

Title:
nvidia-390 fails to boot graphical display

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1752053/+subscriptions

[Brian Murray]

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
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752053

Title:
nvidia-390 fails to boot graphical display

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1752053/+subscriptions

[Bruce Pieterse]

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
/usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1
/usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1.0.0

Any ideas, or should this specific library problem be reported against
gnome-shell?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752053

Title:
nvidia-390 fails to boot graphical display

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1752053/+subscriptions

[Brian Murray]

$ 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.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752053

Title:
nvidia-390 fails to boot graphical display

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1752053/+subscriptions

[Francois Thirioux]

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 :
https://ubuntuforums.org/forumdisplay.php?f=427
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752053

Title:
nvidia-390 fails to boot graphical display

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1752053/+subscriptions

[Alberto Milone]

@walkerstreet: disabling the dGPU won't work, because of logind:
https://github.com/systemd/systemd/issues/6908

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

** Bug watch added: github.com/systemd/systemd/issues #6908
https://github.com/systemd/systemd/issues/6908
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752053

Title:
nvidia-390 fails to boot graphical display

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1752053/+subscriptions

[walkerstreet]

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?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752053

Title:
nvidia-390 fails to boot graphical display

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1752053/+subscriptions

[Peter Silva]

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
shells.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752053

Title:
nvidia-390 fails to boot graphical display

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1752053/+subscriptions

[Thomas O'Keeffe]

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.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752053

Title:
nvidia-390 fails to boot graphical display

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1752053/+subscriptions

[Peter Silva]

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.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752053

Title:
nvidia-390 fails to boot graphical display

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1752053/+subscriptions

[Bruce Pieterse]

Thanks Brian,

Looks like libegl1 landed today. Picked it up with a normal apt update
and everything is good again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752053

Title:
nvidia-390 fails to boot graphical display

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1752053/+subscriptions

[Chris McDonough]

Downgraded from proposed using pins and after a dist-upgrade it works,
thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752053

Title:
nvidia-390 fails to boot graphical display

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1752053/+subscriptions

[tikend]

Purging

apt-get remove --purge nvidia*

and doing number #30 worked for me

apt-get install nvidia-driver-390
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752053

Title:
nvidia-390 fails to boot graphical display

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1752053/+subscriptions

[linuxar]

I am affected by the same bug, on Xubuntu Bionic. I only managed to log
in by

dpkg-reconfigure to gdm3

to obtain a login manager

and then choosing Gnome session.

I only manage to get... 640x480, but at least it is graphical
environment.

When trying anything else (lightdm as login manager or anything else
like Xubuntu, Mate or Ubuntu DEs), only black screen.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752053

Title:
nvidia-390 fails to boot graphical display

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1752053/+subscriptions

[Burt P.]

Using bionic Xubuntu with the updated nvidia driver I can log in and
everything works, but in only 640x480.

dmesg looks like nvidia is loaded, but it ends up using llvmpipe anyway.

~~~
dmesg | grep nvidia:
[ 0.997785] nvidia: loading out-of-tree module taints kernel.
[ 0.997792] nvidia: module license 'NVIDIA' taints kernel.
[ 1.002303] nvidia: module verification failed: signature and/or required key missing - tainting kernel
[ 1.008686] nvidia-nvlink: Nvlink Core is being initialized, major device number 243
[ 1.008940] nvidia 0000:07:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=none:owns=io+mem
[ 1.022995] nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for UNIX platforms 390.25 Wed Jan 24 19:29:37 PST 2018
[ 1.023352] [drm] [nvidia-drm] [GPU ID 0x00000700] Loading driver
[ 1.023353] [drm] Initialized nvidia-drm 0.0.0 20160202 for 0000:07:00.0 on minor 0
[ 3.934224] nvidia-uvm: Loaded the UVM driver in 8 mode, major device number 241
[ 4.114021] caller os_map_kernel_space.part.7+0xda/0x120 [nvidia] mapping multiple BARs
[ 202.094928] caller os_map_kernel_space.part.7+0xda/0x120 [nvidia] mapping multiple BARs
~~~
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752053

Title:
nvidia-390 fails to boot graphical display

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1752053/+subscriptions

[Burt P.]

Forgot to mention in #43 that using bionic proposed didn't help.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752053

Title:
nvidia-390 fails to boot graphical display

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1752053/+subscriptions

[Kyle Weber]

I had to wipe my system from an image I had made last week. I went
through everything mentioned above--I was able to get video back, but as
soon as I'd try logging in my UI would hang. I'd have to reboot from
SSH. Everything is working now--I'm going to hold off running any
upgrades for a few days though in hopes they fix the bug. Running GTX
1060.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752053

Title:
nvidia-390 fails to boot graphical display

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1752053/+subscriptions

[Chris McDonough]

Burt P wrt https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-
drivers-390/+bug/1752053/comments/43, you might try this:

edit /etc/default/grub, editing:

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"

to:

GRUB_CMDLINE_LINUX_DEFAULT=""

And adding:

GRUB_GFXMODE=1920x1080-32,auto
GRUB_GFXPAYLOAD_LINUX=keep

(you will almost certainly need to change the GRUB_GFXMODE value if your
main display is not native 1920x1080)

Then rerun sudo grub-mkconfig -o /boot/grub/grub.cfg.

I had the same symptom you did a while back, because for unknown reasons
the hardware would get into a snit if the grub graphics mode didn't
match the native mode. You may not need to comment out the splash and
quiet, but I needed to in order to be able to successfully enter a
decryption passphrase.

See also
https://www.reddit.com/r/thinkpad/comments/5m9u00/installed_ubuntu_16041_on_thinkpad_p50_some_notes/de79o3n/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752053

Title:
nvidia-390 fails to boot graphical display

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1752053/+subscriptions

[Ron Bentley]

The work-around suggested in #29 worked for me. That's using the
Graphics Drivers PPA (https://launchpad.net/~graphics-
drivers/+archive/ubuntu/ppa).

Just to be clear about the symptoms I was seeing:

- The splash screen DID appear
- LightDM would NOT appear (just a black, blank screen)
- I could go to a virtual terminal and start the desktop with "startx"
- I had no problems with the Nouveau drivers only the proprietary drivers

However, lightdm works fine with the nvidia-390 package from the
Graphics Drivers PPA.

The hardware is an Asus GL-553-VD laptop with NVIDIA GeForce GTX 1050
Mobile.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752053

Title:
nvidia-390 fails to boot graphical display

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1752053/+subscriptions

[Daniel van Vugt]

nvidia-90 support may/should be fixed now that Mesa 18.0 is in bionic.
Please update and retest.

** Changed in: nvidia-graphics-drivers-390 (Ubuntu)
Status: Confirmed => Incomplete

** Changed in: nvidia-graphics-drivers-390 (Ubuntu)
Assignee: Alberto Milone (albertomilone) => (unassigned)

** Also affects: mesa (Ubuntu)
Importance: Undecided
Status: New

** Changed in: mesa (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752053

Title:
nvidia-390 fails to boot graphical display

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+subscriptions

[Francois Thirioux]

Quadro M1000M : works now without any tweak.

Nonetheless, if you mean "*full* support", laptop users like me will
argue the lack of a GPU switching ability and the removing of the
Wayland session.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752053

Title:
nvidia-390 fails to boot graphical display

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+subscriptions

[Chazall1]

All functioning as expected with the nvidia-driver-390.

Thank you
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752053

Title:
nvidia-390 fails to boot graphical display

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+subscriptions

[Burt P.]

Regarding my comment #43:
The solution suggested in #46 doesn't work. While it does force 1920x1080, even after login, the nvidia driver is not working.

lspci -v does show "Kernel driver in use: nvidia" for the card, but
nvidia-settings behaves as if the driver is not loaded and glxinfo shows
llvmpipe as the OpenGL renderer.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752053

Title:
nvidia-390 fails to boot graphical display

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+subscriptions

[Branchus]

I have a different issue.

it happened in Arch linux, Manjaro, Ubuntu 18.04 beta. if I didn't
install the nvidia 390 driver, everything run smooth, after I installed
nvidia 390 driver, I have no problem with GUI, however, the system
doesn't turn off, restart itself properly. my monitor goes into sleep
(power saving mode - no signal) while the fan and all leds are still on.

I initially thought it is a kernel or systemd issue, after asking
questions on different forums and trying different distros, I think now
I confirm it is a display driver issue.

my graphic card is nvidia quodra k2200

anyone got the same issue?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752053

Title:
nvidia-390 fails to boot graphical display

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+subscriptions

[Burt P.]

Regarding #43, #44, #51, here is what I did:
* Reset the grub config file
* Removed all nvidia* packages
* Reverted everything to the standard bionic as described here: https://askubuntu.com/a/229663
* Removed all the old package information using: dpkg --purge `dpkg --get-selections | grep deinstall | cut -f1`
* Installed nvidia-driver-390: apt-get install nvidia-driver-390
* Restarted

Everything seems to work.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752053

Title:
nvidia-390 fails to boot graphical display

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+subscriptions

[Burt P.]

I spoke too soon, the lock screen is still 640x480, but when unlocked it
returns to 1920x1080. I can live with this, but something is still wrong
with the driver.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752053

Title:
nvidia-390 fails to boot graphical display

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+subscriptions

[walkerstreet]

I still get a blank screen with a text cursor in the top left corner on
my desktop computer. There is no login and no GUI after I install the
nvidia-driver-390. It has 2 GTX 1080 Ti cards. My laptop is working
OK. Can anyone help me or give me some tips on how to troubleshoot
this?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752053

Title:
nvidia-390 fails to boot graphical display

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+subscriptions

[Alberto Milone]

All the required components should be in Bionic now. I am closing this
bug report. Feel free to file a new bug report, if you experience any
further problems with the driver.

P.S. disabling the discrete GPU (on systems with hybrid graphics) does
not work yet, but it will soon.

** Changed in: nvidia-graphics-drivers-390 (Ubuntu)
Status: Incomplete => Fix Released

** Changed in: mesa (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752053

Title:
nvidia-390 fails to boot graphical display

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+subscriptions

[Roman Dinga]

Is there an open bug for discrete GPU switch not working? Or should I
open a new one?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752053

Title:
nvidia-390 fails to boot graphical display

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+subscriptions

[Roman Dinga]

Ok I see that there already is a bug for this
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1752739
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752053

Title:
nvidia-390 fails to boot graphical display

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+subscriptions

[netslovdlyasnov]

after nvidia-390 became nvidia-driver-390 I get back screen.
I have Acer vx5 laptop with nvidia 1050/Intel
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752053

Title:
nvidia-390 fails to boot graphical display

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+subscriptions

[siddesh kadam]

same problem i got black flickering screen on del 5558 , i have 920m
please suggest me which stable graphics driver can i use right now i am
unable to use tensorflow because of this , right now it is working on
nouveau drivers which has got set automatically by the sysytem , m
running linux ubuntu 64 bit .

** Attachment added: "this is the problem plaese twkl me which stable version , that i can install right now"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1752053/+attachment/5095870/+files/alternate_drivers
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752053

Title:
nvidia-390 fails to boot graphical display

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+subscriptions

[Lysenko Denis]

You may try this ppa https://launchpad.net/~graphics-
drivers/+archive/ubuntu/ppa just updated driver from this rep on 18.04
and succesfully booted.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752053

Title:
nvidia-390 fails to boot graphical display

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+subscriptions

[siddesh kadam]

i have tried the above link for Ubuntu 16.04 not working with nvidia
drivers (390) i have del 5558 and 920m graphics . (same flickering
screen ) , reverted back to nouveau drivers .
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752053

Title:
nvidia-390 fails to boot graphical display

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+subscriptions

[netslovdlyasnov]

I have tried graphics-drivers ppa and it doesn't work on 18.04.
On blank screen xrandr --listmonitors returns "Monitors: 0"


But everything works ok with ubuntu 16.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752053

Title:
nvidia-390 fails to boot graphical display

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+subscriptions

[Giraffe]

I'm having the shame issue with nvidia-390 just upgraded to Bionic i
have a Dell Precision 7510 with a Quadro M2000M
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752053

Title:
nvidia-390 fails to boot graphical display

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+subscriptions

[Bret Ancowitz]

Same issue with Nvidia 390 with Ubuntu Budgie 18.04 beta 2, with an
MX-150 Nvidia on a Xiaomi Air 13.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752053

Title:
nvidia-390 fails to boot graphical display

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+subscriptions

[Michael Brown]

Same issue with nvidia 390. I was able to fix for a couple of days by
installing MATE, but am back to square one after updating packages
today.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752053

Title:
nvidia-390 fails to boot graphical display

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+subscriptions

[Renaud Lepage]

By accident, I upgraded some parts to 390, so I just gave up and tried
to upgrade *all* the packages to 390, instead of having some from
graphics-drivers and some from partner. Lo and behold, I think I'm on
partner-provided drivers now, because everything works on 390.48 and I
have multiple independent packages for the nvidia drivers, instead of
the (simplified) limited number graphics-drivers provides.

No idea if I'm a unique case.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752053

Title:
nvidia-390 fails to boot graphical display

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+subscriptions

[Horst Schirmeier]

For me this is still broken with -proposed packages although this bug
has "Fix Released" status: When I have xserver-xorg-video-nvidia-390
390.48-0ubuntu1 installed, the system boots into a back screen.
Without, LightDM comes up as expected.

lspci excerpt (on a ThinkPad T460p):
00:02.0 VGA compatible controller: Intel Corporation HD Graphics 530 (rev 06)
02:00.0 3D controller: NVIDIA Corporation GM108M [GeForce 940MX] (rev a2)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752053

Title:
nvidia-390 fails to boot graphical display

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+subscriptions

[Luke Williams]

I have an Asus ROG GL703VD and have a similar issue. The display shows the ROG display, then flashes purple for a second (Grub menu splash before the Ubuntu splash logo, which doesn't display on the laptop, but does on the HDMI display) then goes blank and never comes online. Even pressing CTRL+ALT+F1-6 does not switch between virtual terminals on the laptop display, it does shift on the mirrored HDMI display. The only way to get a display is to hook up a monitor to the HDMI port and then logging in and setting the display to mirror mode. In fact, this is the only way to install Bionic on the device as even booting the install media with nouveau blacklisted doesn't work. In previous releases, running nouveau.modeset=0 would bring up the display properly and then you could install, but with Bionic, this is does not work. Also, installing the Bionic kernel in Xenial or Artful creates the same condition for those releases.
I have looked at the logs and settings everywhere, and from what I can tell everything appears to be loading properly. Gnome sees both displays when connected, but the laptop display remains black.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752053

Title:
nvidia-390 fails to boot graphical display

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+subscriptions

[Horst Schirmeier]

Additional side effect: Bionic sometimes fails to come back from S3 and
stays frozen with a black screen.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752053

Title:
nvidia-390 fails to boot graphical display

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+subscriptions

[hunter`]

(on ubuntu 18.04 beta 2)i had the same problem after upgrading to
nvidia-drivers-390.48, than i could not login even using nouveau after
removing all nvidia driver.

GDM3 could not manage to boot properly but just installing lightdm and
setting it to default let me login successfully (i did not remove gdm so
it was not necessary to do so to fix it)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752053

Title:
nvidia-390 fails to boot graphical display

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+subscriptions

[chadotter]

I upgraded to Bionic using a GeForce 950 and got a blank screen when
lightdm should have been visible. The only way I have been able to get
it working has been to delete /etc/X11/xorg.conf which was being used
before since my card was overclocked. If nvidia-xconfig is used later
and creates xorg.conf again the display breaks again until xorg.conf is
removed.

The actual text in xorg.conf was the same as what was working previously
with artful and nvidia-384.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752053

Title:
nvidia-390 fails to boot graphical display

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+subscriptions

[Biswajit biswas]

All things as mentioned above are garbage................
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752053

Title:
nvidia-390 fails to boot graphical display

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+subscriptions

[Horst Schirmeier]

Seems to have been fixed by a recent update; boots into SDDM now as
expected, using nvidia-drivers-390.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752053

Title:
nvidia-390 fails to boot graphical display

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+subscriptions

[Nguyen Xuan Viet]

I still encounter this issue after upgrade my bionic to the latest update.
The only way to boot to graphic shell is config to using lightdm as default.
Now I'm in unity session and try to install nvidia-396 to see if it fix this issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752053

Title:
nvidia-390 fails to boot graphical display

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+subscriptions

[Nguyen Xuan Viet]

Same issue with nvidia-396, I must config lightdm as default display manager.
After that I can login to ubuntu and ubuntu-unity sessions.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752053

Title:
nvidia-390 fails to boot graphical display

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+subscriptions

[netslovdlyasnov]

It started to work with 390.48-0ubuntu3

Working xorg.conf:


Section "ServerLayout"
Identifier "layout"
Screen 0 "nvidia"
Inactive "intel"
EndSection

Section "Device"
Identifier "intel"
Driver "modesetting"
BusID "PCI:***@0:2:0"
Option "AccelMethod" "None"
EndSection

Section "Screen"
Identifier "intel"
Device "intel"
EndSection

Section "Device"
Identifier "nvidia"
Driver "nvidia"
BusID "PCI:***@0:0:0"
Option "ConstrainCursor" "off"
EndSection

Section "Screen"
Identifier "nvidia"
Device "nvidia"
Monitor "Monitor0"
Option "AllowEmptyInitialConfiguration" "on"
Option "IgnoreDisplayDevices" "CRT"
EndSection

Section "Monitor"
Identifier "Monitor0"
VendorName "Unknown"
ModelName "Unknown"
Option "DPMS" "on"
EndSection
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752053

Title:
nvidia-390 fails to boot graphical display

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+subscriptions

[Ivan Antonijevic]

I have same problem. After dist-upgrade from 17.10 to 18.04. I get black
screen, and tty only.

I can startx after removing nvidia

sudo apt-get purge nvidia*

sudo apt dist-upgrade

and remove old xorg.conf

sudo mv /etc/X11/xorg.conf /etc/X11/xorg.conf_bck

Now I can get X with startx, but on boot I still getting only black
screen and tty.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752053

Title:
nvidia-390 fails to boot graphical display

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+subscriptions

[Jean-Philippe Vignolo]

Having more or less the same bug as anybody here, but with final Bionic
18.04.

I tried what proposed on #29 and #47 => installing from ppa :
https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa without
success (either 390 or 396 version of drivers) without success

Tried also installing lightdm instead of gdm3 which just get me a dark
screen.

Reverted back to Nouveau drivers doing what Ivan did in #78, I managed
to do a startx and get into gnome desktop. Then I rebooted, and gdm3 was
just fine and managed to login.

But after another reboot I could just access to gdm3 but system seemed
hangs after login (fixed cursor in middle of a dark screen). If I play
with alt+ctrl+f1 , f2 It turns back to gdm3 login screen. alt+ctrl+f3
gets me to a standard text login.

I managed to properly boot again after doing a sudo dpkg-reconfigure
gdm3 but it worked only once.

Finally, out of desperation, I did another sudo apt-get install nvidia-
driver-396 and now everything is working :) Go figure...

My guess is that removing the old xorg.conf file did the trick for me
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752053

Title:
nvidia-390 fails to boot graphical display

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+subscriptions

[Ivan Antonijevic]

It's better now. After #78 I run

sudo service gdm3 start
sudo dpkg-reconfigure gdm3

sudo add-apt-repository ppa:graphics-drivers/ppa

sudo apt-get update
sudo apt-get upgrade

activate nvidia-driver-396, and now works, but X is started on
ctrl+alt+F2, not on F7, and on F1 I get only mouse pointer, and system
blocked :(
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752053

Title:
nvidia-390 fails to boot graphical display

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+subscriptions

[Haneef Mubarak]

I upgraded from Kubuntu 17.10 to 18.04 and have the same issue. I was on
the graphics-drivers ppa, so I did a ppa-purge but that was to no avail.
For me, the weird thing is that it *seamlessly* says that it switched
fine, but that it still just uses the NVidia dGPU instead of the Intel
iGPU.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752053

Title:
nvidia-390 fails to boot graphical display

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+subscriptions

[Haneef Mubarak]

I am also encountering this bug, after upgrading from Kubuntu 17.10 to
18.04.

For me, initially only my Intel driver wouldn't work (with PRIME) - it
would instead just go ahead and use the NVidia driver (even when PRIME
said Intel was in use).

However, upgrading to {xserver-xorg-video-nvidia-396,nvidia-driver-396
,nvidia-utils-396} via the graphics-drivers ppa results in neither
operating correctly and the fallback llvmpipe software renderer being
used.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752053

Title:
nvidia-390 fails to boot graphical display

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+subscriptions

[Manvydas]

Upgraded from 17.10 to 18.04 less than an hour ago on my laptop.

I'm using nvidia-driver-396 from the graphics-drivers ppa
(https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa) with gdm3.
At first, I couldn't even get to the login screen.

#79 (Jean-Philippe Vignolo (popopow)) was right - it seems to be related
to the xorg.conf file. Removing it solved the problem for me. Tried
rebooting a few times and everything continues to work.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752053

Title:
nvidia-390 fails to boot graphical display

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+subscriptions

[claudio@ubuntu]

** Also affects: xserver-xorg-video-nouveau (Ubuntu)
Importance: Undecided
Status: New

** Changed in: xserver-xorg-video-nouveau (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752053

Title:
nvidia-390 fails to boot graphical display

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+subscriptions

[claudio@ubuntu]

To me it looks that there is something broken wider than what most comments touch.
On my laptop with a NVIDIA Corporation GK107M [GeForce GT 750M] (prime) card, since 17.10 (including 18.04):
- nouveau drivers work very poorly with Xorg: too slow to play video (tearing, drop frames, etc).
- nouveau drivers work very poorly with Xorg: too slow to play video (tearing, drop frames, etc).
- nvidia-340 drivers with prime selection of both nvidia and intel: No Xorg, no Wayland.
- nvidia-390 drivers with prime selection of nvidia: No Xorg, Waylang stuck in login loop.
- nvidia-390 drivers with prime selection of intel on Xorg: too slow to play video (tearing, drop frames, etc).
- nvidia-390 drivers with prime selection of intel on Wayland: everything seems to work.

I would prefer to run Xorg on 18.04 because Wayland on 17.10 crashed one
in a while probably due to extensions.

Ping if more info is needed (logs, tests) or it this should be moved to
its own ticket.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752053

Title:
nvidia-390 fails to boot graphical display

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+subscriptions

[Bernadette Addison]

Having the same issue as most users here. Installed fresh copy of 18.04
to brand new hard drive, brand new dell XPS 15. Nvidia GTX 1050 on
board....Installed drivers nvidia-390 from ppa. Now the machine will
only boot to black dos screen and I am not even able to get to the tty
because none of the combination key commands work. My only recourse is
to install from scratch again. Tried this with the normal installation
and with the minimal installation. Nvidia drivers simply do not work.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752053

Title:
nvidia-390 fails to boot graphical display

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+subscriptions

[Bernadette Addison]

Edited to add: I’ve also tried disabling the nouveau-nvidia drivers
before and then after installing the nvidia-390 drivers but still not
working.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752053

Title:
nvidia-390 fails to boot graphical display

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+subscriptions

[Ibrahim Essam]

I had the same problem after upgrading from ubuntu 17.10
It was fixed by removing xorg.conf file
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752053

Title:
nvidia-390 fails to boot graphical display

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+subscriptions

[netslovdlyasnov]

In my case removing xorg.conf didn't help because nvidia driver reported
"no device found", so I had to use minimal xorg.conf (from my previous
answer) to make the driver find the card (BusID "PCI:***@0:0:0")

Also I confirm that nouveau driver is buggy and hangs computer on
switching consoles.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752053

Title:
nvidia-390 fails to boot graphical display

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+subscriptions

[omar reddam]

Still having the issue as today (18.04 final) with a GTX 1050 Ti (Asus Prime X299-Deluxe mobo).
Frozen black screen at startup after trying versions 390 & 396 of the NVidia drivers.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752053

Title:
nvidia-390 fails to boot graphical display

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+subscriptions

[Bernadette Addison]

@omar reddam - I also have the GTX 1050 in my new dell XPS-15 laptop.
After deleting xorg.conf as recommended here, I went a step further and
performed this command to blacklist nouveau:

$ sudo bash -c "echo blacklist nouveau > /etc/modprobe.d/blacklist-nvidia-nouveau.conf"
$ sudo bash -c "echo options nouveau modeset=0 >> /etc/modprobe.d/blacklist-nvidia-nouveau.conf"

Then I updated initramfs:
$ sudo update-initramfs -u

And lastly, I installed the nvidia software package via "sudo apt
install nvidia-390" before rebooting.

BLACK SCREEN.....*sigh*

Has anyone tried to download the bin files directly from nvidia.com website?
What were the results?

I think I'll go ahead and try that. Will report back my findings.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752053

Title:
nvidia-390 fails to boot graphical display

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+subscriptions

[Bernadette Addison]

so, I downloaded various versions of the Linux drivers directly from
Nvidia.com website. Went thru the installation process - each time
starting over from scratch, formatting and reinstalling Ubuntu 18.04 so
I would have a "blank canvas" to work with. This process failed too.
My thinking was that perhaps the Nvidia drivers may/may not contain a
component that would not break the laptop. But this was a futile
effort.

Guess I will wait for a few more suggestions/ideas on how to get this
graphics card working once and for all.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752053

Title:
nvidia-390 fails to boot graphical display

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+subscriptions

[Kyle Weber]

Hopeful this bug was fixed (as it improperly states above), I did a
fresh install on my machine with an Nvidia 1060. It will boot, then go
to a black screen on login, etc. I tried what people mentioned above,
but was not able to get a stable working system. I went back to 17.10
and have not had any issues since.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752053

Title:
nvidia-390 fails to boot graphical display

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+subscriptions

[Alexander Kops]

Dell XPS-15 with GTX 1050 user reporting in, for me just deleting xorg.conf and rebooting worked (using nvidia-390).
I had upgraded from 17.10.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752053

Title:
nvidia-390 fails to boot graphical display

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+subscriptions

[Nguyen Xuan Viet]

I think there is something wrong with gdm3/wayland/NVIDIA proprietary driver.
If I config gdm3 as default display manager, when rebooted, I have a black screen but I'm able to switch to other tty by press crtl-alt-f2 to f7.
Then I edit /etc/gdm3/custom.conf uncomment line 7th to WaylandEnable=false then rebooted, then I have system hange after reboot :(. It seems that the OS is stuck in gdm3 service.
I tried to change/regenerate/delete xorg.conf but it simply doesn't work. So I think xorg.conf is not the root cause for me.

If I uninstall all nvidia stubs and install nouveau xorg driver, the
system is able to boot to graphic shell with gdm3 as a display manager.
Unfortunately, the nouveau driver does not support CUDA computing
framework and the performance of this driver is very poor when compare
to the binary one.

If I config to use lightdm as default DM, it works with NVIDIA binary
driver, but this is not what I expected. I expect the system have to
work with gdm3, ubuntu-xorg session and NVIDIA proprietary driver. I
have an app that need xorg session and CUDA, so I must install NVIDIA
binary driver.

PS: If you are able to boot to graphic mode but stuck with login loop,
you could try to delete the ~/.Xauthority file then reboot. It worked
for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752053

Title:
nvidia-390 fails to boot graphical display

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+subscriptions

[Nguyen Xuan Viet]

My hardware configuration is CPU Intel E3 1231 v3 (no iGPU), GPU NVIDIA
GTX 1060 6GB, RAM DDR3 16GB
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752053

Title:
nvidia-390 fails to boot graphical display

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+subscriptions

[Tom]

Dell XPS15 9560 - System is now usable, after nightmare of trials and about 50 reboots.
If I recall correctly: Ctrl-Alt-F2 / F3 on login prompt; sudo update; sudo apt purge nvidia*; sudo apt install nvidia-390;
I switched to Wayland and back, all broken again, so then again in tty at login prompt: sudo nvidia-xconfig (to create /etc/X11/xorg.conf) and then sudo rm /etc/X11/xorg.conf No idea why to rm xorg directly after creating to make discrete graphics work and put Nvidia back in its cage, but it did. Tried sudo nvidia-settings but that does not work as system is convinced nvidia is not loaded...

Also for what it is worth, I added GRUB_CMDLINE_LINUX_DEFAULT="splash
acpi_rev_override=1 nouveau.runpm=0" as without the acpi override logout
takes ages...

I wont even dream about the good old days of 17.04/17.10 when I could
switch Nvidia / Prime on and off... Note to myself: avoid Nvidia in
laptops like the plague. Please... read this again, Tom, in 3 years when
a new laptop is due **no optimus/prime/Nvidia on laptops** ... !!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752053

Title:
nvidia-390 fails to boot graphical display

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+subscriptions