After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 682563 - Keyboard becomes non-responsive
Keyboard becomes non-responsive
Status: RESOLVED FIXED
Product: gtk+
Classification: Platform
Component: Widget: Other
2.24.x
Other Linux
: Normal normal
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2012-08-23 18:08 UTC by freddy
Modified: 2016-03-06 02:53 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description freddy 2012-08-23 18:08:22 UTC 
In several applications the keyboard becomes non-responsive. I see this myself in Pidgin (Fedora17) upon changing the status when using gtk2-2.24.11(-1.fc17.x86_64). When downgrading to gtk2-2.24.10(-1.fc17.x86_64) things work as expected.

Similar bugs have been filed on redhat bugzilla (https://bugzilla.redhat.com/show_bug.cgi?id=845953) where NetworkManager is mentioned as well and on pidgin's bugtracker (http://developer.pidgin.im/ticket/15220) where claws-mail on Mageia is mentioned as well.

A workaround for pidgin (as mentioned on the bugtracker) is to switch the input method.
Comment 1 Matthias Clasen 2012-08-25 01:47:14 UTC 
I don't think this is caused by a change in 2.24.11. I could reproduce such a symptom with pidgin for a bit. I could also produce it with 2.24.10. But when I bisected all the way from 2.24.9 to 2.24.11, it did not reoccur, and right now, I can't produce it with 2.24.11. So whatever this is, it is unreliable.

I can confirm that swiching input methods did fix the symptom when I was seeing it.
Comment 2 freddy 2012-08-31 12:10:29 UTC 
Matthias,

I can not reproduce this bug using gtk2-2.24.10-1.fc17.x86_64. As soon as I update to gtk2-2.24.11-1.fc17.x86_64 the problem is back. So how did you manage to reproduce with 2.24.10?

If you can give me a short overview of how to do the bisecting (or point to some documentation), then perhaps I can try to narrow it down.
Comment 3 freddy 2012-09-05 18:48:01 UTC 
I updated to gtk2-2.24.12 (saw that an updates tar.xz file existed on ftp.gnome.org) and with that version I can no longer reproduce the issue. So I have goods hopes this error will be resolved in the nearby future.