After upgrade can't start ghostty #8837
Replies: 6 comments 3 replies
-
|
Does anyone have any more details here? I see a few upvotes but otherwise I haven't really heard of any issues with launching Ghostty, and we're seeing hundreds of thousands of daily macOS update pings per day (update checks) so I think its working fine. We don't send any telemetry or user identifiable data with that so it's unclear how many are macOS 13. |
Beta Was this translation helpful? Give feedback.
-
|
If I can help in diagnosing further let me know how. For me ghostty is still unusable, worked perfectly before the update. I don't have any issues running other terminals iTerm, alacritty, Warp. |
Beta Was this translation helpful? Give feedback.
-
|
Just attempted an upgrade to the latest patch release 1.2.3 today and I am still having this same issue on MacOS 13.2.1. Attaching my crash report, which is pretty much the same as the one from @dixpac. I've attempted upgrading with Homebrew and also installing by downloading the DMG from the website. Same issue with starting the application in either case. |
Beta Was this translation helpful? Give feedback.
-
|
I downloaded ghostty for the first time today, don't have any previous installs of it - quits unexpectedly on startup on intel macOS 13 |
Beta Was this translation helpful? Give feedback.
-
|
I've resolved the issue by upgrading macOS version |
Beta Was this translation helpful? Give feedback.
-
|
Uhm its been once a day now every day it seems there is something with having multiple tabs i have around 12 tabs each with 2 panels, multiple npm (node processes) running and at least 4 or 5 claude sessions. It seems it reaches a point daily when it just dies |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Issue Description
Ghostty crashes after upgrade on macOS 13
Expected Behavior
I've just upgraded ghosty to latest version. But after upgrade terminal is not starting.
Tried to delete ghostty and install it from scratch again but still same issue
Actual Behavior
This is the crash report I get on my mac m1 13.2.1
Reproduction Steps
Ghostty Logs
No response
Ghostty Version
OS Version Information
macOS 13.2.1
(Linux only) Display Server
None
(Linux only) Desktop Environment/Window Manager
No response
Minimal Ghostty Configuration
Additional Relevant Configuration
No response
I acknowledge that:
```) on separate lines.Beta Was this translation helpful? Give feedback.
All reactions