Bug 340199

Comment 1 Olivier Thomann 2011-03-25 10:58:52 EDT

I found new ones using I20110323-1055:
A conflict occurred for CTRL+O:Binding(CTRL+O,
ParameterizedCommand(Command(org.eclipse.jdt.ui.edit.text.java.show.outline,Quick Outline,
,
Category(org.eclipse.ui.category.navigate,Navigate,null,true),
org.eclipse.ui.internal.Workbench$MakeHandlersGo@7757fe3d,
,,true),null),
org.eclipse.ui.defaultAcceleratorConfiguration,
org.eclipse.jdt.ui.javaEditorScope,,,system)
Binding(CTRL+O,
ParameterizedCommand(Command(org.eclipse.pde.ui.quickOutline,Quick Outline,
,
Category(org.eclipse.ui.category.navigate,Navigate,null,true),
org.eclipse.ui.internal.Workbench$MakeHandlersGo@7757fe3d,
,,true),null),
org.eclipse.ui.defaultAcceleratorConfiguration,
org.eclipse.pde.ui.pdeEditorContext,,,system)

A conflict occurred for CTRL+SHIFT+F:Binding(CTRL+SHIFT+F,
ParameterizedCommand(Command(org.eclipse.jdt.ui.edit.text.java.format,Format,
,
Category(org.eclipse.jdt.ui.category.source,Source,Java Source Actions,true),
org.eclipse.ui.internal.Workbench$MakeHandlersGo@7757fe3d,
,,true),null),
org.eclipse.ui.defaultAcceleratorConfiguration,
org.eclipse.jdt.ui.javaEditorScope,,,system)
Binding(CTRL+SHIFT+F,
ParameterizedCommand(Command(org.eclipse.pde.ui.edit.text.format,Format Source,
,
Category(org.eclipse.pde.ui.category.source,Manifest Editor Source,PDE Source Page actions,true),
org.eclipse.ui.internal.Workbench$MakeHandlersGo@7757fe3d,
,,true),null),
org.eclipse.ui.defaultAcceleratorConfiguration,
org.eclipse.pde.ui.pdeEditorContext,,,system)

Comment 2 Joachim Mairböck 2011-04-20 06:41:22 EDT

I get similar messages in the Console as well, but only on subsequent startups (i.e. when there is a saved state that is restored). It seems that every binding is listed twice, for the same command.

For example:
!SUBENTRY 1 org.eclipse.jface 2 0 2011-04-20 12:30:25.156
!MESSAGE A conflict occurred for CTRL+S:
Binding(CTRL+S,
	ParameterizedCommand(Command(org.eclipse.ui.file.save,Save,
		,
		Category(org.eclipse.e4.ui.model.application.MApplication,Application Category,null,true),
		org.eclipse.ui.internal.Workbench$MakeHandlersGo@32ef2d,
		,,true),null),
	org.eclipse.ui.defaultAcceleratorConfiguration,
	org.eclipse.ui.contexts.window,,,system)
Binding(CTRL+S,
	ParameterizedCommand(Command(org.eclipse.ui.file.save,Save,
		,
		Category(org.eclipse.e4.ui.model.application.MApplication,Application Category,null,true),
		org.eclipse.ui.internal.Workbench$MakeHandlersGo@32ef2d,
		,,true),null),
	org.eclipse.ui.defaultAcceleratorConfiguration,
	org.eclipse.ui.contexts.window,,,system)

Comment 3 Joachim Mairböck 2011-04-20 06:44:46 EDT

(In reply to comment #2)
> I get similar messages in the Console as well, but only on subsequent startups
> (i.e. when there is a saved state that is restored). It seems that every
> binding is listed twice, for the same command.


My build Id is I20110419-2200 (Eclipse 4.1). I am running a classic RCP application in compatibility mode.

Comment 4 Paul Webster 2011-05-13 15:25:53 EDT

I haven't yet been able to reproduce this.  If someome could check their steps on a build based on I20110512-2200 I can have a look.

PW

Comment 5 Joachim Mairböck 2011-05-16 02:18:23 EDT

With Build I20110504-2200 (I cannot update at the moment), I can also only reproduce the bug if activate all the plugins of the target platform, even the Team related ones (which are not needed for. And even there, it is not really this bug because there are no duplicate bindings for the same command, but the commands are different. So the bug WORKSFORME now. ;-)

Comment 6 Eclipse Genie 2019-05-23 11:14:04 EDT

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.

Comment 7 Lars Vogel 2019-06-05 07:30:16 EDT

This is a mass change to close all e4 bugs marked with "stalebug" whiteboard.

If this bug is still valid, please reopen and remove the "stalebug" keyword.