Bug 1823445

Summary: gnome-shell killed after screen lock
Product: [Fedora] Fedora Reporter: Dennis Wagelaar <dwagelaar>
Component: gnome-sessionAssignee: Ray Strode [halfline] <rstrode>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 30CC: awilliam, caillon+fedoraproject, gnome-sig, john.j5live, mclasen, rhughes, rstrode, sandmann
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-04-22 22:55:54 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
/var/log/messages none

Description Dennis Wagelaar 2020-04-13 17:44:15 UTC 
Created attachment 1678498 [details]
/var/log/messages

Description of problem:
A short while (< 1 minute) after locking the screen, the gnome session is terminated, and you're presented with the standard login screen instead of the unlock screen.

Version-Release number of selected component (if applicable):
gnome-session-3.32.0-1.fc30.x86_64

How reproducible:
The bug does not always occur, but it does occur very often. The steps listed below aren't always necessary to trigger it, but it makes triggering the bug more frequent.

Steps to Reproduce:
1. Start firefox
2. Start a youtube video
3. Lock the screen

Actual results:
Screen is locked initially, screen dims to black (DPMS fails to power down screen, but ok...). After 30-60 seconds, the screen lights back up, this time with the standard login screen instead of the unlock screen.

Expected results:
Screen remains locked, dimmed to black, until user input is provided.

Additional info:
https://retrace.fedoraproject.org/faf/reports/2712266/

/var/log/messages attached, latest bug occurrence at 19:20 on April 13th, 2020.

Problematic portion seems to be:
Apr 13 19:20:11 styx journal[16047]: Object St.Bin (0x5573015528b0), has been already deallocated — impossible to set any property on it. This might be caused by the object having been destroyed from C code usin
g something such as destroy(), dispose(), or remove() vfuncs.
Apr 13 19:20:11 styx org.gnome.Shell.desktop[16047]: == Stack trace for context 0x5572fcffa280 ==
Apr 13 19:20:11 styx org.gnome.Shell.desktop[16047]: #0   557300b4e020 i   resource:///org/gnome/shell/ui/userWidget.js:48 (7efc9d747af0 @ 151)
Apr 13 19:20:11 styx org.gnome.Shell.desktop[16047]: #1   7fff9aa46900 b   self-hosted:979 (7efc9d7515e0 @ 440)
Apr 13 19:20:11 styx org.gnome.Shell.desktop[16047]: == Stack trace for context 0x5572fcffa280 ==
Apr 13 19:20:11 styx org.gnome.Shell.desktop[16047]: #0   557300b4e020 i   resource:///org/gnome/shell/ui/userWidget.js:51 (7efc9d747af0 @ 200)
Apr 13 19:20:11 styx org.gnome.Shell.desktop[16047]: #1   7fff9aa46900 b   self-hosted:979 (7efc9d7515e0 @ 440)
Apr 13 19:20:11 styx org.gnome.Shell.desktop[16047]: == Stack trace for context 0x5572fcffa280 ==
Apr 13 19:20:11 styx org.gnome.Shell.desktop[16047]: #0   557300b4e020 i   resource:///org/gnome/shell/ui/userWidget.js:48 (7efc9d747af0 @ 151)
Apr 13 19:20:11 styx org.gnome.Shell.desktop[16047]: #1   7fff9aa46900 b   self-hosted:979 (7efc9d7515e0 @ 440)
Apr 13 19:20:11 styx org.gnome.Shell.desktop[16047]: == Stack trace for context 0x5572fcffa280 ==
Apr 13 19:20:11 styx org.gnome.Shell.desktop[16047]: #0   557300b4e020 i   resource:///org/gnome/shell/ui/userWidget.js:51 (7efc9d747af0 @ 200)
Apr 13 19:20:11 styx org.gnome.Shell.desktop[16047]: #1   7fff9aa46900 b   self-hosted:979 (7efc9d7515e0 @ 440)

I was instructed to files this bug at https://bugzilla.redhat.com/show_bug.cgi?id=1526164#c42
Comment 1 Adam Williamson 2020-04-13 17:56:21 UTC 
ah, that's an interesting one...we actually had that on F31 and fixed it:

https://bugzilla.redhat.com/show_bug.cgi?id=1761327
https://gitlab.gnome.org/GNOME/gnome-shell/issues/1704

but I'm not sure if it's the same problem in F30. I'll ask Florian.
Comment 2 Adam Williamson 2020-04-13 18:17:10 UTC 
well, actually, on a closer look this might be a bit different and more serious than that one. I think this is actually:

https://gitlab.gnome.org/GNOME/gnome-shell/issues/1295

This was marked as the fix for that:

https://gitlab.gnome.org/GNOME/gnome-shell/-/commit/2fd120162fe49bc85d7773435ac1412c512c5af4

I'll have to look into whether it reached a 3.32 stable release...
Comment 3 Adam Williamson 2020-04-13 18:25:20 UTC 
Looks like this was merged two commits after 3.32.2 was tagged, and there's never been a 3.32.3. I guess I can backport it and do a new build for F30.
Comment 4 Fedora Update System 2020-04-13 18:44:31 UTC 
FEDORA-2020-8824216b0e has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2020-8824216b0e
Comment 5 Dennis Wagelaar 2020-04-15 20:22:37 UTC 
(In reply to Fedora Update System from comment #4)
> FEDORA-2020-8824216b0e has been submitted as an update to Fedora 30.
> https://bodhi.fedoraproject.org/updates/FEDORA-2020-8824216b0e

I've installed gnome-shell-3.32.2-3.fc30.x86_64, and this bug hasn't occurred again so far!
Comment 6 Fedora Update System 2020-04-15 21:40:02 UTC 
FEDORA-2020-8824216b0e has been pushed to the Fedora 30 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-8824216b0e`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-8824216b0e

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 7 Fedora Update System 2020-04-22 22:55:54 UTC 
FEDORA-2020-8824216b0e has been pushed to the Fedora 30 stable repository.
If problem still persists, please make note of it in this bug report.