Community
Participate
Working Groups
I20110512-2000 This started to happen when I upgraded to 11.04 (happened both on 3.6.x and 3.7). I can't reproduce it at will but it happens a few times a day. 1. Switch to the Eclipse window from another workspace. When switching to the Eclipse window, and select an editor, the tab is not darked with blue as is normal, but remains light (and I think the titles on all of the editor tabs are lighter than normal). I also cannot type text into the editor window. 2. If I go back to another workspace (with a Chrome browser for example) and then come back to the Eclipse workspace it fixes itself. Sometimes it takes 2-3 tries to fix it. I don't have a screenshot, but I will get one next time it happens.
More information: 1) I just hit it again, but the act of taking the screenshot fixed the problem, so the screenshot is not interesting (it just shows a normal looking window) 2) When I was in the problem, I could switch to any editor/view I wanted with the mouse. But the active view's tab would not have the normal blue background, instead it would just have the same background as the other tabs, and I think the text in the tab was greyed out. 3) When in an editor, none of the keyboard keys would work, however, I could click around the the editor's cursor mark would respond to the mouse. 4) When I clicked into the Project Explorer, the arrow keys worked correctly.
I can force the issue reliably and it's very annoying. I use several workspaces. Eclipse is started in workspace 5. When I switch from another workspace to workspace 5 and Eclipse becomes the active window, any opened editors are locked. I have to switch to another application in the same workspace and back to Eclipse to unlock them. The relevant unity launchpad entry seems to be https://bugs.launchpad.net/ubuntu/+source/eclipse/+bug/781618
Arun, please investigate.
I have tried to reproduce this issue on my Ubuntu 11.04 setup but I haven't been able to. Have you faced the problem with the latest Eclipse 3.7 release (I20110613-1736)? Do you switch workspaces using keyboard shortcuts or through the workspace switcher in unity launcher or via some other method? This could be a unity bug but I cannot investigate further without being able to reproduce the problem.
This could be related to this Unity bug which messes up window focus when an application has multiple windows open - https://bugs.launchpad.net/ubuntu/+source/unity/+bug/802527
(In reply to comment #4) > I have tried to reproduce this issue on my Ubuntu 11.04 setup but I haven't > been able to. > Have you faced the problem with the latest Eclipse 3.7 release > (I20110613-1736)? > Do you switch workspaces using keyboard shortcuts or through the workspace > switcher in unity launcher or via some other method? > This could be a unity bug but I cannot investigate further without being able > to reproduce the problem. I hit this problem regularly on I20110613-1736. It's much worse if I have two Eclipses running in different workspaces. Unfortunately I can't reproduce it at will. But I suggest trying maybe 3-4 Eclipses running in different workspaces, and have each of those running some application that they started in the same workspace. I always switch workspaces using the mouse by either clicking on the workspace switcher or clicking on the icon in the dock that is Eclipse.
(In reply to comment #5) > This could be related to this Unity bug which messes up window focus when an > application has multiple windows open - > https://bugs.launchpad.net/ubuntu/+source/unity/+bug/802527 It's possible it's this issue. I notice that keys have no effect, so it could be that the issue that the window that has the focus is not visible and it's antother Eclipse window in the same workspace (a self hosted Eclipse that I just launched). Next time it happens I will experiment with keys to see if the other Eclipse is getting the key strokes.
(In reply to comment #7) > (In reply to comment #5) > > This could be related to this Unity bug which messes up window focus when an > > application has multiple windows open - > > https://bugs.launchpad.net/ubuntu/+source/unity/+bug/802527 > It's possible it's this issue. I notice that keys have no effect, so it could > be that the issue that the window that has the focus is not visible and it's > antother Eclipse window in the same workspace (a self hosted Eclipse that I > just launched). Next time it happens I will experiment with keys to see if the > other Eclipse is getting the key strokes. Have you been able to verify this bug Francis? Since this behavior is most likely caused by a Unity bug, I would like to close this bug.
I have updated to Ubuntu Oneiric (11.10) and the bug is still there. I'm also running Eclipse 3.7.1. Generally when running one instance of Eclipse and nothing else it's much better on this release. However by starting two instances of the IDE (in different Unity workspaces, and in a different workspace in the browser), I was able to quickly reproduce it. This is a really annoying problem as when you hit it you have to select a window in another workspace and then play with that a bit and go back and hope your Eclipse window is fixed. Sometimes it is, sometimes not. Let me know if you need more information.
I have switched to GNOME 3 on Ubuntu 11.10 and the problem is gone; so it's something related to Unity.
I have the same problem in Unity, also. With Ubuntu 11.10 and Eclipse 3.7.1 (also with Juno).
I don't think this bug has anything to do with your Eclipse version. As far as I understand, it is caused by a Unity behavior bug referred to in comment 5. That bug is apparently fixed in recent versions of Unity and Compiz packages but I have not tested myself. Can you please verify if you can upgrade to the referred Unity/Compiz versions and see if the problem goes away? If that doesn't work, you might have to try using GNOME 3 but there is no way we can fix this issue in Eclipse. In fact, its a problem which occurs with any application which has multiple windows open in Unity.
Will be closing this as not an eclipse bug (it is a Ubuntu Unity bug), can be reopened if necessary. Thanks!
Closing the bug as per above comment.
