Problems running Swing app with latest build?

[Greg Brown]

Seems like that should be a higher-priority bug, especially if it affects Swing apps. It also doesn't appear to be limited to OS X 10.6/XQuartz 2.3, but happens on OS X 10.7/XQuartz 2.6 as well. Should I add this information to the bug report?
G

On Feb 13, 2012, at 1:37 PM, Roger Lewis wrote:

> There was a thread on a crash : http://mail.openjdk.java.net/pipermail/macosx-port-dev/2011-October/001068.html ,  the versions of libfreetype.6.dylib are different but the same error and results in a crash.
> 
>> 1): Library not loaded: /usr/X11/lib/libfreetype.6.dylib
> 
> A bug was opened which can be found here:
> http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=7124341
> 
> -Roger
> 
> 
> 
> On 2/13/12 10:06 AM, Greg Brown wrote:
>> Hi all,
>> 
>> I can't seem to launch the Swing Set demo with the latest build. I get the following error:
>> 
>> java -jar /Library/Java/Demos/JFC/SwingSet2/SwingSet2.jar
>> Exception in thread "main" java.lang.UnsatisfiedLinkError: /Library/Java/JavaVirtualMachines/1.7.0u-dev.jdk/Contents/Home/jre/lib/libfontmanager.dylib: dlopen(/Library/Java/JavaVirtualMachines/1.7.0u-dev.jdk/Contents/Home/jre/lib/libfontmanager.dylib, 1): Library not loaded: /usr/X11/lib/libfreetype.6.dylib
>>   Referenced from: /Library/Java/JavaVirtualMachines/1.7.0u-dev.jdk/Contents/Home/jre/lib/libfontmanager.dylib
>>   Reason: Incompatible library version: libfontmanager.dylib requires version 14.0.0 or later, but libfreetype.6.dylib provides version 13.0.0
>> 	at java.lang.ClassLoader$NativeLibrary.load(Native Method)
>> 	at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1928)
>> 	at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1846)
>> 	at java.lang.Runtime.loadLibrary0(Runtime.java:845)
>> 	at java.lang.System.loadLibrary(System.java:1084)
>> 	at sun.lwawt.macosx.LWCToolkit$1.run(LWCToolkit.java:73)
>> 	at java.security.AccessController.doPrivileged(Native Method)
>> 	at sun.lwawt.macosx.LWCToolkit.<clinit>(LWCToolkit.java:70)
>> 	at java.lang.Class.forName0(Native Method)
>> 	at java.lang.Class.forName(Class.java:186)
>> 	at java.awt.Toolkit$2.run(Toolkit.java:870)
>> 	at java.security.AccessController.doPrivileged(Native Method)
>> 	at java.awt.Toolkit.getDefaultToolkit(Toolkit.java:862)
>> 	at javax.swing.UIManager.getSystemLookAndFeelClassName(UIManager.java:607)
>> 	at javax.swing.UIManager$1.run(UIManager.java:1228)
>> 	at java.security.AccessController.doPrivileged(Native Method)
>> 	at javax.swing.UIManager.loadSwingProperties(UIManager.java:1223)
>> 	at javax.swing.UIManager.initialize(UIManager.java:1430)
>> 	at javax.swing.UIManager.maybeInitialize(UIManager.java:1420)
>> 	at javax.swing.UIManager.getUI(UIManager.java:1002)
>> 	at javax.swing.JPanel.updateUI(JPanel.java:126)
>> 	at javax.swing.JPanel.<init>(JPanel.java:86)
>> 	at javax.swing.JPanel.<init>(JPanel.java:109)
>> 	at javax.swing.JPanel.<init>(JPanel.java:117)
>> 	at SwingSet2.<init>(SwingSet2.java:191)
>> 	at SwingSet2.main(SwingSet2.java:251)
>> 
>> I also tried a build from a few days ago and I get the same error. I did not see this problem with the build I downloaded a couple of weeks ago.
>> 
>> Is this a known issue? Possibly a configuration issue on my end?
>> 
>> Thanks,
>> Greg
>>