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

launches but no new window, launched its .app( in show package contence) and this is what i got #12136

Closed
cyberduck opened this issue Feb 4, 2006 · 18 comments

Comments

@cyberduck
Copy link
Collaborator

anonymous created the issue

I recognize some of this stuff from coca and core data Developer info (CS student), I'm certian the developers will find this usefull

Welcome to Darwin!
adsl-70-130-135-107:~ user$ /Users/user/Desktop/Cyberduck.app/Contents/MacOS/Cyberduck; exit
2006-02-04 14:25:49.597 Cyberduck[790] Unknown class `ch.cyberduck.ui.cocoa.CDMainController' in nib file, using `NSObject' instead.
2006-02-04 14:25:49.599 Cyberduck[790] Could not connect the action donateMenuClicked: to target of class NSObject
2006-02-04 14:25:49.599 Cyberduck[790] Could not connect the action licenseMenuClicked: to target of class NSObject
2006-02-04 14:25:49.600 Cyberduck[790] Could not connect the action preferencesMenuClicked: to target of class NSObject
2006-02-04 14:25:49.600 Cyberduck[790] Could not connect the action feedbackMenuClicked: to target of class NSObject
2006-02-04 14:25:49.600 Cyberduck[790] Could not connect the action updateMenuClicked: to target of class NSObject
2006-02-04 14:25:49.601 Cyberduck[790] Could not connect the action newDownloadMenuClicked: to target of class NSObject
2006-02-04 14:25:49.601 Cyberduck[790] Could not connect the action newBrowserMenuClicked: to target of class NSObject
2006-02-04 14:25:49.602 Cyberduck[790] Could not connect the action newBrowserMenuClicked: to target of class NSObject
2006-02-04 14:25:49.602 Cyberduck[790] Could not connect the action downloadBookmarksFromDotMacClicked: to target of class NSObject
2006-02-04 14:25:49.603 Cyberduck[790] Could not connect the action uploadBookmarksToDotMacClicked: to target of class NSObject
2006-02-04 14:25:49.603 Cyberduck[790] Could not connect the action helpMenuClicked: to target of class NSObject
2006-02-04 14:25:49.604 Cyberduck[790] Could not connect the action bugreportMenuClicked: to target of class NSObject
2006-02-04 14:25:49.610 Cyberduck[790] Can't open input server /Library/InputManagers/Smart Crash Reports.bundle

If anyone has a solution or the application has been updated to resolve this matter pleas email me at mehemiah5@netscape.com,
as for my system it is < iMacG5 2Ghz 10.4, devtools unpacked >

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Check if you can launch the application from the mounted disk image.

@cyberduck
Copy link
Collaborator Author

9adae35 commented

Yeah - I have the same problem(s). Newly installed Cyberduck.

Does NOT work from Disk Image.

@cyberduck
Copy link
Collaborator Author

4981452 commented

I have exactly the same problem myself.
Mac Mini with 10.4.4 OS X.

@cyberduck
Copy link
Collaborator Author

561bfeb commented

Same problem with Cyberduck 2.5.4 on powerbook G4 1,33 GHz. Does not start at system disk.
All of a sudden. I think is has something to do with 10.4.3 update.

chris

@cyberduck
Copy link
Collaborator Author

84d66fe commented

This is still present.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Does it work when launching Cyberduck under a different user account?

@cyberduck
Copy link
Collaborator Author

84d66fe commented

Nope. Fails.

Launched from drive, this also behaves the same.

@cyberduck
Copy link
Collaborator Author

72ee495 commented

I have this one too, and it has been present for quite a while now. I haven't been able to open Cyberduck for who knows how long, and that bothers me, because I'm considering switching to it.

Here is my output from console.app:

2006-03-10 13:13:38.893 Cyberduck[5894] Unknown class ch.cyberduck.ui.cocoa.CDMainController' in nib file, using NSObject' instead.
2006-03-10 13:13:38.903 Cyberduck[5894] Could not connect the action donateMenuClicked: to target of class NSObject
2006-03-10 13:13:38.904 Cyberduck[5894] Could not connect the action licenseMenuClicked: to target of class NSObject
2006-03-10 13:13:38.904 Cyberduck[5894] Could not connect the action preferencesMenuClicked: to target of class NSObject
2006-03-10 13:13:38.904 Cyberduck[5894] Could not connect the action feedbackMenuClicked: to target of class NSObject
2006-03-10 13:13:38.904 Cyberduck[5894] Could not connect the action updateMenuClicked: to target of class NSObject
2006-03-10 13:13:38.904 Cyberduck[5894] Could not connect the action newDownloadMenuClicked: to target of class NSObject
2006-03-10 13:13:38.904 Cyberduck[5894] Could not connect the action newBrowserMenuClicked: to target of class NSObject
2006-03-10 13:13:38.905 Cyberduck[5894] Could not connect the action newBrowserMenuClicked: to target of class NSObject
2006-03-10 13:13:38.906 Cyberduck[5894] Could not connect the action downloadBookmarksFromDotMacClicked: to target of class NSObject
2006-03-10 13:13:38.907 Cyberduck[5894] Could not connect the action uploadBookmarksToDotMacClicked: to target of class NSObject
2006-03-10 13:13:38.907 Cyberduck[5894] Could not connect the action helpMenuClicked: to target of class NSObject
2006-03-10 13:13:38.908 Cyberduck[5894] Could not connect the action bugreportMenuClicked: to target of class NSObject

@cyberduck
Copy link
Collaborator Author

a97ad0b commented

I've just had the same problem, but in different circumstances (which may bring some light, hopefully).

I have 10.3.9 installed. I force installed java 1.5 from apple, using a similar approach as in
http://www.macosxhints.com/article.php?story=2005043002313964

(which is bad practice, I would'nt recommend this to anyone, since it apparently broke several java/cocoa apps).

After a few mistakes (which caused Cyberduck simlpy not to launch), I got the same result.

Switching back to 1.4.2 (by just modifying the symbolic link Current and CurrentJDK in /System/Library/Frameworks/JavaVM/Version) does'nt help. My guess is that java 1.5 somehow modifies the way java/cocoa apps work, in a more radical fashion that simply using a new vm.

Well, that's just a wild guess.

@cyberduck
Copy link
Collaborator Author

anonymous commented

I have the same problem with OSX 10.4.5, Cyberduck 2.5.5 (both newly installed !)

@cyberduck
Copy link
Collaborator Author

fa29416 commented

I have the same problem with OS X 10.4.5. and Cyberduck 2.5.5 also. Since I last successfully used Cyberduck, I upgrade to 10.4.5 and installed Java 1.5 (and modified the Current and CurrentJDK symbolic links as described above).

@cyberduck
Copy link
Collaborator Author

72ee495 commented

Installation of Java 1.5 seem to be the trouble here, since I have also done that prior to trying Cyberduck.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Installing Java 1.5 is no problem at all. Modifying symlinks in /System/Library/Frameworks/JavaVM.framework/ however will break Cocoa applications dependant from Java and possibly later OS upgrades. Use /Applications/Utilities/Java/J2SE\ 5.0/Java\ Preferences.app to modify the default Java version which allows you to modify the Java version Cyberduck uses. To change the default JDK for your shell refer to .bash_profile and 'man bash' if you are using the bash shell.

Anyone having the problem described without modifying symbolic links?

@cyberduck
Copy link
Collaborator Author

anonymous commented

I have solved the problem by doing :

  1. Verify that you have the following lines in /System/Library/Frameworks/JavaVM.framework/Versions :
drwxr-xr-x    6 root  wheel  204 Mar 13 23:52 A
lrwxr-xr-x    1 root  wheel    1 Nov 16 21:48 Current -> A
lrwxr-xr-x    1 root  wheel    5 Nov 16 21:50 CurrentJDK -> 1.5.0

If not, create it.

  1. Go in Applications -> Utilitaires -> Java -> J2SE5.0 -> Java Preferences -> General. Put 1.4.2 in "Utiliser la version :" and move J2SE 1.4.2 before J2SE 5.0 in the box in the middleof the window. Clic "Save".

  2. Repete 2. but in "Utiliser la version:" put J2SE 5.0 and move J2SE 5.0 before J2SE 1.4.2 in the box in the middle of the window. Clic "save".

  3. Run Cyberduck.

(Sorry for the french word, but my OSX is in french).

@cyberduck
Copy link
Collaborator Author

84d66fe commented

Confirming fix. Worksforme as well.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Also refer to e.g. (http://lists.apple.com/archives/java-dev/2006/Mar/msg00296.html)

@cyberduck
Copy link
Collaborator Author

anonymous commented

The Java update released today (Java 2 Standard Edition (J2SE) 5.0 Release 4) solved this issue on my computer.

@cyberduck
Copy link
Collaborator Author

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant