xubuntu / bionic / nvidia-driver-390 can only be used by one user at a time

Bug #1757202 reported by Burt P. on 2018-03-20
This bug affects 5 people
Affects Status Importance Assigned to Milestone
nvidia-graphics-drivers-390 (Ubuntu)

Bug Description

In XUbuntu 18.04 bionic, with the nvidia-driver-390, ony one user can use the nvidia driver at a time.
A second user logged-in gets stuck at 640x480 and llvmpipe for OpenGL.
Before the update around 11-12 March 2018, it was possible for multiple users to use the nvidia driver.

First User
For the first user to log in, they get this:

lsb_release -a:
Distributor ID: Ubuntu
Description: Ubuntu Bionic Beaver (development branch)
Release: 18.04
Codename: bionic

apt-cache policy nvidia-driver-390:
  Installed: 390.42-0ubuntu1+gpu18.04.1
  Candidate: 390.42-0ubuntu1+gpu18.04.1
  Version table:
 *** 390.42-0ubuntu1+gpu18.04.1 500
        500 http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu bionic/main amd64 Packages
        100 /var/lib/dpkg/status
     390.42-0ubuntu1 500
        500 http://us.archive.ubuntu.com/ubuntu bionic/restricted amd64 Packages

07:00.0 VGA compatible controller: NVIDIA Corporation GK106 [GeForce GTX 660] (rev a1)

glxinfo | grep renderer:
OpenGL renderer string: GeForce GTX 660/PCIe/SSE2

Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 16384 x 16384
DVI-I-0 disconnected (normal left inverted right x axis y axis)
DVI-I-1 disconnected (normal left inverted right x axis y axis)
HDMI-0 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 819mm x 461mm
   1920x1080 60.00*+ 60.00 59.94 50.00 23.98 60.00 50.04
   1280x1024 75.02
   1280x720 60.00 59.94 50.00
   1024x768 75.03 70.07 60.00
   800x600 75.00 72.19 60.32
   720x576 50.00
   720x480 59.94
   640x480 75.00 59.94 59.93
DP-0 disconnected (normal left inverted right x axis y axis)
DVI-D-0 disconnected (normal left inverted right x axis y axis)
DP-1 disconnected (normal left inverted right x axis y axis)

After switching to a second user

glxinfo | grep renderer:
OpenGL renderer string: llvmpipe (LLVM 5.0, 128 bits)

Screen 0: minimum 640 x 480, current 640 x 480, maximum 640 x 480
default connected 640x480+0+0 0mm x 0mm
   640x480 73.00*

Roland65 (roland65) wrote :

I can confirm the bug on Xubuntu 18.04.
My graphics card is an nVidia GeForce GTX 570 (GF110).

I tried with a fresh Ubuntu 18.04 (and not Xubuntu) and there's no bug.

So I think the issue is related to lightdm, which is used on Xubuntu and not Ubuntu.

Roland65 (roland65) wrote :

The bug is not related to lightdm because it also occurs with gdm3.

I have several Linux boxes with graphic cards nVidia GTX 570, GTX 670 and Quadro K2000, and the problem appears on each one, with different resolutions for the second user and sometimes with a very slow rendering.

I analyzed the Xorg logs and found that for the second user, the ModulePath is incorrectly set to "/usr/lib/xorg/modules" instead of "/usr/lib/x86_64-linux-gnu/nvidia/xorg". Thus the nvidia modules are not found when the X server starts. Note that this problem does not occur for the first user...

So, here is a workaround for this problem:

1. Create an xorg.conf file for your nVidia device. All you have to do for this is to launch the command:

sudo nvidia-xconfig

This will create a file /etc/X11/xorg.conf.

2. Edit the created file /etc/X11/xorg.conf and add at the end the lines:

Section "Files"
 ModulePath "/usr/lib/x86_64-linux-gnu/nvidia/xorg"
 ModulePath "/usr/lib/xorg/modules"

3. Save and restart the X server. Now, for the first and second user you should have the nvidia driver in use, with the correct resolution and fast rendering. You can check it using the command:

glxgears -info |grep NVIDIA

which should return the nvidia opengl version.

Note, there is also a problem of slow scrolling in the virtual console (Ctrl-Alt-F1). To solve this, edit /etc/default/grub and set the GRUB_CMDLINE_LINUX variable as:


then do:

sudo update-grub

and reboot. Now, the scrolling speed in the virtual console should be very fast.

Launchpad Janitor (janitor) wrote :

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

Changed in nvidia-graphics-drivers-390 (Ubuntu):
status: New → Confirmed
spike speigel (frail-knight) wrote :

Same issue with Xubuntu 18.10 Cosmic and nvidia-driver-415.

tags: added: bionic cosmic nvidia
spike speigel (frail-knight) wrote :

Fixed with:

Section "Files"
    ModulePath "/usr/lib/x86_64-linux-gnu/xorg"
    ModulePath "/usr/lib/xorg/modules"

launchpadmember (lpuser1138) wrote :

What should be done if everything in post #2 is set as directed, but on the following step...:
glxgears -info |grep NVIDIA

...the following is returned?:
X Error of failed request: BadValue (integer parameter out of range for operation)
  Major opcode of failed request: 154 (GLX)
  Minor opcode of failed request: 3 (X_GLXCreateContext)
  Value in failed request: 0x0
  Serial number of failed request: 31
  Current serial number in output stream: 32

NOTE: The workaround provided in post #2 above did in fact solve this issue for a few months on my setup until this morning when this problem started happening again.

My computers Specs:
CPU: Two Intel(R) Xeon(R) CPU E5-2687W v3 @ 3.10GHz
Mem: 64GB
OS: Xubuntu 18.04.2 LTS
Graphics: NVIDIA Quadro P6000
Software & Updates panel:
  [Ubuntu Software Tab]: (The following are checked)
  * Canonical-supported free and open-source software (main)
  * Community-maintained free and open-source software (universe)
  * Proprietary drivers for devices (restricted)
  * Software restricted by copyright or legal issues (multiverse)
  [Additional Drivers Tab]: (The following graphics driver is in use)
  * Using NVIDIA driver metapackage from nvidia-driver-390 (proprietary, tested)

If I'm remembering correctly this setup is currently utalizing some of the functionality provided by the proprietary drivers that can not be provided by the more generic Noveau driver. I can't quite remember what this is at the moment but I would prefer to stick with the proprietary driver if at all possible while solving this problem.

Please let me know if there are any other logs or information that I might be able to report in order to help verify or narrow down what is causing this issue to re-occur after the fix provided in step #2 has been applied.


To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers