Community
Participate
Working Groups
System config: OS: Linux RH9 JDK: 1.4.2 Eclipse: Eclipse-GTK 3.0M3 Personal config: - Emacs keybinding (not really, I don't use the default Emacs keybinding shipped with Eclipse, as I found it to have some very annoying behavior. So I basically mapped my keys, similar to the Emacs keybindings to my preferences). Eclipse frequently lost the control over keyboard, and I can't type anymore. Meanwhile, the keyboard is working just fine for any other application, including other Java apps that are running at the same time. And once this happens, there is absolutely nothing I can do, besides shutting Eclipse down, and restart it. And the strangest of all, my Emacs keybinding is still working. That is, if I put the cursor in the editor (the mouse is still working, and Eclipse seems to be just running ok), and I can do Ctrl-N, Ctrl-P, Ctrl-A, Ctrl-E, .... basicallly all my keybindings are still working. Except I can't type the normal keys and input in the editor, or anywhere else. This is happening very frequently. The worst thing is when I type in the input field in a dialog box. On average, if I type 5 times in a dialog box, I can get one screw-up. Today, I had a big refactoring job to do, changing a bunch of package names, and it is worse than normal. I had refactored 6 packages, and had to restart Eclipse 3 times already. So I decided to spend some times filing this bug. And this is happening on all versions since 2.1. I did use 2.0, but I didn't remember to run into this problem, probably I didn't do any key mapping at the time. And this problem only shows up if I use keybinding, even with the default Emacs keybinding. If I don't use any keybinding, I don't get this problem. But, how can one write code when you have to move your hand to the arrow keys just to move the cursor and move your hand back to type? There's no way I can tolerate that, so my Emacs keys is an absolute must-have! This is a very very very very annoying problem!!!!
Actually, the keybinding feature is totally broken on 3.0M3. Horror! I got really weird behavior after I upgraded to M3, some of the keys are not working anymore. Then I went to Preferences -> Workbench -> Keys, and found that it's all changed. Actually when I select Keys option, Eclipse would take 100% of the CPU and stay like that for 1.5 minute. If I select any category, it just grabs the CPU 100% again, for a long long long time, then tells me there's an buffer overflow, and I should shutdown. Worse, of the categories will just grab the CPU forever, and there's no way to stop except kill it with a -9 from a console. Ok, all keybindings are totally screwed now. Worse thing is, I switched back to M2, and they are gone! Now, have to rebind all these again!
Just downloaded SDK N20030908, and it fixed (half!) the problem of setting keybinding options in 3.0M3 described ealier. At least, Eclipse would not take up the CPU, and would actually let me set my own keys. However, the Alt key is not working, that means half of the emacs keys are not usable. In the option dialog, I can press, say, "Alt+w" and it is selected. But when I go to the editor, Alt+w does not work, it just type in 'w' instead. Esc is ok, but that key is way too far, even on a Thinkpad laptop. And if I remap the General keybindings, the keyboard is totally unusable. I can't type anything, can't input anything.
Here's how to reproduce the dead keyboard: - Eclipse SDK N20030908 Linux-GTK (Linux RH9) - Open a Java source file or a text file - Bring up the Find/Replace dialog box - In the Find field, type in something, then press tab to jump to the next field. The cursor actually jumped to the Replace With field, but the keyboard is dead. Nothing you can anymore, except shutting down.
reporter has touched on a number of already logged bugs, of varying severity. 1. the find/replace where emacs keys still work is the keybindings remain active in modeless dialog problem, which should have been the last fix to enter 3.0 M3 (?) 2. CPU at 100% is the stack overflow problem on linux now fixed by swt. 3. doug, is there a problme with Alt+ keys on linux? 4. there might be some custom key bindings 2.1 importing problems which will have to be reviewed for 3.0, but i don't think there is a problem here. 5. as far as keys completely disappearing, i'm not sure we've seen that anywhere else, except for perhaps a few builds before 3.0 M3 i saw this. (there were a number of bugs such as java editor key bindings missing, etc. - these were very short lived problems due to the transition of scopes->editors, and movement of standard key config -> null and global scope -> null) can you annotate duplicates where appropriate and close? thanks..
Eclipse: SDK N20030908 1- The Find/Replace example is just one example I gave on how to see the keyboard problem. Actually, if you press tab on almost any dialog, you get a dead keyboard. This is so serious that I'm rebooting Eclipse every 10 minutes or so, on average now. Just a few other dialogs which would give you dead keyboard: - add a new cvs repository; type in server name, press tab ==> dead! - Preferences -> Ant -> Editor; put your cursor in Print Margin Column, and press tab ==> dead! - menu Search -> References -> select Java Search tab -> type something in search string field, press tab key ==> dead! - .... I can give you a bunch more, but that would take too long to reproduce, as I have gef, emf, and a bunch of other plugins too, so the start up time is long, even on my 1.8GHz TP laptop. 2- CPU at 100% and stack overflow is fixed (I don't see it after trying a couple of nightlies). Sorry, I should have checked first that it's dup of #42664. 3- Alt+ problem appears after M3. Still can't use it. 4- I don't think the problem I see is caused by importing key bindings from 2.1. After I switched to 3.0M1, I actually reset the keys, and spent time rebinding from scratch, and I actually like it better (seems more responsive, just my impression!). So all my key bindings are from 3.0 only, unless the reset button is not working as expected, and there's still 2.1 legacy left behind. 5- Well, I don't know what to say. I switched back to M2, looked in my key preferences, everything is set to default. Curiously, some of the keys are still working. In M3, sometimes it tries to reset some of my keys. I was using the key just fine, and then suddenly, it stops working. I went to look at key bindings, sure enough, it's back to the default. I'll try to come up with some instructions on how to duplicate that. thanks
See Bug 41832 for other problems with focus on GTK. If you can, it would be helpful to provide more examples of lost focus (with the exact steps to reproduce). See Bug 42465 for the StackOverflowError. I don't see the problem you mention in Comment #3 using I20030909 on Linux-GTK, RedHat 9.0. Can you reproduce the problem using a fresh workspace? (cp your workspace to a backup location, don't install any plugins, and open eclipse) What locale are you using? Which JVM? Which window manager? Which linux distribution? However, I do see another problem, which is now described in Bug 42873. I do not see your 'Alt+' problem, though it might be that the KeysPreferencePage is a bit unintuitive at first pass. To bind 'Alt+W' to a new key, do the following: 1.) Select the category. 2.) Select the command. 3.) Type the key sequence into the key sequence text widget. 4.) Click on Add. 5.) Click Apply/Ok. Your bug does not result in crashes, data loss or a severe memory leak. Since no developers or testers have noticed the problem either, I'm moving your bug to "major". (in the future, please file separate bugs for separate problems. it's much easier to keep track of. thanks.)
(waiting for response -- moving to P4)
Ok, some more system config details: OS: Linux RH 9 (downloaded ISO from redhat.com, signature verified) JDK: 1.4.2 (downloaded from java.sun.com) Eclipse: Eclipse-GTK N20030908 Window Manager: Gnome + Metacity Locale: zh_CN.GB18030 X input method: chinput (but this is not used when I'm working in Eclipse, only activate the chinput client when I write documents or emails) Computer: Thinkpad T30 (no other addon, besides extra RAM) Memory: 512MB Problem: Alt+ key combo is totally unusable in my environment. It was working ok up until M3 (M2 is fine). Yes, I know how to bind the Alt+W key. I bind it for "In General", for "Editing Java Source", and for "Editing Text". That's the key binding I'm using on a daily basis, plus other usual Emacs key. I don't really care that my specific key bindings being lost. It's annoying, but I know this is beta, and I can always rebind them. But the keyboard losing focus has no workaround. As soon as I touch the tab key in a dialog, it's dead. There's absolutely nothing I can do about it. I don't think I need to give more examples besides the ones in #1. Basically, everytime I touch tab key in a dialog, it's dead. Sometimes, the keyboard is gone too, even without typing the tab key. I just have to type at my normal speed (which I think is average fast, not really super fast), and the keyboard is dead too. This problem existed before, but it's very hard to reproduce. It just happens at random, I didn't file any bug as I can't reproduce it everytime. After M3, if I want to work in Eclipse, I have to wait half a second in between every character input. And have to be really careful not to touch the tab key (which is almost impossible as a very old habit), and have to be really careful to use the mouse to position the cursor in the field I want to input in. Oh yeah, even if the keyboard lost focus, I still can use the mouse to position the cursor anywhere, I still can open/close dialogs, etc. Just can't type. Sorry for lumping all these problems together. I just wanted to file the keyboard problem, but ended adding other stuffs in here. And yes, I should have reported the locale earlier. It looks like that's the issue here. Ok, looks like I need to switch to C locale to work with Eclipse again.
Okay, there are two problems then: 1.) Alt keys aren't working 2.) Focus disappears on tab or randomly during use I cannot reproduce (either problem) using the following set-up: + Eclipse-GTK integration build I20030910 + RedHat 9.0 + Sun JDK 1.4.2 (build 1.4.2-b28) + GNOME desktop environment, with Metacity as the window manager + Locale "en_US.UTF-8" ("English (American)") + IBM NetVista with 512MB I will try to reproduce using "zh_CN.GB18030". Could you please try to reproduce using "en_US.UTF-8"? Thanks. (downgrading to normal -- only affects "zh_CN.GB18030" locale.)
Yep, local en_US.UTF-8 is working fine. This is actually the locale I'm working in right now. The problem is in locale zh_CN.GB18030.
Switching locale to "zh_CN.GB18030" causes keyboard craziness to ensue. I see what you mean about unusable now; it sounded a bit like an exaggeration at first. Sorry.
Opening any dialog and pressing a key within the dialog freezes the keyboard input and blocks keyboard accelerators from working. Mouse continues to function, and Eclipse is still responsive. Keyboard continues to work in other applications even while keyboard input is frozen in Eclipse. Dialogs can be opened and navigated with a mouse (and closed with a mouse), and keyboard input continues to work. No freezes noticed yet from input into non-dialog windows.
I'm going to split this into two separate bugs.
Doug, can this report be closed? I recently assigned two bugs to Felipe, which I think are from this report, just split into two.
This bug report is quite long and mentions a bunch of different problems. Ideally, I think 43009 and 43011 to be fixed, and then for all the symptoms mentioned here to be double-checked. You can either move this bug to Felipe as well, or punt it back to me.
Felipe, note the two dependencies that this bug has. Once they're taken care of this bug may also be fixed (go through and verify).
No reason to keep this bug open since we have a specific problem report bug each bug. *** This bug has been marked as a duplicate of 43009 ***
