Bug 149626

Summary: no swt-mozilla-gtk-3123 in java.library.path
Product: [Fedora] Fedora Reporter: Jeff Pound <jpound>
Component: eclipseAssignee: Andrew Overholt <overholt>
Status: CLOSED RAWHIDE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: rawhide   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: 3.1.0_fc-0.M5.9 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2005-03-08 18:19:30 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Jeff Pound 2005-02-24 17:21:47 UTC
Description of problem:
when trying to launch an SWT Browser a java.lang.UnsatisfiedLinkError
occurs with the message no "swt-mozilla-gtk-3123 in java.library.path"
This lib doesnt exist.

Version-Release number of selected component (if applicable):
3.1M5

How reproducible:
always

Steps to Reproduce:
1. Open an SWT Browser
  
Actual results:
the workbench "recommends" you exit. 

Expected results:
The browser should launch.

Additional info:
You can use the bugzilla plug-in to reproduce this bug. Just double
click an element in the bugzilla view to open the browser.

Comment 1 Jeff Pound 2005-02-24 18:58:06 UTC
swt-mozilla.jar[.so] exists in the eclipse install. Its just the
libswt-mozilla-gtk-<version>.so that is missing. Copying a
libswt-mozilla-gtk-<version>.so from an upstream build to
/usr/share/eclipse/plugins/org.eclipse.swt.gtk_3.1.0/os/linux/x86/
(and renaming it to the apropriate version) seems to solve the problem.

Comment 2 Andrew Overholt 2005-03-02 21:51:56 UTC
Changing target.

Comment 3 Andrew Overholt 2005-03-02 21:52:36 UTC
Assigning to me.

Comment 4 Andrew Overholt 2005-03-08 17:53:30 UTC
Jeff, can you verify that this is now fixed?  It should be fixed in
versions >= 3.1.0_fc-0.M5.9

Comment 5 Jeff Pound 2005-03-08 18:19:30 UTC
Verified fixed in 3.1.0_fc-0.M5.10 (sorry, dont have .9 around to test).