Red Hat Bugzilla – Bug 845721
Cannot enter a message in the message bar after startup
Last modified: 2012-08-06 01:18:47 EDT
Description of problem:
Since some time I cannot start entering a message in the pidgin message bar directly after start-up.
Version-Release number of selected component (if applicable):
Pidgin 2.10.5-1.fc17 (libpurple 2.10.5)
Running in KDE 4.8.4
I start pidgin manually into offline mode. Switch to 'online', wait for the servers to get registered, and open a number of IRC chats.
In the past, I could then start typing messages, and press 'enter' to post them. Currently, I can select the window (mouse follows focus), place the cursor in the message bar, but key-strokes are not echo-ed in the bar.
The application seems to work otherwise, messages from people get copied into the chat display, and they 'see' me getting online.
I have tried to determine the cause, but mostly failed. It does not seem time related. When I open the windows, and leave them alone for a while, the problem does not fix itself. Switching desktops, focus switching (by moving the mouse around) doesn't help either. It is also not busy, running 'top' doesn't give huge CPU use. The disk also doesn't seem to be used.
A thing that does work is to open a menu of the application. After clicking outside the menu, or pressing escape, the program responds as it should; key-strokes are copied in the message bar, and I can post the messages.
Same here, running F17 with gnome-shell. The input field gets unresponsive (but the cursor keeps blinking) after changing the status in pidgin.
sudo yum downgrade gtk2 gtk2-devel gtk2-devel-docs gtk2-immodule-xim
fixed it, so I suspect it's an issue that came with the last gtk2 update.
This issue was fixed in gtk2 recently, but no new version has been released yet.
Could you mark this bug as a duplicate of the https://bugzilla.redhat.com/show_bug.cgi?id=843296 please?
*** This bug has been marked as a duplicate of bug 843296 ***