F20 gnome inactivity causes mouse/kbd unresponsiveness, must restart gnome-shell

[Pekka Savola]

Hello,

I've two systems running F20 + updates-testing, a T400 laptop and a 
desktop PC. PC was upgraded with yum from F18, laptop was a fresh 
install. Both experience the same problems, at least for roughly two 
weeks now, maybe longer (not sure when this started, maybe even from 
the install in Dec/Jan). The problems are much more severe on the 
laptop, though (laptop is on docking station and on power all the 
time).

After inactivity timeout, you need to swipe the screen or use keyboard 
to reactivate it (I've disabled screen locking). The problem that 
often occurs is that mouse movement works, but clicking doesn't do 
anything. Similarly keyboard is unresponsibe. The clock has been 
frozen to the inactivity time.

The workaround is to use CTRL-ALT-F2, log on there and do 'killall 
-HUP gnome-shell'. Then you can resume the session (after entering the 
password etc.). Sometimes restarting doesn't work.

I've been unable to find similar reports on F20 but maybe I don't know 
what to look for. On F18 I found something remotely familiar (but this 
occurs pre-locking and there are no errors): 
https://bugzilla.redhat.com/show_bug.cgi?id=872118

I see no strange messages in messages, Xorg.0.log or gdm logs.
Any ideas? Where to start digging?

-- 
Pekka Savola                 "You each name yourselves king, yet the
Netcore Oy                    kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings