3.5.2-2ubuntu3 version breaks p2 update, plugins

Bug #567113 reported by Adrian Wilkins
48
This bug affects 9 people
Affects Status Importance Assigned to Milestone
eclipse (Ubuntu)
New
Undecided
Unassigned
Nominated for Lucid by Paul Logasa Bogen II

Bug Description

Binary package hint: eclipse

1) Ubuntu Lucid up to date as of 2010-04-20 0830

2) eclipse-3.5.2-2ubuntu3 + it's associated package constellation, + java-6-openjdk (no Oracle JVM on the machine).

After upgrading to 3.5.2-2ubuntu3 the following error occurs, various plugins (like Mylyn) no longer work, the software update has reverted to the "old" style, which also no longer works (producing errors as in #530414).

3.5.2-2ubuntu2 seemed to be working ok .. the changelog says you just added a hook for apport which doesn't seem like it should have caused this.

adrian@motoko:~$ eclipse
org.osgi.framework.BundleException: The bundle could not be resolved. Reason: Missing Constraint: Import-Package: org.eclipse.equinox.internal.provisional.p2.director; version="0.0.0"
 at org.eclipse.osgi.framework.internal.core.AbstractBundle.getResolverError(AbstractBundle.java:1313)
 at org.eclipse.osgi.framework.internal.core.AbstractBundle.getResolutionFailureException(AbstractBundle.java:1297)
 at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:309)
 at org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:280)
 at org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:272)
 at org.eclipse.equinox.internal.simpleconfigurator.ConfigApplier.startBundles(ConfigApplier.java:307)
 at org.eclipse.equinox.internal.simpleconfigurator.ConfigApplier.install(ConfigApplier.java:108)
 at org.eclipse.equinox.internal.simpleconfigurator.SimpleConfiguratorImpl.applyConfiguration(SimpleConfiguratorImpl.java:129)
 at org.eclipse.equinox.internal.simpleconfigurator.SimpleConfiguratorImpl.applyConfiguration(SimpleConfiguratorImpl.java:143)
 at org.eclipse.equinox.internal.simpleconfigurator.Activator.start(Activator.java:48)
 at org.eclipse.osgi.framework.internal.core.BundleContextImpl$1.run(BundleContextImpl.java:783)
 at java.security.AccessController.doPrivileged(Native Method)
 at org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:774)
 at org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:755)
 at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:352)
 at org.eclipse.osgi.framework.internal.core.AbstractBundle.resume(AbstractBundle.java:370)
 at org.eclipse.osgi.framework.internal.core.Framework.resumeBundle(Framework.java:1068)
 at org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:557)
 at org.eclipse.osgi.framework.internal.core.StartLevelManager.incFWSL(StartLevelManager.java:464)
 at org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel(StartLevelManager.java:248)
 at org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent(StartLevelManager.java:445)
 at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:227)
 at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:337)

Revision history for this message
André (afsverissimo) wrote :

i can confirm this exception,

Using Sun's 'Java(TM) SE Runtime Environment (build 1.6.0_20-b02)'

Revision history for this message
Jean-Philippe LECHÊNE (jphlechene) wrote :

Hello,

 Same situation here : the JBoss Tools AS plugins does not work anymore with this version. (using OpenJDK 64-Bit Server VM (build 14.0-b16, mixed mode)

Revision history for this message
Nick Maynard (nick-maynard) wrote :

Also seeing this, using IBM SDK 6.0.
Downgrading to 3.5.2-2ubuntu2 doesn't appear to work, but of course it's possible I've got that process wrong.

Please fix this ASAP - I can't do any work!

Changed in eclipse (Ubuntu):
assignee: nobody → Benjamin Drung (bdrung)
Revision history for this message
Nick Maynard (nick-maynard) wrote :

Assigning this to Benjamin as he checked in the new package version.

Revision history for this message
Adrian Wilkins (adrian-wilkins) wrote :

Happily the eclipse.org distribution unpacked to your home folder seems to work well, so I can at least work. The GTK bugs that plagued the previous version seem to have been corrected either in Eclipse or in Lucid.

Mildly annoying that I had to reinstall my plugins, but never mind.

Revision history for this message
Benjamin Drung (bdrung) wrote :

I unassign me. The change from 3.5.2-2ubuntu2 to 3.5.2-2ubuntu3 (the added apport hook) shouldn't cause this bug. It's probably caused by something else.

I do not experience your problems. Can you rename/remove ~/.eclipse (this will remove all your plugins) and install the plugins step by step. Does this lead to this error message again?

Changed in eclipse (Ubuntu):
assignee: Benjamin Drung (bdrung) → nobody
Revision history for this message
Clemens Hupka (clemens) wrote :

Same problem here. Removing ~/.eclipse didn't help. Will try to purge the whole Eclipse-installation tomorrow... Would be awful to have an LTS without Eclipse...

Revision history for this message
Clemens Hupka (clemens) wrote :

Seems to be a duplicate of Bug #566131

Revision history for this message
Nick Maynard (nick-maynard) wrote :

Not sure of the duplicate status - that bug mentions that Eclipse still works regardless of the error. Whereas the submitters here seem to have a non-functioning Eclipse.

Does anyone know if the previous version, 3.5.2_2ubuntu2, still works? If it does, the problem isn't environmental and I wonder if backing out 3.5.2_2ubuntu3 might be the quickest fix before LTS release. I can't seem to get hold of 3.5.2_2ubuntu2 any more.

Personally I now have a version of 3.5.2 downloaded from eclipse.org and running - have given up on the Ubuntu package until ths bug is fixed.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.