incorrect screen resolution in wayland session

[Chris Hermansen]

Running a fresh install of Ubuntu 24.06 (ie not an upgrade from 23.10). Graphics card is NVIDIA GeForce RTX™ 3060 with 5120 X 1440 Samsung monitor. Configuration behaves as expected on xorg but switching to Wayland on login gives display resolution at ? X 1080. Settings application crashes under Wayland.

Until release of 24.06 this machine was running 23.10 which did not exhibit this problem.

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: xorg 1:7.7+23ubuntu3
ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
Uname: Linux 6.8.0-31-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus.0000.09.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.171.04 Tue Mar 19 20:30:00 UTC 2024
 GCC version:
ApportVersion: 2.28.1-0ubuntu3
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed May 15 07:45:30 2024
DistUpgraded: Fresh install
DistroCodename: noble
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 NVIDIA Corporation GA106 [GeForce RTX 3060] [10de:2503] (rev a1) (prog-if 00 [VGA controller])
   Subsystem: eVga.com. Corp. GA106 [GeForce RTX 3060] [3842:3657]
InstallationDate: Installed on 2024-04-27 (18 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
MachineType: Gigabyte Technology Co., Ltd. X570 AORUS PRO WIFI
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-31-generic root=UUID=4c1c0f5a-bb01-4985-92a3-b10dfd4acd1a ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/06/2020
dmi.bios.release: 5.14
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F12e
dmi.board.asset.tag: Default string
dmi.board.name: X570 AORUS PRO WIFI
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF12e:bd03/06/2020:br5.14:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSPROWIFI:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSPROWIFI:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
dmi.product.family: Default string
dmi.product.name: X570 AORUS PRO WIFI
dmi.product.sku: Default string
dmi.product.version: -CF
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.120-2build1
version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.5-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.12-1ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1build1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

[Chris Hermansen (c-hermansen)]

I thought to try adding a new user which would have fresh configuration files. This new user experienced the same or very similar problems (xorg session screen resolution seems fine, wayland session screen resolution is ? X 1080).

On first login (which was an xorg session) the screen resolution was set to 3840 x 1080. I used the Settings application to change it to 5120 X 1440. The resolution did not change at that point, but when I logged out and logged back in again, it was at that point 5120 X 1440.

So I infer from this (perhaps wrongly) that the problem is not caused by some crufty old configuration file.

Also, the Settings app reports two monitors for both users, when only one is connected. Not sure why.

[Daniel van Vugt (vanvugt)]

> Also, the Settings app reports two monitors for both users, when only one is connected. Not sure why.

See bug 2060268.

[Chris Hermansen (c-hermansen)]

Daniel:

Thanks for linking to https://bugs.launchpad.net/bugs/2060268. Solved my "ghost monitor" problem; I will report my experience on that bug.

Relative to the screen resolution - when I added the boot flag mentioned there to /etc/default/grub, rebooted and logged into an X (not Wayland) session, my screen was back to 3840 x 1080. However, when I went into Settings and changed the resolution to 5120 X 1440, this time the screen blanked briefly, then returned in the higher resolution and asked if I wanted to keep the setting. I selected "yes" and I continue to have the desired resolution as long I as I am using X.

However, logging into a Wayland session, my screen resolution is back to 3840 X 1080, and I still cannot run the Settings to try to change the resolution (the Settings icon appears briefly in the dock, then vanishes, and no apport is offered).

Another observation: looking at the GNOME login screen, I'm pretty sure it's in 3840 X 1080 mode as well (or at least, not in the higher resolution supported by this monitor), as the info on the screen appears larger than I recall it from April in 23.10.

[John Kizer (johnandmegh)]

Just checking a theory - does installing libnvidia-egl-wayland1 help with being able to open the Settings app, at least?

[Chris Hermansen (c-hermansen)]

John Kizer:

I installed libnvidia-egl-wayland1 versuib 1:1.1.13-1build1 from the repositories, and not only does Settings now work, but I can also change the screen resolution from the low-res 3840 X 1080 to the high-res value 5120 X 1440, and all seems to work just fine.

Thanks for sharing your theory!

If I see anything amiss I will report back.

*** UPDATE ***

I probably should have made it clear that I mean "works in the Wayland session". Also, I logged out and logged back in again and the new Wayland session remembered the previous screen resolution. So it seems I'm off to the races, for now anyway.