Bug 1296477

Summary: After unlocking screen applications do not respond to input
Product: [Fedora] Fedora Reporter: Petri Pennanen <p.pennanen>
Component: gnome-sessionAssignee: Ray Strode [halfline] <rstrode>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 23CC: jmccann, rstrode
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-01-08 08:00: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:
Attachments:
Description Flags
Output from journalctl -p err -b -1
none
lspci output
none
dmidecode output none

Description Petri Pennanen 2016-01-07 10:44:10 UTC
Created attachment 1112405 [details]
Output from journalctl -p err -b -1

Description of problem:
After unlocking the screen all applications other than Gnome Shell stop responding to input. Selecting and clicking widgets does not work. Typing in applications does not work. Gnome Shell still responds to mouse input, but does not appear to respond to keyboard input. Even if a new application is launched, it does not respond to input. 

Version-Release number of selected component (if applicable):
Name        : gnome-session
Arch        : x86_64
Epoch       : 0
Version     : 3.18.1.2
Release     : 2.fc23

Name        : gnome-shell
Arch        : x86_64
Epoch       : 0
Version     : 3.18.3
Release     : 1.fc23

Name        : xorg-x11-server-Xorg
Arch        : x86_64
Epoch       : 0
Version     : 1.18.0
Release     : 2.fc23


How reproducible:
Happens roughly every fifth time the screen is unlocked.

Steps to Reproduce:
1. Lock the screen
2. Unlock the screen 
3. Try to type in an application, or select something with the mouse pointer

Actual results:
The application window does not change or respond to input.

Expected results:
Normal response from application.

Additional info:
The system is a Lenovo L540 laptop, with a secondary screen attached.

See attached log lines regarding gnome-session-binary (the timing matches the input freeze).

Comment 1 Petri Pennanen 2016-01-07 10:44:52 UTC
Created attachment 1112407 [details]
lspci output

Comment 2 Petri Pennanen 2016-01-07 10:45:20 UTC
Created attachment 1112408 [details]
dmidecode output

Comment 3 Petri Pennanen 2016-01-08 08:00:06 UTC
It looks like the behaviour was triggered by the gnome-pomodoro extension. The same issue has been reported in the gnome-pomodoro issue tracker and the GNOME bugzilla: 

https://github.com/codito/gnome-pomodoro/issues/190
https://bugzilla.gnome.org/show_bug.cgi?id=754102

I am closing this, since it is known upstream.