Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 312638

Summary: The bundle "org.eclipse.equinox.ds_1.2.0.v20100422-1745 [56]" could not be resolved
Product: [Eclipse Project] Equinox Reporter: Darin Wright <darin.eclipse>
Component: p2Assignee: P2 Inbox <equinox.p2-inbox>
Status: CLOSED WONTFIX QA Contact:
Severity: normal    
Priority: P3 CC: pascal, tjwatson
Version: unspecified   
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
Whiteboard: stalebug
Attachments:
Description Flags
bundles.info none

Description Darin Wright CLA 2010-05-12 10:40:42 EDT 
When launching the latest I-build, I get this error in my .log. I also see it when selfhosting.

eclipse.buildId=I20100511-0800
java.version=1.6.0_18
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
Command-line arguments:  -os win32 -ws win32 -arch x86


Error
Wed May 12 08:41:28 CDT 2010


org.osgi.framework.BundleException: The bundle "org.eclipse.equinox.ds_1.2.0.v20100422-1745 [56]" could not be resolved. Reason: Another singleton version selected: org.eclipse.equinox.ds_1.2.0.v20100507
at org.eclipse.osgi.framework.internal.core.AbstractBundle.getResolverError(AbstractBundle.java:1317)
at org.eclipse.osgi.framework.internal.core.AbstractBundle.getResolutionFailureException(AbstractBundle.java:1301)
at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:319)
at org.eclipse.osgi.framework.internal.core.AbstractBundle.resume(AbstractBundle.java:374)
at org.eclipse.osgi.framework.internal.core.Framework.resumeBundle(Framework.java:1067)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:561)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:546)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.incFWSL(StartLevelManager.java:459)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel(StartLevelManager.java:243)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent(StartLevelManager.java:440)
at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:227)
at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:337)
Comment 1 Thomas Watson CLA 2010-05-12 10:45:06 EDT 
This appears to be an issue with p2 not uninstalling some bundles on an upgrade.  Moving to p2.  Darin, please attach the bundles.info.  It must have ds listed twice.
Comment 2 Darin Wright CLA 2010-05-12 10:54:39 EDT 
Created attachment 168156 [details]
bundles.info

There are many duplicates in my bundles.info. I was upgrading from I20100506-0800 to I20100511-0800. I had some patches installed in the SDK that did not get uninstalled when upgrading, so I manually uninstalled after the upgrade.
Comment 3 Pascal Rapicault CLA 2010-05-12 23:25:10 EDT 
I think it may be related to the presence of the patches. I'll take a look to see if I can reproduce.
Comment 4 Thomas Watson CLA 2010-05-13 09:21:12 EDT 
I also think it may be related to patches, I had a similar thing happen to me, but the steps to reproduce are not predictable.  I tried to repeat a process of patching/upgrading etc. and could not get duplicates to show up again in my environment.
Comment 5 Eclipse Genie CLA 2019-01-12 03:39:54 EST 
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 6 Lars Vogel CLA 2019-09-24 13:55:25 EDT 
This bug was marked as stalebug a while ago. Marking as worksforme.

If this report is still relevant for the current release, please reopen and remove the stalebug whiteboard tag.