Screen lock crashes after playing fullscreen games

[Tom Cook]

This appears to be new after an upgrade to 24.04.

My laptop has a 2560x1600 panel. When I play a fullscreen Steam game (in this case Satisfactory) set to that resolution, afterwards the virtual display size in GNOME is increased, so that if I move the mouse off the bottom or right-hand sides of the screen then the desktop scrolls. The GNOME shell has not resized and the extra virtual space is just grey. If I then suspend the system by shutting the lid and then unsuspend it again, the lock screen does not appear and I get a brief glimpse of the screen content before the "Something went wrong" screen and a forced log off. After logging off, everything is okay again. I am using the Xorg display session.

This only happens after playing the game and therefore when the virtual display size is increased. My guess is that GNOME Shell is not handling the mismatched display sizes.

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: gnome-shell 46.0-0ubuntu5.1
ProcVersionSignature: Ubuntu 6.8.0-35.35-generic 6.8.4
Uname: Linux 6.8.0-35-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.28.1-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: GNOME
Date: Thu Jun 6 08:39:09 2024
DisplayManager: gdm3
InstallationDate: Installed on 2023-12-05 (184 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1)
RelatedPackageVersions: mutter-common 46.0-1ubuntu9
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to noble on 2024-04-28 (39 days ago)

[Daniel van Vugt (vanvugt)]

The scrolling issue is bug 2066126 so we can ignore that here.

As for the crash, please follow these steps:

1. Run these commands:
    journalctl -b0 > journal.txt
    journalctl -b-1 > prevjournal.txt
and attach the resulting text files here.

2. Look in /var/crash for crash files and if found run:
    ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

3. If step 2 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us.

Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself.

[Daniel van Vugt (vanvugt)]

Are you locking the screen while in the overview? If so then a fix for that is coming:
https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/3252

[Tom Cook (tom-k-cook)]

Attaching journal.txt

[Tom Cook (tom-k-cook)]

I'm not locking the screen while in the overview.

This happened this morning and I'm not absolutely sure that I'd had Satisfactory running beforehand. I've uploaded the journal files from this crash above.

The crash this morning produced crash files from chrome and vscode but I don't think these are a symptom rather than the cause; previous crashes have not produced these. There is a crash file for /usr/lib/xorg/Xorg but `ubuntu-bug --save bug.txt /var/crash/_usr_lib_xorg_Xorg.1000.crash` produces an empty file.

[Tom Cook (tom-k-cook)]

And the only whoopsie link is from January, ie before the upgrade to 24.04.

[Daniel van Vugt (vanvugt)]

I can't see any gnome-shell crashes there, but I can see kernel bug 2062426 causing the X server some problems. Please try the workarounds mentioned in bug 2060268.

[Tom Cook (tom-k-cook)]

I'm uncertain how to tell if I'm affected by that bug. I'm not seeing the main symptom - a "phantom" display in settings. But I'm only running Nvidia drivers version 535, so possibly that symptom doesn't show up until you install 545?

I do have a /dev/card0 which is from the simple-framebuffer module. I'll try adding the initcall_blacklist but I don't think it'll do anything; AFAICT there is no simpledrm driver on the system, only simple-framebuffer, and I thought that module init methods and to match the name of the module? Or maybe not when it's not loaded as a module, IDK (and simple-framebuffer appears to be compiled-in on this system).

I saw the crash again this morning and again there are no crash files in /var/crash - the most recent was three days ago.

[Tom Cook (tom-k-cook)]

Also trying to set the kernel commandline with `sudo snap set system system.kernel.cmdline-append` appears to have crashed snapd. Quite what state that's left my system in is anyone's guess. It _might_ be bootable...

[Daniel van Vugt (vanvugt)]

The phantom display affects all Nvidia driver versions at the moment.

And yes simple-framebuffer is the same thing as simpledrm. I think the former is just the internal backend name. Which is reported by `drm_info` (from `sudo apt install drm-info`)?

[Tom Cook (tom-k-cook)]

I've managed to recover my system to the point that snap is working again - see #2068874 - but won't get a chance to test this just now.

Yes, drm_info reports card0 as simpledrm and card1 as nvidia-drm.