RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Created attachment 1529134 [details]
gnome-shell backtrace

Description of problem:
After resume (mostly the second time) I end up with blank screen and cannot switch to VT. Remote login to the machine shows gnome-shell process (user session and gdm session) are eating 100% CPU. 

From the backtrace it looks like deadlock.  

Both gdm and user sessions are Wayland. The attached backtrace is from machine with NVidia GPU using the binary driver but I was able to reproduce this also on my laptop with intel gpu.

It's a regression as this didn't happened before in rhel8 I suspect it happened after mutter-3.28.3-11.el8, but I have to retest to be sure.


Version-Release number of selected component (if applicable):
gnome-shell-3.28.3-9.el8
mutter-3.28.3-16.el8

How reproducible:
100%

Steps to Reproduce:
1. Login to gnome session
2. Suspend/Resume
3. Suspend/Resume

Actual results:
deadlock

Expected results:
The resume is successful 

Additional info:

Created attachment 1529136 [details]
journal

Ray pushed a potential fix to https://bugzilla.redhat.com/show_bug.cgi?id=1663440 that should solve this. If it does, we can close this as a duplicate.

*** This bug has been marked as a duplicate of bug 1663440 ***