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.

Sign up for GitHub

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

Jump to bottom

Cyberduck moves file to trash #1927

Closed
cyberduck opened this issue Apr 10, 2008 · 5 comments
Closed

Cyberduck moves file to trash #1927

cyberduck opened this issue Apr 10, 2008 · 5 comments
Assignees
@dkocher
Labels
bug core worksforme
Milestone
3.0

Comments

@cyberduck
Copy link
Collaborator

8778256 created the issue

Hi, I am not sure if this is a bug or not, but it seems odd to me.

I just updated to the most recent version of Cyberduck and when I wanted to connect to one of my favorites (listed in the drawer) it asked me to transfer permissions for keychain or something like that. I clicked yes, and then it started connecting. But at the same time it moved a file to the trash with the name of the name of my favorite connection and ".duck" as the file extension.

I restarted Cyberduck and connected to the server again, and it moved that same file to the trash again, even though I had already emptied the trash before. Is this known to you? Is it normal?

thanks for making cyberduck,

  • temhawk :)
@cyberduck
Copy link
Collaborator Author

anonymous commented

I'm noticing this under 2.8.5 too. When connecting to the bookmark, the .duck bookmark file is copied to the trash. After connecting, every directory that I navigate to is then copied to the trash (just the directory, not the files within), and every file that I open to edit is copied to the trash.

These files are only being copied to the trash and at no point are they ever removed from the server. The bookmark itself, despite being initially copied to the trash, never leaves Cyberduck's drawer.

This happened after I updated to Cyberduck 2.8.5 from 2.8.4 using the built-in updater.

If you don't mind, I'd like to bump the priority and severity of this bug up to at least "normal", since the action of copying directories to the trash may alarm new users.

Thanks for continuing to develop Cyberduck! I'm really looking looking forward to version 3!

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Replying to [comment:1 anonymous]:

Edited files are always moved to the Trash after the editor is closed. We don't delete them immediately to prevent data loss if the upload to the server has failed. The file can then still be recovered.

Temporary bookmarks from the history are no longer moved to the Trash in 3.0.

@cyberduck
Copy link
Collaborator Author

8778256 commented

dkocher, you mean Cyberduck 3.0 ?

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Replying to [comment:3 temhawk@hotmail.com]:

dkocher, you mean Cyberduck 3.0 ?

Right.

@cyberduck
Copy link
Collaborator Author

moskovskii intim dosug commented

Hi!
http://dosugplace.awardspace.biz moskovskie individualki
http://trac.miranda.im/mainrepo/ticket/21538 intim dosug moskvy
http://trac.etentec.com/pm/ticket/126 moskovskie shalavy
http://www.dontstuffbeansupyournose.com/trac/ticket/237 moskovskii intim dosug
online.

@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.
Assignees

@dkocher dkocher

Labels
bug core worksforme
Projects
None yet
Milestone
3.0
Development

No branches or pull requests
2 participants
@dkocher @cyberduck