Problems running Swing app with latest build? (original) (raw)
Greg Brown greg.x.brown at oracle.com
Mon Feb 13 12:32:09 PST 2012
- Previous message: Problems running Swing app with latest build?
- Next message: Problems running Swing app with latest build?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Thanks for the suggestion. Updating to 10.7.3 appears to have resolved the problem, though oddly enough my XQuartz version did not change.
Greg
On Feb 13, 2012, at 2:50 PM, Anthony Petrov wrote:
Hi Greg,
I got the same error last week on a 10.6.8 (Snow Leopard) system. Running System Update and installing all the latest updates (W/O upgrading to Lion) did resolve the issue with the libfreetype. Hope this helps. -- best regards, Anthony On 2/13/2012 10:06 PM, 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.(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.(JPanel.java:86) at javax.swing.JPanel.(JPanel.java:109) at javax.swing.JPanel.(JPanel.java:117) at SwingSet2.(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
- Previous message: Problems running Swing app with latest build?
- Next message: Problems running Swing app with latest build?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]