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 Tries To Use iTerm For Default Terminal and Fails #11168

Closed
cyberduck opened this issue Sep 11, 2020 · 1 comment
Closed

Cyberduck Tries To Use iTerm For Default Terminal and Fails #11168

cyberduck opened this issue Sep 11, 2020 · 1 comment

Comments

@cyberduck
Copy link
Collaborator

@cyberduck cyberduck commented Sep 11, 2020

cd4881b created the issue

I recently installed iTerm, but to my knowledge, have not made it the default Terminal of my Mac. When I use Go > Open in Terminal, Cyberduck tries to use iTerm as the default terminal. However, it fails with the error message:

Access Denied

Failure running script in iTerm2. Expected “,” but found class name. Please verify disk permissions.

I found this ticket: #2987

Which details how to reset the defaults with the following commands:

defaults delete ch.sudo.cyberduck terminal.bundle.identifier
defaults delete ch.sudo.cyberduck terminal.command

But running either of these commands shows the following message:

Defaults have not been changed.

  1. How can I set Cyberduck to use the standard Mac Terminal?
  2. If I later ended up wanting to use iTerm, what would I need to do to get it to work?
@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Oct 10, 2020

@dkocher commented

Please change the default application for {{.command}} files in Finder to Terminal.app to revert.

@cyberduck cyberduck closed this Oct 10, 2020
@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 27, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant