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

Cyberduck Spotlight Importer not removed from memory on upgrade #2973

Closed
cyberduck opened this issue Feb 10, 2009 · 4 comments
Closed

Cyberduck Spotlight Importer not removed from memory on upgrade #2973

cyberduck opened this issue Feb 10, 2009 · 4 comments
Assignees
Labels
bug core thirdparty Issue caused by third party

Comments

@cyberduck
Copy link
Collaborator

06c0ee5 created the issue

Operation cannot be completed because Cyberduck Spotlight Importer is in use.

3.1.2.

@cyberduck
Copy link
Collaborator Author

bb777fc commented

Version 3.1.2. Same error as above when attempting to empty trash: "The operation cannot be completed because the item Cyberduck Spotlight Importer is in use."

@cyberduck
Copy link
Collaborator Author

bb777fc commented

This appears to be an artifact from upgrading. The Cyberduck Spotlight Importer remains in memory and as a result requires the user to logout/login in order to empty the trash. Either need scripting to kill the process in question or some definition of the process and a brief note to end-users explaining that the process {name} needs to be killed manually.

@cyberduck
Copy link
Collaborator Author

90cc08b commented

Encountered the same problem when upgrading to Cyberduck 3.2.1 on Mac OS X 10.5.7. Had to open the Activity Monitor and kill the process "mdworker" to empty the Trash.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

I expect OS X to fix this as part of the Spotlight architecture. It is not Cyberduck itself spawning that process and is therefore not responsible for killing it.

@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.
Labels
bug core thirdparty Issue caused by third party
Projects
None yet
Development

No branches or pull requests

2 participants