Community
Participate
Working Groups
If I use the hide keybinding (Command/Apple-H), then Cmd-tab back to eclipse, most keybindings don't work (e.g. Open type, Cmd-Shift-T). The keybinding hints in menus have all disappeared too. If I then I Cmd-Tab out to another app, then Cmd-tab back into eclipse, the key bindings start working again. eclipse 3.2M6 on os x 10.4.5 using java 1.4.2_09
Could you please start running with a -debug <file> that contains: org.eclipse.ui/debug=true org.eclipse.ui/trace/keyBindings=true org.eclipse.ui/trace/keyBindings.verbose=true org.eclipse.ui/trace/sources=true org.eclipse.ui/trace/handlers=true org.eclipse.ui/trace/handlers.verbose=true org.eclipse.ui/trace/contexts=true org.eclipse.ui/trace/contexts.verbose=true Pipe the output to log file. ex, I use: eclipse -debug debug.options >tracing.log 2>&1 but I'm not sure how to do that on a Mac. I look at the "points" in the log where: CMD+SHIFT+T works CMD+SHIFT+T doesn't work CMD+SHIFT+T works Thanx, PW
Were you able to reproduce the problem? PW
I doesn't always happen on startup, sometimes it takes a while before it shows up, and of course, I never seem to be running with tracing enabled when it happens because command line eclipse doesn't run well on os x ( see bug 139994 ) :( I just setup a script for launching eclipse with tracing enabled, to avoid the above issue, which I'll run till I can duplicate it - hopefully this weekend sometime (using RCC3 now) On a related (?) note, sometimes the Hide key (Cmd-H) itself stops working (Eclipse menu flashes like its doing something, but nada), and then I _really_ can't duplicate it :) Either way, you should get something out of the log. In fact Hide key aint working right now, with tracing enabled! expect a trace soon :)
Ok, I was mistaken in my last comment, I wasn't running from the command line when Cmd-H stopped working. However, I did manage to reproduce the original problem with tracing enabled. I think the problem exhibits itself after suspending/reawakening my laptop since it wasn't there after startup and right before I closed the lod, but was there as soon as I opened the lid. Its a little hard to figure out where in the logfile what happens, but I determined the size of the file before starting the sequence below (2403878 bytes), and marked that point (search for *** in the attached log file), so at least you know exactly what I'm doing from that point on: Cmd-tab to eclipse Cmd-shift-t (works) Cmd-h (hide) Cmd-tab to eclipse Cmd-shift-t (doesn't work) Cmd-tab out and back in again Cmd-shift-t (works) this is with 3.2RC3
Created attachment 40557 [details] trace with problem duplicated If you need a finer granularity of when I hit which key, let me know of a way to do it since I can't edit the file while its being written to, and if I switch to a terminal to look at the size of the file at that point, those keypresses will affect behavior as well as what goes in the trace!
Is this the same/related to bug 139711?
*** Bug 140995 has been marked as a duplicate of this bug. ***
I'm affected by this as well running 3.2RC7 but I'm not able to reproduce it by just hiding Eclipse and coming back to the app. It seems to be random but if I can figure out a pattern I'll create a log file.
(In reply to comment #6) > Is this the same/related to bug 139711? > I think it might be except for me, my context menu also loses shortcuts. I've also noticed that they sometimes come back after I've fiddled with the eclipse window, or minimised/maximised. I haven't worked out anything consistent. Channing
*** Bug 146401 has been marked as a duplicate of this bug. ***
I've been able to recreate this on 3.2RC7 on Mac 10.4.6(PPC) with Java 5 installed. After hiding, regardless of how I reactivate (Cmd+Tab/clicking on dock) the Command+ keystrokes seem to go missing, until I switch to another app and back again (again, either with Cmd+Tab or clicking on the dock).
Confirming that the problem remains in 3.2.0 (M20060629-1905), on 10.4.7 (Intel) running Java 5. Is there anything we can do to assist the Eclipse team debug this? I'd be happy to provide trace files to supplement Matt Conway's trace if that would be of value. Thanks!
Also, I've noticed that (at least in my case) it does not matter how I send Eclipse into the background/foreground. The problem will sometimes occur even if I click on my desktop and then back into the Eclipse window. It also happens if I click on the dock to switch apps. It seems that cmd-tab, cmd-h, etc are just variations on the theme of losing and then regaining focus.
*** Bug 152105 has been marked as a duplicate of this bug. ***
Hi, I just woke my mac from sleep and eclipse was running. My accelerators were missing on all the menus, also content assist didn't work. I had a look in my console.log which had the stack below. I don't know if it helps at all but its just more info. Exception in thread "AutoAssist Delay" org.eclipse.swt.SWTException: Failed to execute runnable (org.eclipse.jface.text.Assert$AssertionFailedException: null argument;) at org.eclipse.swt.SWT.error(SWT.java:3374) at org.eclipse.swt.SWT.error(SWT.java:3297) at org.eclipse.swt.widgets.Synchronizer.syncExec(Synchronizer.java:178) at org.eclipse.ui.internal.UISynchronizer.syncExec(UISynchronizer.java:28) at org.eclipse.swt.widgets.Display.syncExec(Display.java:3825) at org.eclipse.jface.text.contentassist.ContentAssistant$AutoAssistListener.showAssist(ContentAssistant.java:336) at org.eclipse.jface.text.contentassist.ContentAssistant$AutoAssistListener.run(ContentAssistant.java:252) at java.lang.Thread.run(Thread.java:613) Caused by: org.eclipse.jface.text.Assert$AssertionFailedException: null argument; at org.eclipse.jface.text.Assert.isNotNull(Assert.java:157) at org.eclipse.jface.text.Assert.isNotNull(Assert.java:133) at org.eclipse.jface.text.contentassist.ContentAssistant.setRepeatedInvocationTrigger(ContentAssistant.java:2125) at org.eclipse.jdt.internal.ui.text.java.ContentAssistProcessor$2.assistSessionStarted(ContentAssistProcessor.java:163) at org.eclipse.jface.text.contentassist.ContentAssistant.fireSessionBeginEvent(ContentAssistant.java:1992) at org.eclipse.jface.text.contentassist.ContentAssistant.prepareToShowCompletions(ContentAssistant.java:1469) at org.eclipse.jface.text.contentassist.ContentAssistant.access$6(ContentAssistant.java:1462) at org.eclipse.jface.text.contentassist.ContentAssistant$2.run(ContentAssistant.java:345) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:123) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3181) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2936) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1914) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1878) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:419) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:95) at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:78) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:92) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:68) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:400) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:177) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.eclipse.core.launcher.Main.invokeFramework(Main.java:336) at org.eclipse.core.launcher.Main.basicRun(Main.java:280) at org.eclipse.core.launcher.Main.run(Main.java:977) at org.eclipse.core.launcher.Main.main(Main.java:952)
*** Bug 154879 has been marked as a duplicate of this bug. ***
Created attachment 50474 [details] another trace exhibiting the problem On line 59702, the repeated key commands to save and find have no effect. I then moused around in the menu bar and confirmed that the keyboard shortcut information was missing. Then I switched focus to the Finder and then back to Eclipse. Finally, on line 59925, I type command-S and the save takes place.
*** Bug 157835 has been marked as a duplicate of this bug. ***
I also noticed that code suggestions do not appear when Eclipse is in the problematic state. Switching focus away from and then back to Eclipse restored the auto-completion capability. Hopefully that's a useful clue.
This happens on my Mac as well, every single time I'm hiding the application and switch then back, all shortcuts are lost. I always have to switch to another application and then back. Unfortunately, this is not just a bug, this is a major bug, i will have to change back to jBuilder
Patrick, are all key bindings lost or just some specific ones? Which build are you using.
Yep, all key bindings are gone. Build id: 20061111-5.1.0-GA
What's that build id? That doesn't sound like an Eclipse SDK build id. What version is it (3.2.1?). Are the key bindings also lost in the default text editor or are really all, including global key bindings like e.g. Ctrl+H to open the Search dialog lost?
Well, this is MyEclipse Build Id. I got eclipse 3.2.1. I dont' know where to find build nr from eclipse¨
Patrick, could you please check whether the same problem appears if just using Eclipse SDK 3.2.1 (http://download.eclipse.org/downloads/drops/R-3.2.1-200609210945/index.php) with no additional plug-ins? Thanks.
Sir, I just downloaded the 3.2.1 version. I started Eclipse with no othe plug-ins, unfortunately i got the same effect.
>This happens on my Mac as well, every single time I'm hiding the application >and switch then back, all shortcuts are lost. I always have to switch to >another application and then back. Unfortunately, this is not just a bug, this >is a major bug, i will have to change back to jBuilder I believe this problem has been fixed in 3.3 already (See bug#139711). Please try the latest build.
Yes, I just download build 3.3 M4 and it works, yeahh!!! Thank you guys, that was a major problem for me. Thanks!!!!
I can confirm that this problem ssems to have disappeared in 3.3M4 for me as well - lets hope it stays that way :) Feel free to close this bug if appropriate.
(In reply to comment #29) > I can confirm that this problem ssems to have disappeared in 3.3M4 for me as > well - lets hope it stays that way :) Me too.
*** This bug has been marked as a duplicate of bug 139711 ***
Changing OS from Mac OS to Mac OS X as per bug 185991
