Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 427148 - x11-libs/gtk+-2.24.11 makes net-im/pidgin-2.10.[46] refuse keyboard input
Summary: x11-libs/gtk+-2.24.11 makes net-im/pidgin-2.10.[46] refuse keyboard input
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Library (show other bugs)
Hardware: All Linux
: Normal normal
Assignee: Gentoo Linux Gnome Desktop Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-07-18 20:23 UTC by Christian Trefzer
Modified: 2012-07-22 10:06 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
output of $ emerge --info (file_427148.txt,6.05 KB, text/plain)
2012-07-18 20:23 UTC, Christian Trefzer
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Christian Trefzer 2012-07-18 20:23:18 UTC
Created attachment 318574 [details]
output of $ emerge --info

With x11-libs/gtk+-2.24.11 installed, recent versions of net-im/pidgin refuse any keyboard input whatsoever - hotkeys, conversations, send message won't work. Downgrading gtk+ to 2.24.10-r1 solves the problem, whereas installing different versions of pidgin does not.
Comment 1 Rafał Mużyło 2012-07-18 23:48:39 UTC
More details are needed about your desktop env setup needed, cause works just fine here.
Comment 2 Lars Wendler (Polynomial-C) (RETIRED) gentoo-dev 2012-07-19 12:06:03 UTC
Have you tried restarting your X-server after updating gtk+? I was hit by this problem as well but it disappeared after I restarted X.
Comment 3 Christian Trefzer 2012-07-20 00:41:35 UTC
(In reply to comment #2)
> Have you tried restarting your X-server after updating gtk+? I was hit by
> this problem as well but it disappeared after I restarted X.

Yes, I restarted pidgin, later X, then even rebuilt world and did a quick kexec... Within the same X session, toggling the gtk+ version toggles the issue as well.
Comment 4 Christian Trefzer 2012-07-20 00:59:41 UTC
(In reply to comment #1)
> More details are needed about your desktop env setup needed, cause works
> just fine here.

Maybe I messed something up. I'm running ~amd64 and my GUI setup basically consists of X.org-1.12.3 w/ fluxbox-9999 and some more live ebuilds in the area of libdrm, mesa, and a few dependencies. Any change, restart or rebuild did not make a difference, except for the gtk+ downgrade. I specifically checked, updated to 2.24.11 again, restarted and connected pidgin, no keys. Back to 2.24.10-r1, fire up pidgin again, works like a charm.

I am really puzzled, for now I masked the critical version just so I don't inadvertently update to that any time soon. I'm a bit used to development so I might as well build a few packages with debug info and provide core dumps, although I'd rather not make my in-memory IM service credentials publicly available :(

Thanks for the replies so far. If I am the only one seeing this, something may be at odds with my setup. I could not find a report of similar misbehaviour anywhere, and a downgrade avoids the problem, so first of all I wanted to share this info and ideally help sorting out a speed bump.
Comment 5 shinydoofy 2012-07-20 17:55:26 UTC
I'm having similar trouble with gajim. I'm also running ~amd64, but without any meaningful live ebuilds.

After changing my status from available to away, gajim doesn't accept any keyboard input, unminizing the roster from tray doesn't work either.

Downgrading to =x11-libs/gtk+-2.24.10-r1 also fixes this for me.
Comment 6 Rafał Mużyło 2012-07-20 19:07:30 UTC
Comment 5 changes things - I can reproduce that in pidgin (that is after changing status, some widget grabs focus preventing input).

Most likely culprits are http://git.gnome.org/browse/gtk+/commit/?h=gtk-2-24&id=b32a9eb691920f21ad3b9127c833aaba15727c4b and http://git.gnome.org/browse/gtk+/commit/?h=gtk-2-24&id=8da54b81182af2d56230de22c0e00a5aba9ab442.

Anyone up to testing which one was it ?
Comment 7 Christian Trefzer 2012-07-20 19:53:38 UTC
(In reply to comment #6)
> Comment 5 changes things - I can reproduce that in pidgin (that is after
> changing status, some widget grabs focus preventing input).
> 
> Most likely culprits are
> http://git.gnome.org/browse/gtk+/commit/?h=gtk-2-
> 24&id=b32a9eb691920f21ad3b9127c833aaba15727c4b and
> http://git.gnome.org/browse/gtk+/commit/?h=gtk-2-
> 24&id=8da54b81182af2d56230de22c0e00a5aba9ab442.
> 
> Anyone up to testing which one was it ?

I'll inject a patch reverting either of those into the ebuild and test each of them tomorrow during the day. Thanks a lot for the pointers!
Comment 8 Alexandre Rostovtsev (RETIRED) gentoo-dev 2012-07-20 23:00:34 UTC
(In reply to comment #6)

Actually, the culprit appears to be http://git.gnome.org/browse/gtk+/commit/?h=gtk-2-24&id=3f6592f60fd15fb353fc84600caefba3054dc892

I've reported the bug upstream at https://bugzilla.gnome.org/show_bug.cgi?id=680346
Comment 9 Rafał Mużyło 2012-07-20 23:35:32 UTC
(In reply to comment #8)
> (In reply to comment #6)
> 
> Actually, the culprit appears to be
> http://git.gnome.org/browse/gtk+/commit/?h=gtk-2-
> 24&id=3f6592f60fd15fb353fc84600caefba3054dc892
> 
> I've reported the bug upstream at
> https://bugzilla.gnome.org/show_bug.cgi?id=680346

Odd, after I reproduced the bug, I was able to get the keyboard unstuck by opening the menu with mouse.

Though the code before that commit did call _gdk_xgrab_check_unmap...
Comment 10 Alexandre Rostovtsev (RETIRED) gentoo-dev 2012-07-20 23:58:29 UTC
Fixed in gtk+-2.24.11-r1. Thanks for reporting!

>*gtk+-2.24.11-r1 (20 Jul 2012)
>
>  20 Jul 2012; Alexandre Rostovtsev <tetromino@gentoo.org>
>  +gtk+-2.24.11-r1.ebuild, +files/gtk+-2.24.11-stuck-grab.patch:
>  Fix stuck keyboard grab in pidgin and gajim (bug #427148, thanks to Christian
>  Trefzer, Rafał Mużyło, shinydoofy).
Comment 11 Christian Trefzer 2012-07-22 10:06:06 UTC
That did the trick. Thanks a bunch folks!