-
-
Notifications
You must be signed in to change notification settings - Fork 296
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 opening Info window #4536
Comments
Replying to [4536 anonymous]:
Same here! Whenever I try to get info from a uploaded file, Cyberduck crashes :( |
Please report the localization you are using and attach the crash report and any output you can find in the |
I also experience this crash with the latest Cyberduck .3.5 (6066). Me too, both with plain FTP and TLS mode. This occurs with a Plesk hosting server, running ProFTPD 1.3.1. Crash report & screen shots enclosed. This FTP site is known to be a bit flakey - sometimes manual actions via FireFTP fail with obscure permission problems even when the owner logs in. Still, this should not lead to application crashes. If it helps, I can give you a temporary login to this Swiss hosting site (yoursite.ch). Unrelated topic but still curious - is it expected that Cyberduck has two help menus? |
Please send us a temporary login to feedback@cyberduck.ch. Thanks for helping us to sort out this issue. |
I also get crashes/beachball on Cmd-I or "Get Info" on files, with FTP-SSL. |
Okay, that was totally unhelpful of me. |
Replying to [comment:5 John Buehrer <john@…>]:
Not expected. I cannot see this issue here. |
Replying to [comment:5 John Buehrer <john@…>]:
Thanks for the login credentials. Unfortunately we can still not reproduce the issue. Can you send us additionally
|
Output in system.log shows there is a out of bounds issue in a control.
|
Try to get some information about folders. With cmd + i or Menu - Information cyberduck crashes / does not working (spinning beachball).
Try it on different FTP Servers.
Attachments
JDB_Cyberduck crash info.txt
(42.2 KiB)The text was updated successfully, but these errors were encountered: