Screen lock crashes after playing fullscreen games
This bug report will be marked for expiration in 3 days if no further activity occurs. (find out why)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-shell (Ubuntu) |
Incomplete
|
Undecided
|
Unassigned |
Bug Description
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
ProcVersionSign
Uname: Linux 6.8.0-35-generic x86_64
NonfreeKernelMo
ApportVersion: 2.28.1-0ubuntu2
Architecture: amd64
CasperMD5CheckR
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)
RelatedPackageV
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to noble on 2024-04-28 (39 days ago)
tags: | added: nvidia simpledrm |
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.