Bug 493118 - [neon] conflicting handlers for org.eclipse.ui.navigate.backwardHistory
Summary: [neon] conflicting handlers for org.eclipse.ui.navigate.backwardHistory
Status: CLOSED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 4.6   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords: needinfo
Depends on:
Blocks:
 
Reported: 2016-05-06 04:21 EDT by Dennis Huebner CLA
Modified: 2020-10-17 14:45 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dennis Huebner CLA 2016-05-06 04:21:33 EDT
Eclipse DSL Neon M7
eclipse.buildId=4.6.0.I20160428-0800
java.version=1.8.0_45

After starting Neon M7 I've noticed an error log complaining about Conflicting handlers:

Conflicting handlers for org.eclipse.ui.navigate.backwardHistory: {ActionHandler(org.eclipse.ui.internal.dialogs.PreferencePageHistory$1@16139b0)} vs {ActionHandler(org.eclipse.ui.internal.NavigationHistoryAction@2fcffc05)}
Comment 1 Patrik Suzzi CLA 2016-05-06 05:30:41 EDT
It would be good to have: donwload link, list of additional plug-ins installed, and instructions the full error log. 

Thanks for reporting!
Comment 2 Patrik Suzzi CLA 2016-05-11 10:31:54 EDT
I cannot reproduce in Eclipse DSL Tools
Version: Neon Milestone 7 (4.6.0M7)
Build id:20160505-1310

This is a non-critical bug, initially spotted in 2014.

Most likely happens when different plug-ins are defining conflicting handlers. 

Could you please provide a download link or the steps to reproduce ?
Comment 3 Andrey Loskutov CLA 2018-10-27 02:56:55 EDT
Just got exact same conflict with 4.10 :

Conflicting handlers for org.eclipse.ui.navigate.backwardHistory: {ActionHandler(org.eclipse.ui.internal.dialogs.PreferencePageHistory$1@86fa656)} vs {ActionHandler(org.eclipse.ui.internal.NavigationHistoryAction@454e9d65)}

The log does not add the context and stack, I will push a patch to fix this, may be we see what is going on then.
Comment 4 Eclipse Genie CLA 2018-10-27 03:39:52 EDT
New Gerrit change created: https://git.eclipse.org/r/131540
Comment 5 Andrey Loskutov CLA 2018-10-27 03:41:42 EDT
(In reply to Eclipse Genie from comment #4)
> New Gerrit change created: https://git.eclipse.org/r/131540

The error looks now like this below (faked, since I can't reproduce the problem yet):

Conflicting handlers for command org.eclipse.ui.edit.text.toggleBlockSelectionMode: {ActionHandler(org.eclipse.ui.texteditor.BlockSelectionModeToggleAction@26c2f767)} vs {ActionHandler(org.eclipse.ui.texteditor.BlockSelectionModeToggleAction@26c2f767)} in: PartImpl (org.eclipse.e4.ui.compatibility.editor)  org.eclipse.jdt.ui.CompilationUnitEditor removeOnHide (A.java) Context

java.lang.IllegalStateException: Conflicting handlers: {[ActionHandler(org.eclipse.ui.texteditor.BlockSelectionModeToggleAction@26c2f767),  for 'org.eclipse.ui.edit.text.toggleBlockSelectionMode',  in PartImpl (org.eclipse.e4.ui.compatibility.editor)  org.eclipse.jdt.ui.CompilationUnitEditor removeOnHide (A.java) Context, activeWhen=AndExpression [children=[LegacyHandlerSubmission(Shell {runtime-Java9 - A/src/A.java - Eclipse SDK},null,PartSite(id=org.eclipse.jdt.ui.CompilationUnitEditor,pluginId=org.eclipse.jdt.ui,registeredName=Java Editor,hashCode=633578561)), ActivePartExpression(org.eclipse.jdt.internal.ui.javaeditor.CompilationUnitEditor@614ae4eb)]], active=true, sourcePriority=68162560, participating=true]} vs {[ActionHandler(org.eclipse.ui.texteditor.BlockSelectionModeToggleAction@26c2f767),  for 'org.eclipse.ui.edit.text.toggleBlockSelectionMode',  in TrimmedWindowImpl (IDEWindow) Context, activeWhen=AndExpression [children=[LegacyEditorActionBarExpression(org.eclipse.jdt.ui.CompilationUnitEditor), WorkbenchWindowExpression(org.eclipse.ui.internal.WorkbenchWindow@30704f85)]], active=true, sourcePriority=4210689, participating=true]} in: PartImpl (org.eclipse.e4.ui.compatibility.editor)  org.eclipse.jdt.ui.CompilationUnitEditor removeOnHide (A.java) Context
	at org.eclipse.ui.internal.handlers.LegacyHandlerService$HandlerSelectionFunction.compute(LegacyHandlerService.java:147)
	at org.eclipse.e4.core.internal.contexts.ValueComputation.get(ValueComputation.java:65)
	at org.eclipse.e4.core.internal.contexts.EclipseContext.internalGet(EclipseContext.java:251)
	at org.eclipse.e4.core.internal.contexts.EclipseContext.get(EclipseContext.java:238)
	at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.lookUpHandler(HandlerServiceImpl.java:103)
	at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.setEnabled(HandlerServiceHandler.java:75)
	at org.eclipse.core.commands.Command.setEnabled(Command.java:865)
	at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.canExecute(HandlerServiceImpl.java:179)
	at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.canExecute(HandlerServiceImpl.java:166)
	at org.eclipse.ui.internal.menus.MenuHelper$1.evaluate(MenuHelper.java:243)
	at org.eclipse.e4.ui.internal.workbench.ContributionsAnalyzer.isCoreExpressionVisible(ContributionsAnalyzer.java:289)
	at org.eclipse.e4.ui.internal.workbench.ContributionsAnalyzer.isVisible(ContributionsAnalyzer.java:263)
	at org.eclipse.e4.ui.workbench.renderers.swt.ContributionRecord.computeVisibility(ContributionRecord.java:170)
	at org.eclipse.e4.ui.workbench.renderers.swt.ContributionRecord.updateVisibility(ContributionRecord.java:101)
	at org.eclipse.e4.ui.workbench.renderers.swt.MenuManagerRendererFilter.updateElementVisibility(MenuManagerRendererFilter.java:194)
	at org.eclipse.e4.ui.workbench.renderers.swt.MenuManagerRendererFilter.updateElementVisibility(MenuManagerRendererFilter.java:205)
Comment 7 Eclipse Genie CLA 2020-10-17 14:45:17 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. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. 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.