Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 328547 - [typing] Keyboard becomes unresponsive frequently in edit area
Summary: [typing] Keyboard becomes unresponsive frequently in edit area
Status: CLOSED NOT_ECLIPSE
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Text (show other bugs)
Version: 3.6.1   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-Text-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: needinfo
Depends on:
Blocks:
 
Reported: 2010-10-24 10:16 EDT by Nevo CLA
Modified: 2010-10-30 10:03 EDT (History)
4 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Nevo CLA 2010-10-24 10:16:02 EDT
Build Identifier: M20100909-0800

Trying to edit java code in edit area, when mouse cursor moves over a class name or other symbols to show up the inline annotations or java doc box or bring up autocompletion box, after that, the keyboard will become unresponsive almost all the time, except for those keys like ctrl,alt,caps. Switch app windows/tabs can reactivate keyboard input.

Linux:Debian Squeeze
GTK: 2.20.1
JRE: 1.6.0_20

Note that, in Ubuntu 10.04 I found the same problem ,with the same version of eclipse and JRE.

Reproducible: Always

Steps to Reproduce:
1. Move cursor to a java class name or other symbol names in edit area to show up annotation box or javadoc box, or bring up autocompletion box
2. click elsewhere in edit area to dismiss those boxes.
3. Keyboard will become unresponsive
Comment 1 Remy Suen CLA 2010-10-24 15:16:51 EDT
(In reply to comment #0)
> 2. click elsewhere in edit area to dismiss those boxes.

What if you click somewhere else that's not back in the editor?
Comment 2 Nevo CLA 2010-10-24 20:45:58 EDT
(In reply to comment #1)
> (In reply to comment #0)
> > 2. click elsewhere in edit area to dismiss those boxes.
> 
> What if you click somewhere else that's not back in the editor?

Sorry to forget to mention that click somewhere that's not in the editor doesn't cause keyboard to become unresponsive. And it's been a long time since I used eclipse first time, so I don't know how to collect the relative logs. If you need it, please tell me which files you want to attach here. Thanks.
Comment 3 Dani Megert CLA 2010-10-25 03:17:24 EDT
(In reply to comment #2)
> (In reply to comment #1)
> > (In reply to comment #0)
> > > 2. click elsewhere in edit area to dismiss those boxes.
> > 
> > What if you click somewhere else that's not back in the editor?
> 
> Sorry to forget to mention that click somewhere that's not in the editor
> doesn't cause keyboard to become unresponsive.
But the keyboard is only not responsive in the editor area? Is it still working in other parts of the workbench? If not, is it working outside? How do you get out of this state? Close the editor?

Please attach the .log and make some stack traces. For details see http://www.eclipse.org/eclipse/platform-text/development/bug-incomplete.htm.
Comment 4 Nevo CLA 2010-10-25 09:56:26 EDT
(In reply to comment #3)
> (In reply to comment #2)
> > (In reply to comment #1)
> > > (In reply to comment #0)
> > > > 2. click elsewhere in edit area to dismiss those boxes.
> > > 
> > > What if you click somewhere else that's not back in the editor?
> > 
> > Sorry to forget to mention that click somewhere that's not in the editor
> > doesn't cause keyboard to become unresponsive.
> But the keyboard is only not responsive in the editor area? Is it still working
> in other parts of the workbench? If not, is it working outside? How do you get
> out of this state? Close the editor?
> 
> Please attach the .log and make some stack traces. For details see
> http://www.eclipse.org/eclipse/platform-text/development/bug-incomplete.htm.

Okay....Today, when I quit eclipse and tried to bring up eclipse from the gnome-terminal directly, I found keyboard input became unresponsive as well. Mouse is working, and alt-tap to switch windows makes keyboard back to normal. I guess this isn't Eclipse bug alone, I'm suspecting gtk (it's weird I've never encountered with this problem with other apps, only eclipse, and now, gnome-terminal... I'll close this bug? 
'
Comment 5 Dani Megert CLA 2010-10-25 10:31:53 EDT
>I'll close this bug? 
Yep, let's close it for now. Please reopen if you think it's Eclipse and you have more data.
Comment 6 Nevo CLA 2010-10-25 10:44:36 EDT
(In reply to comment #5)
> >I'll close this bug? 
> Yep, let's close it for now. Please reopen if you think it's Eclipse and you
> have more data.

okay, thanks!
Comment 7 Nevo CLA 2010-10-25 10:45:22 EDT
Close it  as I found it in another app.
Comment 8 Markus Keller CLA 2010-10-25 13:19:13 EDT
Maybe you accidentally enabled X-mouse behavior (focus follows mouse).
Comment 9 Nevo CLA 2010-10-26 10:33:32 EDT
(In reply to comment #8)
> Maybe you accidentally enabled X-mouse behavior (focus follows mouse).
No, I don't enable that. I currently have no idea except trying to build gtk from latest source. Thank you anyway.
Comment 10 Nevo CLA 2010-10-30 10:03:08 EDT
Well, I finally managed to fix this problem.  The cause of it is scim, for which I use xim protocol as the front-end. After setting the default input method (~/.xinput.d/en_US) to scim-bridge or just scim, this problem disappeared. I'm hoping this could provide some help to other people who have similar problems. Thanks!