New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to load library 'rococoa' #3904
Comments
A previous reporter posted the following stacktrace from the system.log.
|
Can you find any similar related output in the system.log (/Applications/Utilities/Console.app)? |
|
Same problem for me using Cyberduck 3.5.1 (10.5.8, 2.5GHz Core 2 Duo MBP). Moving it outside the Applications folder doesn't help. Console log as follows:
Quick Google suggests that http://stackoverflow.com/questions/1670859/wrapping-an-existing-application-with-jni may possibly have some relevant suggestions on fixing it. |
Please check the folders /Library/Java/Extensions and ~/Library/Java/Extensions for thirdparty libraries installed. |
I suddenly have this problem after updating through the built-in menu today. I have no files in either Java/Extensions folder and it does not work even if I move Cyberduck to the Desktop. From system.log:
|
Just fixed this by changing the Java Application Runtime Settings in Java Preferences. I previously had J2SE 5.0, J2SE 5.0 (64-bit), Java SE 6 (64-bit), J2SE 1.4.2, in that order. I have now swapped the first two around so that the 64-bit version is first, and therefore preferred. Cyberduck will now launch ok. |
Replying to [comment:9 richard fairhurst]:
We ship the native library of Rococoa as a universal binary.
I don't see a reason why it should not load with J2SE 5.0 or J2SE 5.0 (64-bit). Is this a unsupported configuration by Apple (i.e. custom build Java runtime?) I don't know of a 64bit J2SE 5.0 release. |
As far as I know it's not a custom build - I've not knowingly installed one. JavaVM framework appears to be 12.1.0 if that helps. I haven't installed the Java for Mac OS X 10.5 Update 5. |
If I keep the Cyberduck app anywhere else but inside the applications folder it will launch.
The text was updated successfully, but these errors were encountered: