eclipse/swt need mozilla libxpcom.so nonstatic

Bug #41143 reported by Heitzso
6
Affects Status Importance Assigned to Milestone
mozilla (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

See http://www.eclipse.org/swt/faq.php#browserlinux
I recently upgraded by dev box to dapper and
the swt browser is now breaking as noted in the above
FAQ re statically linked mozilla/firefox libs.
Specifically, I get the following:
Exception in thread "main" org.eclipse.swt.SWTError: No more handles (java.lang.UnsatisfiedLinkError: /home/heitzso/visassist.build/singleuser/lib/linux/libswt-mozilla-gtk-3224.so: libxpcom.so: cannot open shared object file: No such file or directory)

I've tried pointing to both /usr/lib/mozilla and /usr/lib/firefox and
both libxpcom.so breaking.

This worked fine before upgrading to dapper.

I believe this is critical to a clean release ... eclipse (and swt)
must work cleanly in dapper, and that includes the builtin browser.

Revision history for this message
Heitzso (heitzso) wrote :

Not a bug.
In dapper I had to add /usr/lib/firefox to /etc/ld.so.conf
then rerun ldconfig to get my SWT app that uses a
browser widget to work. With that my swt app runs.

Note that I did have
    export MOZILLA_FIVE_HOME=/usr/lib/firefox
in my shell script ahead of the java invocation and that
was sufficient prior to Dapper, insufficient in Dapper.

Revision history for this message
Korny Sietsma (korny) wrote :

Note this only worked for me with the following steps:
"sudo ldconfig" (I didn't need to create /etc/ld.so/conf - I'm not clear on the format of this file)
add the following to the shell script running the app:
export MOZILLA_FIVE_HOME=/usr/lib/firefox
export LD_LIBRARY_PATH=${MOZILLA_FIVE_HOME}:${LD_LIBRARY_PATH}

without the LD_LIBRARY_PATH setting, I still got the error listed above.

Revision history for this message
chewnslovich (chewning-keith) wrote :

Thank you Korney. That worked perfectly. No need to edit ld.so.conf.

Daniel T Chen (crimsun)
Changed in mozilla:
status: New → Invalid
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.