Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 336844 - Cannot restart after installing as much of Indigo as possible
Summary: Cannot restart after installing as much of Indigo as possible
Status: RESOLVED WONTFIX
Alias: None
Product: Equinox
Classification: Eclipse Project
Component: Components (show other bugs)
Version: 3.7   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: equinox.components-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-02-10 11:48 EST by Andrew Overholt CLA
Modified: 2019-09-24 14:25 EDT (History)
3 users (show)

See Also:

Attachments
config.ini (1.45 KB, application/octet-stream)
2011-02-10 12:39 EST, Andrew Overholt CLA 		no flags Details
bundles.info (268.95 KB, application/octet-stream)
2011-02-10 12:39 EST, Andrew Overholt CLA 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Andrew Overholt CLA 2011-02-10 11:48:34 EST 
Eclipse IDE for Java and Report Developers

Version: Indigo Release
Build id: 20110204-0611

Linux/Gtk x86_64

I apologize if Equinox Components is not the correct place for this bug; I am not sure where equinox.ds bugs go.

I installed everything from Indigo that I could and after clicking the "restart now" button, I got the following and Eclipse didn't restart.  It also would not start again.

!ENTRY org.eclipse.equinox.ds 4 0 2011-02-10 11:27:23.403
!MESSAGE FrameworkEvent ERROR
!STACK 0
org.osgi.framework.BundleException: The bundle "org.eclipse.equinox.ds_1.3.0.v20110124-0830 [1698]" could not be resolved. Reason: Missing Constraint: Import-Package: org.eclipse.equinox.internal.util.event; version="1.0.0"
        at org.eclipse.osgi.framework.internal.core.AbstractBundle.getResolverError(AbstractBundle.java:1328)
        at org.eclipse.osgi.framework.internal.core.AbstractBundle.getResolutionFailureException(AbstractBundle.java:1312)
        at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:324)
        at org.eclipse.osgi.framework.internal.core.AbstractBundle.resume(AbstractBundle.java:390)
        at org.eclipse.osgi.framework.internal.core.Framework.resumeBundle(Framework.java:1130)
        at org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:559)
        at org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:544)
        at org.eclipse.osgi.framework.internal.core.StartLevelManager.incFWSL(StartLevelManager.java:457)
        at org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel(StartLevelManager.java:243)
        at org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent(StartLevelManager.java:438)
        at org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent(StartLevelManager.java:1)
        at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
        at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340)
Comment 1 Thomas Watson CLA 2011-02-10 11:57:35 EST 
This looks similar to bug 304338 and bug 304340

I wonder if p2 messed up the config.ini or if you are somehow missing the  org.eclipse.equinox.util bundle now.

Could you attach the config.ini and bundles.info used to launch?
Comment 2 Andrew Overholt CLA 2011-02-10 12:39:20 EST 
Created attachment 188706 [details]
config.ini

Here's my config.ini.
Comment 3 Andrew Overholt CLA 2011-02-10 12:39:37 EST 
Created attachment 188707 [details]
bundles.info

... and here's my bundles.info.
Comment 4 Lars Vogel CLA 2019-09-24 13:59:32 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.
Comment 5 Thomas Watson CLA 2019-09-24 14:25:57 EDT 
No plans to investigate this.