Cursor 3.0.4 Linux The window terminated unexpectedly

[hushino]

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

when open cursor 3 in Linux Cachyos kde, it crash with the message
The window terminated unexpectedly (reason: 'crashed, code: ‘139’)
options: Don’t restore editors
Close, Reopen
It’s unusable for me now

Steps to Reproduce

paru -S cursor-bin --rebuild --cleanafter

Screenshots / Screen Recordings

Operating System

Linux

Version Information

version 3.0.4

Does this stop you from using Cursor

Yes - Cursor is unusable

[tyruke]

I am also on CachyOS KDE, and updated Cursor this morning, and got the exact same issue. It’s also unusable for me. I even tried downloading the 3.0 app image and the 2.6 app image instead of using the binary from the AUR, and both of the app images wouldn’t even launch at all. The one from the AUR would at least launch with “The window terminated unexpectedly” error.

[eli.wavv (Eli Smith)]

I am getting the same thing on Arch linux, for some very odd and suspicious reason though when I launch Cursor with the verbose flag(cursor –-verbose) , Cursor actually launches totally fine!

It’s almost as if it behaves properly when it knows its being watched…

[Moiz]

Issue across Arch Linux it seems

[deanrie]

Hey, this is a known issue with Cursor 3.0.4 on Linux. Multiple users on different distros like Arch, CachyOS, and Fedora hit the same SIGSEGV code 139.

As a temporary workaround, run it with the --verbose flag:

cursor --verbose

Like @eli.wavv mentioned in this thread, Cursor starts fine with that flag. It looks like a race condition during sandbox or zygote process init.

Let me know if the workaround doesn’t help.