Skip to content
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

CD launches, but all menus grey, and can't open a new connection. #1128

Closed
cyberduck opened this issue May 26, 2007 · 7 comments
Closed

CD launches, but all menus grey, and can't open a new connection. #1128

cyberduck opened this issue May 26, 2007 · 7 comments

Comments

@cyberduck
Copy link
Collaborator

3196345 created the issue

FYI, I am using Java 1.6DP from a couple weeks ago. It may be the root cause. Here is the output in console.log.

ben@crushftp.com

2007-05-26 16:43:13.567 Cyberduck[22938] Unknown class `ch.cyberduck.ui.cocoa.delegate.HistoryMenuDelegate' in nib file, using `NSObject' instead.
2007-05-26 16:43:13.596 Cyberduck[22938] Unknown class `ch.cyberduck.ui.cocoa.CDMainController' in nib file, using `NSObject' instead.
2007-05-26 16:43:13.691 Cyberduck[22938] Unknown class `ch.cyberduck.ui.cocoa.delegate.EditMenuDelegate' in nib file, using `NSObject' instead.
2007-05-26 16:43:13.691 Cyberduck[22938] Unknown class `ch.cyberduck.ui.cocoa.delegate.BookmarkMenuDelegate' in nib file, using `NSObject' instead.
2007-05-26 16:43:13.691 Cyberduck[22938] Unknown class `ch.cyberduck.ui.cocoa.delegate.RendezvousMenuDelegate' in nib file, using `NSObject' instead.
2007-05-26 16:43:13.692 Cyberduck[22938] Could not connect the action donateMenuClicked: to target of class NSObject
2007-05-26 16:43:13.692 Cyberduck[22938] Could not connect the action licenseMenuClicked: to target of class NSObject
2007-05-26 16:43:13.692 Cyberduck[22938] Could not connect the action preferencesMenuClicked: to target of class NSObject
2007-05-26 16:43:13.692 Cyberduck[22938] Could not connect the action feedbackMenuClicked: to target of class NSObject
2007-05-26 16:43:13.692 Cyberduck[22938] Could not connect the action newDownloadMenuClicked: to target of class NSObject
2007-05-26 16:43:13.692 Cyberduck[22938] Could not connect the action newBrowserMenuClicked: to target of class NSObject
2007-05-26 16:43:13.692 Cyberduck[22938] Could not connect the action newBrowserMenuClicked: to target of class NSObject
2007-05-26 16:43:13.692 Cyberduck[22938] Could not connect the action downloadBookmarksFromDotMacClicked: to target of class NSObject
2007-05-26 16:43:13.692 Cyberduck[22938] Could not connect the action uploadBookmarksToDotMacClicked: to target of class NSObject
2007-05-26 16:43:13.692 Cyberduck[22938] Could not connect the action helpMenuClicked: to target of class NSObject
2007-05-26 16:43:13.693 Cyberduck[22938] Could not connect the action bugreportMenuClicked: to target of class NSObject
2007-05-26 16:43:13.693 Cyberduck[22938] Could not connect the action aboutMenuClicked: to target of class NSObject
2007-05-26 16:43:13.693 Cyberduck[22938] Could not connect the action historyMenuClicked: to target of class NSObject
2007-05-26 16:43:13.693 Cyberduck[22938] Could not connect the action downloadBookmarksFromDotMacClicked: to target of class NSObject
2007-05-26 16:43:13.693 Cyberduck[22938] Could not connect the action uploadBookmarksToDotMacClicked: to target of class NSObject

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Refer to #694. Have you manually changed symlinks in /JavaVM.framework/Versions/?

@cyberduck
Copy link
Collaborator Author

3196345 commented

Yes. And I know the speel about that being officially unsuportted by Apple.
However with the Kernel panics that can be created with ease in Java 1.5 by Apple there was little choice in the matter of going to Java 1.6.

Further, from my testing, changing the preference in the Java pref app is what affects the "launched" java applications. Changing the command line affects apps that are launched via "java -jar" etc. I confirmed this with my own app displaying its current Java version and was surprised to see it was reporting 1.5 until I updated the Java pref application in utilities. The Java launcher in OS X apparently uses it to decide what JVM.

CrushFTP works fine as a Java app, and from command line. Eclipse works fine as well too. Cyberduck is the only Java app not wokring fine.

lrwxr-xr-x 1 root wheel 5 May 6 17:06 1.6 -> 1.6.0
drwxr-xr-x 8 root wheel 272 May 6 17:06 1.6.0
drwxr-xr-x 6 root wheel 204 May 24 21:54 A
lrwxr-xr-x 1 root wheel 3 May 6 18:07 Current -> 1.6
lrwxr-xr-x 1 root wheel 3 May 6 18:05 CurrentJDK -> 1.6

Mac Mini Core Duo 10.4.9.

--Ben

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Adjust the $PATH variable in your bash shell (e.g. by editing ~/.bash_profile) to change the default Java Runtime for applications launched from the command line. Use the Java Preferences.app to change the Java version for applications packaged as a .app.

@cyberduck
Copy link
Collaborator Author

3196345 commented

That isn't my issue. I want to be using Java 1.6. I have to be to prevent Kernel panics due to bugs in Java 1.5.

Is Java 1.6 supported?

--Ben

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Yes, you can choose Java 1.6 in the Java Preferences.app and Cyberduck will run using Java 1.6.

@cyberduck
Copy link
Collaborator Author

3196345 commented

OK, so what is causing all the menu's to be grayed out and not working?

I wanted to use Cyberduck, but I definitely can't anymore at this point. It used to work just fine in the past.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Please read the other tickets I referenced. Revert the changes to the symlinks in JavaVM.framework and Cybeduck will work again as advertised.

@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants