Wrong resolution at unlock screen

Bug #1760068 reported by Kev Bowring
72
This bug affects 13 people
Affects Status Importance Assigned to Milestone
light-locker (Ubuntu)
Invalid
Undecided
Unassigned
nvidia-graphics-drivers-340 (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

After coming out of suspend - the unlock screen is at 640x480 resolution.

Expect to see unlock screen at 1920x1080 resolution.

Using nvidia-340.

Previously tested using nouveau driver where resolution at unlock screen was correct.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: light-locker 1.8.0-1ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
Uname: Linux 4.15.0-13-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.20.9-0ubuntu2
Architecture: amd64
CurrentDesktop: XFCE
Date: Fri Mar 30 11:31:20 2018
InstallationDate: Installed on 2017-09-02 (209 days ago)
InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902)
SourcePackage: light-locker
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Kev Bowring (flocculant) wrote :
Revision history for this message
Sean Davis (bluesabre) wrote :

Doesn't seem to affect Intel graphics.

Card-1: Intel Haswell-ULT Integrated Graphics Controller
Card-2: NVIDIA GK107M [GeForce GT 745M]
Display Server: x11 (X.Org 1.19.6 )
drivers: modesetting,nouveau (unloaded: fbdev,vesa)
Resolution: 1920x1080@60.00hz
OpenGL: renderer: Mesa DRI Intel Haswell Mobile
version: 4.5 Mesa 18.0.0-rc5

Revision history for this message
Kev Bowring (flocculant) wrote :

doesn't affect nouveau either

Revision history for this message
Sean Davis (bluesabre) wrote :

Unable to confirm for nvidia-340, but also not sure it's fully installed. Installed via Software & Updates, and it says it's installed, but nvidia-settings has two tabs and this is inxi's output. If this is correct output, it seems to be working on nvidia-340 here.

$ inxi -G
Graphics: Card-1: Intel Haswell-ULT Integrated Graphics Controller
           Card-2: NVIDIA GK107M [GeForce GT 745M]
           Display Server: x11 (X.Org 1.19.6 )
           drivers: modesetting,nouveau (unloaded: nvidia,fbdev,vesa)
           Resolution: 1920x1080@60.00hz
           OpenGL: renderer: N/A version: N/A

Revision history for this message
Sean Davis (bluesabre) wrote :

Also no luck getting nvidia-driver-390 installed to test.

Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in light-locker (Ubuntu):
status: New → Confirmed
Revision history for this message
Hélio Nunes (dedalu-dedalu) wrote :

Me too. Xubuntu 18.04, fresh install.

It happens after resume from suspend and when I switch users (dm-tool switch-to-greeter). For the first user the resolution is correct:

user_a$ inxi -G
Graphics: Card: NVIDIA GT215M [GeForce GT 335M]
           Display Server: x11 (X.Org 1.19.6 ) driver: nvidia Resolution: 1600x900@59.98hz
           OpenGL: renderer: GeForce GT 335M/PCIe/SSE2 version: 3.3.0 NVIDIA 340.106

user_a$ xrandr --query
Screen 0: minimum 8 x 8, current 1600 x 900, maximum 8192 x 8192
VGA-0 disconnected (normal left inverted right x axis y axis)
LVDS-0 connected 1600x900+0+0 (normal left inverted right x axis y axis) 345mm x 194mm
   1600x900 59.98*+
HDMI-0 disconnected (normal left inverted right x axis y axis)

But for the second user:

user_b$ inxi -G
Graphics: Card: NVIDIA GT215M [GeForce GT 335M]
           Display Server: x11 (X.Org 1.19.6 ) driver: nvidia
           Resolution: 640x480@73.00hz
           OpenGL: renderer: N/A version: N/A

user_b$ xrandr --query
xrandr: Failed to get size of gamma for output default
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*

Note: user_b screen resolution is fine if he is the only one using the system. The problem happens only when he is the second.

Thanks.

Revision history for this message
Theo Linkspfeifer (lastonestanding) wrote :

This is a duplicate of bug 1757202.

Revision history for this message
THIAGO AZEVEDO GARCIA (thiagoufg) wrote :

It affects me too... I have an ATI Mobility Radeon HD 5470. And it has nothing to do with 2 users at the same time, because it happens to me with a single user logged in.

Revision history for this message
Theo Linkspfeifer (lastonestanding) wrote :

Thiago, this bug may be caused by having two Xorg instances (the user session and the unlock screen which runs in another VT) accessing the graphics driver. And up until now, only the nvidia driver was reported to be part of the problem.

Please check the logs files in /var/log/lightdm for any hints.

Revision history for this message
Theo Linkspfeifer (lastonestanding) wrote :

Most likely not a bug in light-locker.

