Bug 331017

Summary:	keyboard and mouse inputs ignored until mouse crosses window boundary
Product:	[I don't know] kde	Reporter:	pf
Component:	general	Assignee:	Unassigned bugs mailing-list <unassigned-bugs>
Status:	RESOLVED WORKSFORME
Severity:	normal
Priority:	NOR
Version:	4.11.4
Target Milestone:	---
Platform:	Mageia RPMs
OS:	Linux
Latest Commit:		Version Fixed In:

Description pf 2014-02-11 19:56:22 UTC

Randomly, an application window (ie, just one firefox window is affected, all other OK) appears non-responsive. Clicking on checkboxes, typing text into a textarea, scrolling (scroll bar or mouse wheel), click&drag, loading new pages, refreshing pages, etc will not respond unless the mouse is moved across the windows boundaries. Loading a new page which takes a while usually requires moving the mouse in and out of the window over and over until all the data is displayed.  

More info at https://bugs.mageia.org/show_bug.cgi?id=12101

Reproducible: Sometimes

Steps to Reproduce:
1.  No idea what triggers it.
2.  Close/re-open the window (not the full application if it handles several windows -- such as firefox) to restore full functionality.
3.



This has been happening randomly for months.  Am now on Mageia4 and latest firefox Nightly 30.0a1 displayed this problem today on only one of 9 windows.

Comment 1 pf 2014-02-11 20:33:54 UTC

This problem just occurred on gkrellm...  moving the mouse in/out of the gkrellm window causes single updates -- otherwise, gkrellm just sits there without updating.  

Now it gets weird...  never noticed this before...  I was reading an email (via firefox) which contained an attachment.  Opened the attachment with okular whose window was nowhere near the gkrellm window.  Opened the print dialog on okular and gkrellm got one update.  Closed the print dialog and gkrellm got another update.  Mouse and okular window never came near gkrellm window.  Closed and restarted gkrellm and it's working correctly again...

Comment 2 Christoph Feck 2014-02-11 20:54:17 UTC

Firefox and gkrellm are GTK+ applications, no KDE or Qt applications, so I doubt KDE developers will be able to find the cause for the issue you see.

Comment 3 pf 2014-02-12 17:36:14 UTC

Thanks. Reported at https://bugzilla.gnome.org/show_bug.cgi?id=724200

Comment 4 pf 2016-04-30 16:46:44 UTC

Haven't seen this problem in a while now.

Comment 5 Christoph Feck 2016-05-05 01:19:03 UTC

Thanks for the update. I suggest to also close the bug from comment #3.