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

Doesn't launch on OSX Catalina #2040

Closed
evantravers opened this issue Oct 10, 2019 · 13 comments
Closed

Doesn't launch on OSX Catalina #2040

evantravers opened this issue Oct 10, 2019 · 13 comments

Comments

@evantravers
Copy link

I think it's related to that notarization policy they just introduced…

@evantravers
Copy link
Author

@Luflosi
Copy link
Contributor

Luflosi commented Oct 10, 2019

As far as I'm aware notarizing an app requires an Apple developer account which costs 100$ every year. IMO this is bullshit. Why would any developer of open source software give money to Apple for the privilege of getting an app scanned for malware by Apple when the developer doesn't get any money from publishing the app? I hate Apple for this nonsense. Thankfully the workaround with right-clicking the app and clicking open still works. Let's hope Apple doesn't prevent that at some point as well.

@ddnomad
Copy link

ddnomad commented Oct 10, 2019

There is a fix:

  1. Open "Finder"
  2. Go to "Applications" folder
  3. Right click on "Kitty"
  4. Choose "Open"

You will see a similar "pay Apple tax" pop-up but this time it will has the third "Open" option. Click on that option. Nothing would happen. Then start Kitty again as you usually do. It should fix the issue and the application will start properly.

Hope that helps.

@Luflosi
Copy link
Contributor

Luflosi commented Oct 10, 2019

That is the workaround I was talking about. Thank you for laying out the steps more clearly than I did.

@Luflosi
Copy link
Contributor

Luflosi commented Oct 10, 2019

@kovidgoyal I think we should describe this process in detail in the installation instructions. I can make a couple screenshots if you like.

@kovidgoyal
Copy link
Owner

As long as you dont download the dmg via safari and manually install it,
gatekeeper should not kick in. Use the installation script from
https://sw.kovidgoyal.net/kitty/binary.html and it should bypass
notarization.

And I totally agree that notarization and paying Apple for the privilege
of distributing free applications that make their platform better is
total bullshit.

That said, I already notarize calibre, which needs it since it is used by
less technically inclined people so cant point them to
workarounds/scripts. So maybe at some point I will add notarization to
kitty as well.

@rahulkp220
Copy link

Having issues downloading on MacOS Catalina.

curl -L https://sw.kovidgoyal.net/kitty/installer.sh | sh /dev/stdin

  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  8606  100  8606    0     0  10664      0 --:--:-- --:--:-- --:--:-- 10664
Using python executable: /usr/local/bin/python3
Checking for latest release on GitHub...
Failed to contact https://api.github.com/repos/kovidgoyal/kitty/releases/latest with error: <urlopen error [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1056)>```

@Luflosi
Copy link
Contributor

Luflosi commented Oct 21, 2019

Very similar to #1485. Either wait until GitHub fixes it or try downloading the .dmg manually using the browser and using the workaround from #2040 (comment) for GateKeeper.

@strogonoff
Copy link

strogonoff commented Dec 26, 2019

Kitty suddenly won’t launch no matter what. Also Catalina. Worked perfectly up until today. Troubleshooting steps attempted: rebooted, reinstalled, opened with right-click and silenced Gatekeeper. App icon will jump a few times and disappear. Process kitty does not show up.

@Luflosi
Copy link
Contributor

Luflosi commented Dec 26, 2019

Try opening the Console App and search for kitty. Maybe there are some helpful error messages.

@strogonoff
Copy link

strogonoff commented Dec 27, 2019 via email

@immackay
Copy link

As far as I know, Automater uses open to launch applications, which would result in the same behavior as opening the .app.

I created a relevant issue for this in #2232 - already fixed in master!

@strogonoff
Copy link

As far as I know, Automater uses open to launch applications, which would result in the same behavior as opening the .app.

I created a relevant issue for this in #2232 - already fixed in master!

You’re entirely right, and it’s great to see it fixed so fast!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants