Ubuntu
eclipse package

org.osgi.framework.BundleException exception when starts

Bug #566131 reported by Tiago Hillebrandt
70
This bug affects 31 people
Affects Status Importance Assigned to Milestone
Eclipse
Fix Released
Medium
eclipse (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: eclipse

When starts eclipse by gnome-terminal, i can see the following exception: (even with exception the eclipse starts normally, but exception every appears)

tiago@scd-desktop:~$ 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)

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: eclipse 3.5.2-2ubuntu3
ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-21-generic i686
Architecture: i386
Date: Sun Apr 18 15:11:07 2010
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=pt_BR:pt:en
 LANG=pt_BR.UTF-8
 SHELL=/bin/bash
SourcePackage: eclipse
xulrunner-versions: /usr/lib/xulrunner-1.9.2.3

Revision history for this message
In , Philipp Nanz (philippn) wrote :

Build Identifier: I20100129-1300

When exporting a simple feature-based RCP product using the Product Export Wizard, launching the product for the first time will yield an exception in the .log file.

The problem only occurs when the option "Generate metadata repository" is checked.

Note: This bug also affects 3.5.1 and 3.5.2, please see http://dev.eclipse.org/newslists/news.eclipse.platform.rcp/msg35699.html

Reproducible: Always

Steps to Reproduce:
1. Import the attached projects
2. Run product export wizard on rcp.test/rcp.product
3. Be sure to check "Generate metadata repository"
4. Launch exported RCP app and inspect .log file

Revision history for this message
In , Philipp Nanz (philippn) wrote :

Created attachment 160603
Sample projects for reproducing this bug

Revision history for this message
In , Philipp Nanz (philippn) wrote :

Created attachment 160607
Log file

Revision history for this message
In , Tjwatson (tjwatson) wrote :

This looks similar to bug 304340

Revision history for this message
In , Philipp Nanz (philippn) wrote :

