Bug 100700 - gtk2 applications sometimes stop accepting keyboard input
Summary: gtk2 applications sometimes stop accepting keyboard input
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: gtk2
Version: 9
Hardware: i686
OS: Linux
Target Milestone: ---
Assignee: Owen Taylor
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2003-07-24 14:06 UTC by Wesley Tanaka
Modified: 2007-04-18 16:56 UTC (History)
1 user (show)

Clone Of:
Last Closed: 2004-04-07 01:13:53 UTC

Attachments (Terms of Use)

Description Wesley Tanaka 2003-07-24 14:06:34 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5b) Gecko/20030723

Description of problem:
Sometimes, gtk2 applications (it mostly happens with those using antialiased
fonts) will get into a mode where they will accept mouse input but will not
accept keyboard input.  It seems to happen sporadically when I'm typing in one
window of the application and a new window appears while I'm typing.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Log in in simplified chinese locale
2. run a program that can create multiple windows (e.g. gaim)
3. type into text fields while new windows are being created.

Actual Results:  All windows will get into a state where they do not accept
keyboard input of any kind.  Mouse input still works.

Expected Results:  should continue to work normally.

Additional info:

Comment 1 Owen Taylor 2003-07-24 18:27:25 UTC
Sadly, I don't think we'll be able to do anything unless you can
provide exact details about a set of steps to reproduce the problem,
at the level of "what keys to press", just running logged in in Chinese 
for a couple of hours isn't really an option for me...

Comment 2 Wesley Tanaka 2003-07-24 19:19:06 UTC
The key to reproducing the bug seems to be typing at the same time that the same
application maps another window.

I just reproduced it now (Firebird 0.6) by:

File:New Window

and then, before the window actually mapped, spamming the keyboard with
keystrokes in this text field.  I'm entering the rest of this comment via cut
and paste, since I can't type in firebird anymore.

Comment 3 Leon Ho 2003-08-01 06:16:32 UTC
I couldn't reproduce it in mozilla or gedit. If it is about gtk+2 it should able to 
reproduce on all of the gtk+2 applications? 

Comment 4 Wesley Tanaka 2003-08-04 16:03:53 UTC
I've seen the bug so far in gaim, mozilla and gedit, as well as with SWT
programs like eclipse, mainly because those applications are the ones that I
often type in.  It may not be a GTK2 bug.  Any ideas how to isolate the part of
software further?

Comment 5 Leon Ho 2003-08-12 01:04:52 UTC
Can you reproduce on any locales (including en_US.UTF-8) Or is there a specific 
locale that you are having problem? 

Comment 6 Wesley Tanaka 2003-08-12 04:09:52 UTC
I am using RH9's simplified chinese locale, which is zh_CN.GB18030 

Comment 7 Leon Ho 2003-08-22 04:34:24 UTC
Try it in other locales like en_US.UTF-8 and see if you got the same problem 

Comment 8 Wesley Tanaka 2003-08-22 09:06:35 UTC
I do not get the same problem in en_US.UTF-8

At first I thought I could reproduce it, but focusing on another window and then
back on the window that had the problem seemed to fix it completely.

Comment 9 Owen Taylor 2003-10-15 18:43:01 UTC
Is this the same as bug 106807?

Comment 10 Wesley Tanaka 2003-10-15 19:15:25 UTC
The problem that I've observed applies only to a single process.  if, for
example, eclipse gets stuck, killing and restarting eclipse fixes the problem. 
If gedit gets stuck, killing and restarting gedit fixes the problem.

If it is the case that bug 106807 is a bug in chinput, that suggests these two
bugs may be different.

Comment 11 Leon Ho 2003-12-08 00:20:30 UTC
Sorry I still cannot reproduce it. Can you test on Fedora Core and see
if that still a problem to you?

Comment 12 Wesley Tanaka 2003-12-09 08:35:52 UTC
I've partially upgraded my desktop to Fedora, but haven't used it
extensively enough to know if the problem is still there.

Comment 13 Leon Ho 2004-04-07 01:13:53 UTC
I cannot reproduce in FC2 test2. Let me know if this problem still
occur for you in FC2.

Note You need to log in before you can comment on or make changes to this bug.