Bug 1804709

Summary: Unable to lock the screen
Product: [Fedora] Fedora Reporter: Soham Gumaste <sohamg2>
Component: gnome-shellAssignee: Florian Müllner <fmuellner>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 31CC: fmuellner, gnome-sig, jadahl, kparal, otaylor, philip.wyett
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-02-19 14:21:06 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
journalctl logs of gnome-shell crashing when lockscreen triggered none

Description Soham Gumaste 2020-02-19 13:47:06 UTC
Created attachment 1664045 [details]
journalctl logs of gnome-shell crashing when lockscreen triggered

Description of problem:


Version-Release number of selected component (if applicable):
gnome-shell version 3.34.4

How reproducible:
Easily reproducible

Steps to Reproduce:
1. Attempt to lock the screen with the keyboard shortcut, panel button, or timeout
2. The panel flashes, disappears, and returns to normal (no lock screen; assuming this is a gnome-shell crash)
3. Done

Actual results:
gnome-shell crashes

Expected results:
The screen should lock

Additional info:
Hardware: Dell 7591 laptop with i5 9300H/GTX 1050 on X11. Nvidia driver installed (using DRI to run games as nvidia)
Attached log file from journalctl
(This would trigger ARBT in the past but since I started the report process it has suddenly stopped triggering)

Comment 1 Kamil Páral 2020-02-19 14:09:46 UTC
Hi Soham,
I'm not able to debug this, but I can give you some hints. First try whether the issue occurs with a freshly created user account. If it doesn't, try to disable all gnome-shell extensions in your current profile, reboot, and test it again.

Comment 2 Soham Gumaste 2020-02-19 14:12:14 UTC
Hey Kami,
Thanks for the quick response. I'll try that and get back to you.

Comment 3 Soham Gumaste 2020-02-19 14:21:06 UTC
Hey, that fixed it. I have found the extension that was causing the issue too. Thanks a lot. I'll close this report.

Comment 4 Kamil Páral 2020-02-19 14:23:41 UTC
It's helpful to say which one caused it. Also please report the problem to the extension author. Thanks.