(In reply to comment #3)
> This looks similar to bug 304340

Indeed, it is the very same error message.

It should be noted though, that in my scenario no DS is used. It's just a very simple RCP plugin being referenced by a feature that in turn refers to the org.eclipse.rcp feature.

Revision history for this message
In , Tjwatson (tjwatson) wrote :

This is the same as bug 304340

The config.ini does not seem right in this case. The generated config.ini has
this ...

osgi.bundles=reference\:file\:org.eclipse.equinox.ds_1.2.0.v20100215.jar@1\:start,reference\:file\:org.eclipse.equinox.simpleconfigurator_1.0.200.v20100123-1019.jar@1\:start

Seems like it should only contain simpleconfigurator and not ds. If I remove
ds from the osgi.bundles property then it works with no errors. I also find it
strange that the start-level for ds is being set to 1. I thought the CU for ds
was to set this to start-level 2?

Revision history for this message
In , Tjwatson (tjwatson) wrote :

*** Bug 304340 has been marked as a duplicate of this bug. ***

Revision history for this message
In , Aniefer (aniefer) wrote :

Default start levels are generated in build.
The start level of 1 came from the original patch from Chris on bug 260315. I will change the default to 2 (that is also what the SDK uses).

Work around is to set all your start levels explicitly in the .product file. (You need to do them all since defaults don't happen if any are set).

Revision history for this message
In , Aniefer (aniefer) wrote :

I updated pde/build to set 2 as the default level for ds

Revision history for this message
In , Philipp Nanz (philippn) wrote :

I'm still seeing this bug as of 3.6 M6 (I20100312-1448)

Revision history for this message
In , Philipp Nanz (philippn) wrote :

(In reply to comment #9)
> I'm still seeing this bug as of 3.6 M6 (I20100312-1448)

The generated config ini still reads

osgi.bundles=reference\:file\:org.eclipse.equinox.ds_1.2.0.v20100301.jar@1\:start,reference\:file\:org.eclipse.equinox.simpleconfigurator_1.0.200.v20100304.jar@1\:start

Revision history for this message
In , Aniefer (aniefer) wrote :

Sorry, I missed one case. DS should now be at 2. Fix is in next IBuild I20100323

Revision history for this message
In , Tjwatson (tjwatson) wrote :

*** Bug 308142 has been marked as a duplicate of this bug. ***

Revision history for this message
Tiago Hillebrandt (tiagohillebrandt) wrote :
Revision history for this message
Tiago Hillebrandt (tiagohillebrandt) wrote :

This is an eclipse bug and already was fixed on eclipse 3.6.

https://bugs.eclipse.org/bugs/show_bug.cgi?id=304338

Revision history for this message
nanouck (nanouck) wrote :

Hello Tiago,

i've got the same issue with osgi, i've got the following traces

!ENTRY org.eclipse.osgi 2 0 2010-04-22 12:29:34.096
!MESSAGE One or more bundles are not resolved because the following root constraints are not resolved:
!SUBENTRY 1 org.eclipse.osgi 2 0 2010-04-22 12:29:34.097
!MESSAGE Bundle reference:file:plugins/org.eclipse.equinox.p2.director_1.0.101.R35x_v20100112.jar was not resolved.
!SUBENTRY 2 org.eclipse.equinox.p2.director 2 0 2010-04-22 12:29:34.098
!MESSAGE Missing required bundle org.sat4j.core_2.1.0.
!SUBENTRY 2 org.eclipse.equinox.p2.director 2 0 2010-04-22 12:29:34.099
!MESSAGE Missing required bundle org.sat4j.pb_2.1.0.

regarding eclipse-platform (3.5.2-2ubuntu3) symlinks, sat4j are broken, I do not know which one are right
$ ls -l -F /usr/lib/eclipse/plugins/org.sat4j.*
lrwxrwxrwx 1 root root 39 2010-04-21 15:31 /usr/lib/eclipse/plugins/org.sat4j.core_2.1.1.v20100202.jar -> ../../../share/sat4j/org.sat4j.core.jar
lrwxrwxrwx 1 root root 37 2010-04-21 15:31 /usr/lib/eclipse/plugins/org.sat4j.pb_2.1.1.v20100202.jar -> ../../../share/sat4j/org.sat4j.pb.jar

but org.sat4j.pb.jar and org.sat4j.core.jar are not in /usr/share/sat4j but in /usr/share/java/ see http://packages.ubuntu.com/lucid/all/sat4j/filelist (2.1.1-3)

workaround:
sudo ln -f -s ../../../share/java/org.sat4j.core.jar /usr/lib/eclipse/plugins/org.sat4j.core_2.1.1.v20100202.jar
sudo ln -f -s ../../../share/java/org.sat4j.pb.jar /usr/lib/eclipse/plugins/org.sat4j.pb_2.1.1.v20100202.jar
eclipse -clean -initialize

IMHO, the official correction should be to update symlinks in eclipse-platform package or use another in sat4j
please can someone correct one of these universe package.

Regards

Nicolas

Revision history for this message
Niels Thykier (niels-thykier) wrote : Re: [Bug 566131] Re: org.osgi.framework.BundleException exception when starts

nanouck wrote:
> Hello Tiago,
>
> i've got the same issue with osgi, i've got the following traces
>
> !ENTRY org.eclipse.osgi 2 0 2010-04-22 12:29:34.096
> !MESSAGE One or more bundles are not resolved because the following root constraints are not resolved:
> !SUBENTRY 1 org.eclipse.osgi 2 0 2010-04-22 12:29:34.097
> !MESSAGE Bundle reference:file:plugins/org.eclipse.equinox.p2.director_1.0.101.R35x_v20100112.jar was not resolved.
> !SUBENTRY 2 org.eclipse.equinox.p2.director 2 0 2010-04-22 12:29:34.098
> !MESSAGE Missing required bundle org.sat4j.core_2.1.0.
> !SUBENTRY 2 org.eclipse.equinox.p2.director 2 0 2010-04-22 12:29:34.099
> !MESSAGE Missing required bundle org.sat4j.pb_2.1.0.
>
> regarding eclipse-platform (3.5.2-2ubuntu3) symlinks, sat4j are broken, I do not know which one are right
> $ ls -l -F /usr/lib/eclipse/plugins/org.sat4j.*
> lrwxrwxrwx 1 root root 39 2010-04-21 15:31 /usr/lib/eclipse/plugins/org.sat4j.core_2.1.1.v20100202.jar -> ../../../share/sat4j/org.sat4j.core.jar
> lrwxrwxrwx 1 root root 37 2010-04-21 15:31 /usr/lib/eclipse/plugins/org.sat4j.pb_2.1.1.v20100202.jar -> ../../../share/sat4j/org.sat4j.pb.jar
>
> but org.sat4j.pb.jar and org.sat4j.core.jar are not in /usr/share/sat4j
> but in /usr/share/java/ see
> http://packages.ubuntu.com/lucid/all/sat4j/filelist (2.1.1-3)
>
> workaround:
> sudo ln -f -s ../../../share/java/org.sat4j.core.jar /usr/lib/eclipse/plugins/org.sat4j.core_2.1.1.v20100202.jar
> sudo ln -f -s ../../../share/java/org.sat4j.pb.jar /usr/lib/eclipse/plugins/org.sat4j.pb_2.1.1.v20100202.jar
> eclipse -clean -initialize
>
> IMHO, the official correction should be to update symlinks in eclipse-platform package or use another in sat4j
> please can someone correct one of these universe package.
>
> Regards
>
> Nicolas
>

Hi

Yes, the sat4j jar files moved to /usr/share/java recently - I got a
heads up about it a week ago in Debian, but I honestly did not expect
sat4j would be imported into Ubuntu just now.

@bdrung: Can you get a binNMU scheduled for eclipse in Ubuntu against
the new sat4j (It has version 2.1.1-3 in Debian/unstable)

~Niels

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

Uploaded eclipse.

Changed in eclipse (Ubuntu):
status: New → Fix Committed
Revision history for this message
Alwin Garside (yogarine) wrote :

Is bug #566333 a duplicate of this?

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package eclipse - 3.5.2-2ubuntu4

---------------
eclipse (3.5.2-2ubuntu4) lucid; urgency=low

  * No source change rebuild to pick up new location of sat4j (LP: #566131).
 -- Benjamin Drung <email address hidden> Thu, 22 Apr 2010 14:38:12 +0200

Changed in eclipse (Ubuntu):
status: Fix Committed → Fix Released
Revision history for this message
In , Filip-hrbek-k (filip-hrbek-k) wrote :

*** Bug 310472 has been marked as a duplicate of this bug. ***

Revision history for this message
In , Cwindatt (cwindatt) wrote :

*** Bug 276950 has been marked as a duplicate of this bug. ***

Revision history for this message
In , evans (evans) wrote :

The documentation for 3.5.1 (Build id: M20090917-0800), topic "Configuring p2 Products" says the Start Level should be 1 (how I happened to be using 1 and hence getting the bug). This is just a note to ask you to check that the documentation has been changed as well as the implementation.

Thanks.

Bug Watch Updater (bug-watch-updater)
Changed in eclipse-eclipsers:
importance: Unknown → Medium
status: Unknown → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Subscribing...

Other bug subscribers

Remote bug watches

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