Kitty: Doesn't launch on OSX Catalina
I think it's related to that notarization policy they just introduced…
evantravers
All 13 comments
evantravers
on 10 Oct 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.
Luflosi
on 10 Oct 2019
There is a fix:
- Open "Finder"
- Go to "Applications" folder
- Right click on "Kitty"
- 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.
ddnomad
on 10 Oct 2019
That is the workaround I was talking about. Thank you for laying out the steps more clearly than I did.
Luflosi
on 10 Oct 2019
@kovidgoyal I think we should describe this process in detail in the installation instructions. I can make a couple screenshots if you like.
Luflosi
on 10 Oct 2019
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.
kovidgoyal
on 10 Oct 2019
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:
rahulkp220
on 21 Oct 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 https://github.com/kovidgoyal/kitty/issues/2040#issuecomment-540631916 for GateKeeper.
Luflosi
on 21 Oct 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.
strogonoff
on 26 Dec 2019
Try opening the Console App and search for kitty. Maybe there are some helpful error messages.
Luflosi
on 26 Dec 2019
For me it failed from .app and via an Automator script (the latter is my regular way, not sure if that’s equivalent to launching Kitty from shell)
On 27 Dec 2019, at 2:42 PM, Ian Mackay notifications@github.com wrote:

Launching from the .app is broken for me with newest version - launching via terminal works fine.Potentially relevant console messages:
Timed out waiting for shell to quit while reading shell environment
&Traceback (most recent call last):
File "kitty/main.py", line 347, in main
File "kitty/main.py", line 336, in _main
File "kitty/main.py", line 270, in setup_environment
File "kitty/main.py", line 245, in read_shell_environment
AttributeError: 'function' object has no attribute 'ans'
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.
strogonoff
on 27 Dec 2019
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!
immackay
on 27 Dec 2019
As far as I know, Automater uses
opento 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!
strogonoff
on 28 Dec 2019
Related issues
atomsymbol
·
3Comments
crocket
·
4Comments
drandreaskrueger
·
4Comments
hujianxin
·
3Comments
wavexx
·
3Comments
Most helpful comment
There is a fix:
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.