Changed in light-locker (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in nvidia-graphics-drivers-340 (Ubuntu):
status: New → Confirmed
Revision history for this message
Theo Linkspfeifer (lastonestanding) wrote :

A new version of nvidia-graphics-drivers-340 is available in -updates.

Please check if it resolves the bug.

https://launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/340.107-0ubuntu0.18.04.1

Changed in light-locker (Ubuntu):
status: Incomplete → Invalid
Revision history for this message
Hélio Nunes (dedalu-dedalu) wrote :

I'm using the 340.107 and the problem persists.

As I told in #7, a second X user is affected too, not only the unlock screen. That's the big problem with this bug: it is not only an aesthetic problem.

I confirm that all works as intended with the nouveau driver.

I did not found any error messages in the /var/log/lightdm/ files.

Where and what should I look to contribute more?

Thanks.

Revision history for this message
Theo Linkspfeifer (lastonestanding) wrote :

Well, as mentioned in comment #10, this bug is not limited to the unlock screen (which happens to be a second Xorg instance if you use light-locker).

Does the workaround in bug 1757202 fix the issue for you?

Revision history for this message
Hélio Nunes (dedalu-dedalu) wrote :

Thank you, Theo!

Based on that workaround, I have added

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

to the xorg.conf and it's working!

Thanks!

Revision history for this message
Joshua Hartwell (joshuad) wrote :

That work around did not work for me.

This bug also affects my TTY displays.

Xubuntu 18.04
NVIDIA GeForce GTX 750Ti
64-bit Intel i5-8400

Revision history for this message
Joshua Hartwell (joshuad) wrote :

Nevermind, the full solution from the link did in fact work for me. Using nvidia-driver-390.

I am copy/pasting the solution here for any other users:

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"
EndSection

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:

--- Note by JoshuaD: I did not try anything below this line -----

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:

GRUB_CMDLINE_LINUX="video=vesafb:mtrr:3,ywrap"

then do:

sudo update-grub

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

Revision history for this message
Hélio Nunes (dedalu-dedalu) wrote :

It's almost the same workaround for all nvidia versions: you must inform where is the nvidia_drv and libglx.

For nvidia-340, you must add:

Section "Files"
        ModulePath "/usr/lib/nvidia-340/xorg"
        ...
EndSection

Other versions will need other path.

Revision history for this message
spike speigel (frail-knight) wrote :

Same issue with Xubuntu 18.10 Cosmic and nvidia-driver-415. As mentioned above it is not only the lock screen, but the boot splash screens as well.

tags: added: cosmic
Revision history for this message
spike speigel (frail-knight) wrote :

In my instance (Xubuntu 18.10 with nvidia 415 from the graphics drivers PPA) I was able to fix the lock screen resolution by using the following:

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

My system has /usr/lib/nvidia, but no xorg directory located there. Likewise, no nvidia/xorg directory path under /usr/lib/x86_64-linux-gnu. There was only xorg as listed above with my corresponding nvidia modules.

This workaround does not fix the TTY screen resolution or the Xubuntu boot/loading spash.

Revision history for this message
spike speigel (frail-knight) wrote :

~$ inxi -G
Graphics: Device-1: NVIDIA GP104 [GeForce GTX 1070] driver: nvidia v: 415.27
           Display: x11 server: X.Org 1.20.3 driver: nvidia resolution: 2560x1440~60Hz
           OpenGL: renderer: GeForce GTX 1070/PCIe/SSE2 v: 4.6.0 NVIDIA 415.27

~$ xrandr --query
Screen 0: minimum 8 x 8, current 2560 x 1440, maximum 32767 x 32767
DVI-D-0 disconnected (normal left inverted right x axis y axis)
HDMI-0 disconnected (normal left inverted right x axis y axis)
HDMI-1 connected primary 2560x1440+0+0 (normal left inverted right x axis y axis) 600mm x 340mm
   3840x2160 30.00 + 29.97 25.00 23.98
   2560x1440 59.95*
   1920x1080 60.00 59.94 29.97 60.00
   1600x900 60.00
   1280x1024 60.02
   1280x800 59.81
   1280x720 60.00 59.94
   1152x864 60.00
   1024x768 60.00
   800x600 60.32
   720x480 59.94
   640x480 59.94 59.93
DP-0 disconnected (normal left inverted right x axis y axis)
DP-1 disconnected (normal left inverted right x axis y axis)
DP-2 disconnected (normal left inverted right x axis y axis)
DP-3 disconnected (normal left inverted right x axis y axis)

tags: added: disco
Revision history for this message
spike speigel (frail-knight) wrote :

With Xubuntu 19.04 Disco Dingo and the 418.56 nvidia drivers it appears now my system has:

/usr/lib/x86_64-linux-gnu/nvidia-418/xorg

So added the below options to /etc/X11/xorg.conf fixes the issue:

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

I'm not sure why the file/folder structure differed with Xubuntu 18.10 and 415.xx nvidia drivers.

Revision history for this message
Miqueias (miqueiaspenha) wrote :

Problem solved with solution

Estou usando a versão 430

/usr/lib/x86_64-linux-gnu/nvidia-430/xorg

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

Thank you very much!

Revision history for this message
Ofloo (ofloo) wrote :

Thank you very much, ubunt 18.04 LTS and it fixed my issue as well. However I also tested nvidia driver 430 not tested and it doesn't seem to work in that driver.

Revision history for this message
Thiago Oliveira (thiagomdo1) wrote :

I solved it in Desktop Settings, by changing the Window Manager from "Xfwm4 + Compositing" to "Compiz".

Revision history for this message
Sean Gray (sean-gray) wrote :

Okay.For nvidia-435.21 I fixed it with:

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

Light-locker displays the correct resolution now.

//this is insane. They need to patch this on the light-locker side soon.

Revision history for this message
Jarno Suni (jarnos) wrote :

ls /usr/lib/x86_64-linux-gnu/nvidia*
tells "No such file or directory"

Revision history for this message
Jarno Suni (jarnos) wrote :

I used
sudo nvidia-xconfig
to create initial /etc/X11/xorg.conf file like told in #18

Then added

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

in /etc/X11/xorg.conf
The last directory is empty, so I guess that is why it is ok to comment it out.
Works for the login screen, but other TTY:s have small resolution.

Revision history for this message
Jarno Suni (jarnos) wrote :

Oh, I found alternative way that works for GRUB menu resolution and console resolution, too, and no need to create /etc/X11/xorg.conf.

Edit /etc/default/grub accordingly:
GRUB_GFXMODE=1280x1024,auto
GRUB_GFXPAYLOAD_LINUX=keep,text

You may want to or have to use a different resolution than 1280x1024.

Thereafter "sudo update-grub" and reboot.

Reference: https://linuxconfig.org/how-to-increase-tty-console-resolution-on-ubuntu-18-04-server
https://www.gnu.org/software/grub/manual/grub/html_node/Simple-configuration.html

Revision history for this message
paolo (palopdsthsa) wrote :

well, the same situation.
System: Host: diacon Kernel: 4.15.0-70-generic x86_64 bits: 64 Desktop: Xfce 4.12.3 Distro: Linux Mint 19.2 Tina
Machine: Type: Desktop Mobo: ASUSTeK model: PRIME X370-A v: Rev X.0x serial: <root required>
           UEFI [Legacy]: American Megatrends v: 5220 date: 09/12/2019
CPU: Topology: 8-Core model: AMD Ryzen 7 2700X bits: 64 type: MT MCP L2 cache: 4096 KiB
           Speed: 1885 MHz min/max: 2200/3700 MHz Core speeds (MHz): 1: 1885 2: 1888 3: 2192 4: 2076 5: 1912 6: 2062 7: 2074
           8: 2065 9: 1884 10: 1887 11: 2054 12: 1889 13: 1886 14: 1889 15: 2193 16: 2190
Graphics: Device-1: NVIDIA GP106 [GeForce GTX 1060 3GB] driver: nvidia v: 430.50
           Display: x11 server: X.Org 1.19.6 driver: nvidia unloaded: fbdev,modesetting,nouveau,vesa
           resolution: 1920x1080~60Hz
           OpenGL: renderer: GeForce GTX 1060 3GB/PCIe/SSE2 v: 4.6.0 NVIDIA 430.50
Audio: Device-1: NVIDIA GP106 High Definition Audio driver: snd_hda_intel
           Device-2: Advanced Micro Devices [AMD] Family 17h HD Audio driver: snd_hda_intel
           Sound Server: ALSA v: k4.15.0-70-generic
Network: Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8169
           IF: enp7s0 state: up speed: 100 Mbps duplex: full mac: 40:b0:76:5e:8e:51
Drives: Local Storage: total: 1.58 TiB used: 297.63 GiB (18.4%)
           ID-1: /dev/sda vendor: Samsung model: SSD 860 EVO 500GB size: 465.76 GiB
           ID-2: /dev/sdb vendor: SanDisk model: SDSSDA240G size: 223.57 GiB
           ID-3: /dev/sdc vendor: Western Digital model: WD5000AAKX-75U6AA0 size: 465.76 GiB
           ID-4: /dev/sdd vendor: Western Digital model: WD5003ABYX-01WERA1 size: 465.76 GiB
Partition: ID-1: / size: 245.98 GiB used: 47.76 GiB (19.4%) fs: ext4 dev: /dev/sda5
Sensors: System Temperatures: cpu: 38.5 C mobo: N/A gpu: nvidia temp: 35 C
           Fan Speeds (RPM): cpu: 0 gpu: nvidia fan: 0%
Info: Processes: 293 Uptime: 1h 23m Memory: 31.41 GiB used: 2.46 GiB (7.8%) Shell: bash inxi: 3.0.32

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

Other bug subscribers

Remote bug watches

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