Red Hat Bugzilla – Bug 845953
in some applications, text fields don't accept keyboard input.
Last modified: 2012-10-11 21:31:02 EDT
Description of problem:
I don't know what component to file this against - it's about input methods.
In some apps, keyboard input in text fields doesn't work - the cursor is visible, but no keystrokes are accepted. I observe this mainly with pidgin (both the window for status messages and conversation windows) and the network manager applet in KDE when it asks for the secret of a wireless connection.
This behaviour is not window manager dependant (reproduced under kde, xfce, gnome) and not user dependant (tried with freshly created user)
workaround is the context menu that's bount to right mouse button where input methods can be selected. This is set to System(Simple) by default. Set it to anything else (Simple will do) and keyboard input works again. Set it back to System(Simple) and it will continue to work.
I don't know yet whether it is permanently fixed by this or whether it will have to be set again in a new x session.
Version-Release number of selected component (if applicable):
with fresh user, every time
Steps to Reproduce:
1. open pidgin, set status
2. get status window, try to write anything in there.
keyboard input doen't appear in text field
the opposite :)
set input method for this to anything. Write, it now works normally
Setup component is definitely wrong one - for the multicomponent issues it is the best way to file this as tracker against distribution and single bugzilla per affected component. As I'm not sure if this is really the purpose of the bugzilla, only reassigning to distribution component.
Okay, sorry, didn't know I could file against distribution.
FWIW, I don't think it's really a multicomponent issue. It's just the overall input method handling. If I had to guess, I'd say it's probably just some default setting that doesn't exist in some/most configs and isn't caught by the overall framework...once you set it to anything, it works.
Not sure how and where to debug this, though...never played around with input methods before.
I don't understand your problem.
Would you attached the screenshot?
% gnome-screenshot -i
I am observing the exact same issue. Only noticed this in Pidgin though. Will try the workaround with the input method selection next time.
setup: F17 x86_64, lxde, pidgin 2.10.6-3.fc17 (recompiled from rawhide to see if this fixes the issue). I have no ibus packages installed.
Upstream bug report:
(In reply to comment #4)
> I am observing the exact same issue. Only noticed this in Pidgin though.
> Will try the workaround with the input method selection next time.
> setup: F17 x86_64, lxde, pidgin 2.10.6-3.fc17 (recompiled from rawhide to
> see if this fixes the issue). I have no ibus packages installed.
I don't see any problems in pidgin.
If you could see your problem without ibus, the problem is not in ibus.
I have filed a bug againts gtk2 (https://bugzilla.gnome.org/show_bug.cgi?id=682563). Downgrading to 2.24.10 solves the issue.
I believe this is a duplicate of bug 843296.
Upgrading to gtk-2.24.12 definitely solved the issue for me!
(In reply to comment #8)
> I believe this is a duplicate of bug 843296.
*** This bug has been marked as a duplicate of bug 843296 ***