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

Does not have permission to write to directory/disk image? #1979

Closed
cyberduck opened this issue Apr 23, 2008 · 1 comment
Closed

Does not have permission to write to directory/disk image? #1979

cyberduck opened this issue Apr 23, 2008 · 1 comment

Comments

@cyberduck
Copy link
Collaborator

anonymous created the issue

I've written to you before about getting an error message when trying to Install the recent update to 3611: Cyberduck does not have permission to write to his application's directory. It was suggested that I repair disk permissions, which I've done with no effect.

The error dialog asks if I'm working from a "disk image." I'm not at all sure how Mac disk images work, even after a year owning this MacBook. But I do notice the image of a drive appearing on my desktop every time I launch Cyberduck. I don't know what this means or how it works; it's the only program that does this. This "disk image" is not in my Finder window.. but if this does fit the condition mentioned in the dialog error message, it's pretty frustrating that if indeed, it's correct that I'm "working from a disk image," you offer no further explanation or solution. So, let's say I am "working from a disk image." Now what?

Thanx...

@cyberduck
Copy link
Collaborator Author

@dkocher commented

But I do notice the image of a drive appearing on my desktop every time I launch Cyberduck.

Double click that drive and move the Cyberduck Application to your Applications folder on your hard disk. Then eject the disk image, trash the Cyberduck Icon you have clicked before (probably a alias to the application on the disk image) and then launch Cyberduck from your Applications folder instead.

@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