Bug 2192697

Summary: gnome-shell crashes after suspend/resume
Product: [Fedora] Fedora Reporter: Thomas M Steenholdt <thms>
Component: gnome-shellAssignee: GNOME SIG Unassigned <gnome-sig>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 38CC: adscvr, fmuellner, gnome-sig, jadahl, otaylor, philip.wyett
Target Milestone: ---Keywords: AutomationTriaged
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2024-05-21 14:53:07 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
FULL journald dump for the period from resume and until i resume control by restarting gdm none

Description Thomas M Steenholdt 2023-05-02 18:28:58 UTC 
Created attachment 1961790 [details]
FULL journald dump for the period from resume and until i resume control by restarting gdm

Description of problem:

I move my ThinkPad P14s between work and home, every day, always working on an external monitor, connected via USB-C, which also powers my laptop.

I suspend by disconnecting the USB-C cable.

I then resume by plugging the USB-C cable back in and jiggling the mouse.

More often than now - but crucially not always - the system is weird after resume:

* Some times the luck screen appears wierd, as if the mouse is scrolling the controls, even though it isn't. Keyboard controls work.

* Some times I can log in, but the mouse cannot control the windows. I canm see the mouse cursor moving, but the windows dont react to clocks or anything. The cursor may even go behind the windows. Keyboard controls work.

* Some times the system refuses to wake up properly, but get stuck in a suspend/resume cycle (i'm thinking this has to do with power delivered over USB-C and the lid being closed, combined with these problems)

Version-Release number of selected component (if applicable):

Fedora 38 (but this is on at least Fedora 37 as well and the last few releases of Ubuntu as well)

gnome-shell-44.1-1.fc38.x86_64

How reproducible:

Happens enough to be VERY annoying, but not enough that I have found a way to reproduce at will.

Steps to Reproduce:
1. Work in gnome-shell
2. Suspend
3. Resume

Actual results:

The system does not respond normally top mouse inputs. Restart the entire gnome stack at a minimum is required (but rebooting is easier).

Expected results:

The system behaves normally so I can continue to work.

Additional info:

Problem has existed on several versions of T14(s) thinkpads as well over the past few releases

All impacted laptops - I BELIEVE - have been AMD versions.

I realize the the different behaviors may be different bugs, but it's hard for me to know one from the other. So since it may also be different manifestations of the same bug, I decided to give you as much info as possible.

Also - I believe this bug #2149570 is related, but AFAIKT, gdm is not the culprit.
Comment 1 Thomas M Steenholdt 2023-05-08 20:56:33 UTC 
FWIW, I've been on the road for a couple of days and have not experienced this issue once. Looks like the external monitor is absolutely a factor on my system.
Comment 2 Thomas M Steenholdt 2023-07-16 22:45:35 UTC 
I had this issue forever, but with the latest amd-gpu-firmware (20230625-151.fc38) it appears to have gotten much worst. Always in some type of relation to powersavings, even just powered off screen. I have reverted to previous amd-gpu-firmware (20230310-148.fc38) which have reduced the frequency of this happening. On the newest one, this happend almost every time i returned to the computer from a break.
Comment 3 Fedora Admin user for bugzilla script actions 2023-12-06 08:23:08 UTC 
This component is maintained by the GNOME project. Issues with it should be reported directly to GNOME at https://gitlab.gnome.org/GNOME/.

This issue should only be kept open if it:

1. Relates to Fedora packaging or integration with other Fedora components
2. Is required for Fedora release processes, such as blocker bugs and freeze exceptions

If this issue isn't needed for either of these two reasons, please:

 * create an issue with GNOME
 * add a link to the GNOME issue here
 * close this issue as CLOSED/UPSTREAM

Thank you!
Comment 4 Aoife Moloney 2024-05-21 14:53:07 UTC 
Fedora Linux 38 entered end-of-life (EOL) status on 2024-05-21.

Fedora Linux 38 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.