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

Empty transfer window list #7980

Closed
cyberduck opened this issue May 28, 2014 · 11 comments
Closed

Empty transfer window list #7980

cyberduck opened this issue May 28, 2014 · 11 comments

Comments

@cyberduck
Copy link
Collaborator

49c3d88 created the issue

Hello,
After my problem, mentioned in ticket #7978, was solved (thanks for that), and I upgraded to version 4.5 (14665), the list of transfers has become empty (also previous transfers shown in 4.4 have now disappeared) and no new transfers are being added. I just see an empty list.

Regards
Huib J. Plankeel


Attachments

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Please add the file cyberduck.log in the application support directory.

@cyberduck
Copy link
Collaborator Author

49c3d88 commented

Hello and sorry.
Attachment seems added, but not my message, so again.
I searched my whole harddisk for cyberduck.log but found nothing.
Sreenprint gives all searchresults for cyberduck.

Regards,
Huib J. Plankeel

@cyberduck
Copy link
Collaborator Author

49c3d88 commented

Hello,
Might be relevant that I placed the transfer button on the toolbar.

Regards
Huib J. Plankeel

@cyberduck
Copy link
Collaborator Author

49c3d88 commented

Hello. I just removed the transfer button from the toolbar, but that had no effect.

Regards,
Huib J. Plankeel

@cyberduck
Copy link
Collaborator Author

@dkocher commented

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

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Replying to [comment:4 plankeel]:

I searched my whole harddisk for cyberduck.log but found nothing.

Sorry, I was thinking you are running on Windows.

@cyberduck
Copy link
Collaborator Author

49c3d88 commented

Hello Mr Kocher,

I looked also in the console messages, but found nothing related to cyberduck.
But I might have done something wrong in my ignorance in handling things like this.
I downloaded I think 4.5 (14665) (that's in the about cyberduck) and you talk about 4.4.5 ?
Did I download a wrong file?

Regards
Huib J. Plankeel

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Replying to [comment:9 plankeel]:

Hello Mr Kocher,

I looked also in the console messages, but found nothing related to cyberduck.
But I might have done something wrong in my ignorance in handling things like this.
I downloaded I think 4.5 (14665) (that's in the about cyberduck) and you talk about 4.4.5 ?
Did I download a wrong file?

Regards
Huib J. Plankeel

That is fine. The snapshot builds are versioned as 4.5.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Can you post a screenshot of the Transfers window.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Please make sure you have not set to use the browser connection for file transfers. Documentation.

@cyberduck
Copy link
Collaborator Author

49c3d88 commented

Hello Mr Kocher,
I changed use browser connection to open new connection, and then a transfer (17.32 hours) was recorded.
I changed it back to use browser connection, and a new transfer (17.34 hours) was not recorded. So that seems to be have been the problem.

Strange thing though, that I never (as far as I remember) changed that setting before, and that the earlier version of cyberduck filled the transfer window. It just took my attention that after the upgrade there were no more transfers visible in that window. I would not have noticed otherwise, as I don't have much experience with this program.
Also the reason that I don't like introducing changes I don't understand.

Attached are two screen shots, one at 17.21 hours, before making the change, and one at 17.42 hours, after changing things back.

Anyway, I know now what to do.
Thank you.
Huib J. Plankeel

@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

1 participant