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

Crash in CDMainApplication type]: selector not recognized #1601

Closed
cyberduck opened this issue Jan 15, 2008 · 11 comments
Closed

Crash in CDMainApplication type]: selector not recognized #1601

cyberduck opened this issue Jan 15, 2008 · 11 comments
Assignees
Milestone

Comments

@cyberduck
Copy link
Collaborator

eos292 created the issue

I clicked "install" on 2.8.3. It crashed and would not reopen. I trashed it and reinstalled 2.8.2 which opens and works correctly.

@cyberduck
Copy link
Collaborator Author

7169748 commented

To add to this report, as I see the same thing:

PPC G4, OS X 10.4.11, Cyberduck 2.8.3

The program starts, but without any windows opening. Any attempt to open any window (Preferences, New Download, New Browser) via the menu or keyboard shortcuts does not perform any action.

Right clicking on the dock item gives the "program is not responding" menu.

Checked the nightly build: same thing.

Changing severity of this report to "blocker", as the program cannot be used at all in that version.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Can you find any related output in the console.log (/Applications/Utilities/Console.app)?

@cyberduck
Copy link
Collaborator Author

7169748 commented

Indeed, there are:

-Starting the app*

2008-01-22 17:42:07.055 Cyberduck[13562] *** -[ch/cyberduck/ui/cocoa/CDMainApplication type]: selector not recognized [self = 0x33b470]
2008-01-22 17:42:07.056 Cyberduck[13562] *** -[ch/cyberduck/ui/cocoa/CDMainApplication type]: selector not recognized [self = 0x33b470]

-Opening Preferences via the menu*

2008-01-22 17:42:41.257 Cyberduck[13562] *** -[NSMenuItem type]: selector not recognized [self = 0x34f4c0]
2008-01-22 17:42:41.357 Cyberduck[13562] *** -[NSMenuItem type]: selector not recognized [self = 0x34f4c0]

-Opening Preferences via keyboard shortcut*

2008-01-22 17:43:39.044 Cyberduck[13562] *** -[NSMenu type]: selector not recognized [self = 0x352f40]
2008-01-22 17:43:39.044 Cyberduck[13562] *** -[NSMenu type]: selector not recognized [self = 0x352f40]
2008-01-22 17:43:39.044 Cyberduck[13562] *** -[NSMenu type]: selector not recognized [self = 0x353530]
2008-01-22 17:43:39.045 Cyberduck[13562] *** -[NSMenu type]: selector not recognized [self = 0x353530]
2008-01-22 17:43:39.045 Cyberduck[13562] *** -[NSMenu type]: selector not recognized [self = 0x3536c0]
2008-01-22 17:43:39.045 Cyberduck[13562] *** -[NSMenu type]: selector not recognized [self = 0x3536c0]
2008-01-22 17:43:39.045 Cyberduck[13562] *** -[NSMenu type]: selector not recognized [self = 0x3504a0]
2008-01-22 17:43:39.046 Cyberduck[13562] *** -[NSMenu type]: selector not recognized [self = 0x3504a0]
2008-01-22 17:43:39.063 Cyberduck[13562] *** -[NSMenuItem type]: selector not recognized [self = 0x34f4c0]
2008-01-22 17:43:39.150 Cyberduck[13562] NSInvalidArgumentException: *** -[NSMenuItem type]: selector not recognized [self = 0x34f4c0]
Stack Trace:
NSInvalidArgumentException: *** -[NSMenuItem type]: selector not recognized [self = 0x34f4c0]
	at com.apple.cocoa.application.NSApplication.sendEvent(Native Method)
	at ch.cyberduck.ui.cocoa.CDMainApplication.sendEvent(CDMainApplication.java:64)

-Closing the app via the menu*

2008-01-22 17:44:27.115 Cyberduck[13562] *** -[ch/cyberduck/ui/cocoa/CDMainApplication type]: selector not recognized [self = 0x33b470]
2008-01-22 17:44:27.115 Cyberduck[13562] *** -[ch/cyberduck/ui/cocoa/CDMainApplication type]: selector not recognized [self = 0x33b470]

Hope this helps.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

I have no idea. Can you try the latest nightly build from (http://update.cyberduck.ch/nightly).

@cyberduck
Copy link
Collaborator Author

7169748 commented

The latest nightly shows the same problem. I tried the other versions in the nightly directory and found that [3369] works, and the next one, [3377], does not work anymore. If you could provide me with a built of [3376], I could test if the big changes in [3377] cause the problems.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Now this looks related to #1810. Have you set Java 6 as the default runtime?

@cyberduck
Copy link
Collaborator Author

7169748 commented

I don't have Java 6 installed . The Java Preferences application ("Java-Einstellungen") shows J2SE 5.0 selected. /System/Library/Frameworks/JavaVM.framework/Versions shows

lrwxr-xr-x   1 root  wheel    5 14 Dez 14:13 1.3 -> 1.3.1
drwxr-xr-x   8 root  wheel  272  4 Apr  2006 1.3.1
lrwxr-xr-x   1 root  wheel    5 14 Dez 14:13 1.4 -> 1.4.2
drwxr-xr-x   8 root  wheel  272  4 Apr  2006 1.4.2
lrwxr-xr-x   1 root  wheel    5 14 Dez 14:14 1.5 -> 1.5.0
drwxr-xr-x   9 root  wheel  306 29 Nov 17:15 1.5.0
drwxr-xr-x   6 root  wheel  204 19 Mär 15:06 A
lrwxr-xr-x   1 root  wheel    1 14 Dez 14:14 Current -> A
lrwxr-xr-x   1 root  wheel    3 14 Dez 14:13 CurrentJDK -> 1.5

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Replying to [comment:8 martin]:

I don't have Java 6 installed . The Java Preferences application ("Java-Einstellungen") shows J2SE 5.0 selected. /System/Library/Frameworks/JavaVM.framework/Versions shows

Maybe you have installed WindowDragon? Refer to #1882.

@cyberduck
Copy link
Collaborator Author

jordan_brough commented

I had the same issue and removing WindowDragon has finally fixed it for me. Thank you.

@cyberduck
Copy link
Collaborator Author

7169748 commented

I can confirm, that putting Cyberduck on the exclude list fixes this problem.

Damn interactions between software, tough to figure out. I can see why many software authors dislike Application Enhancer. WindowDragon is so damn useful though...

@cyberduck
Copy link
Collaborator Author

7169748 commented

I opened a ticket on the WindowDragon SourceForge bug tracker.

@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