SIGSEGV in zygote (--type=zygote) on Fedora 43 / kernel 6.19 — Cursor 3.0.4

[tentakle]

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Title: SIGSEGV in --type=zygote on Fedora 43 / kernel 6.19, Cursor 3.0.4

OS: Fedora 43, kernel 6.19.10-200.fc43.x86_64, SELinux Enforcing
Cursor: 3.0.4 (RPM), Electron 39.8.1, Chromium 142.0.7444.265, VSCode 1.105.1
Commit: 63715ffc1807793ce209e935e5c3ab9b79fddc80

Symptom: window crashes immediately with code 139 (SIGSEGV).
Crashes happen in --type=zygote (PID 320367, confirmed via coredumpctl).
–verbose as a flag stabilizes the launch (timing workaround).
–disable-chromium-sandbox causes a hang (breaks zygote IPC protocol).
chrome-sandbox is setuid root, user namespaces are enabled (max 63265).
No SELinux AVC denials found.

Coredump: /var/lib/systemd/coredump/core.cursor.1000…320367…zst (present)
Stack thread 1: #0-#1 in cursor binary, #2 __restore_rt (libc) — no external library frame.

Previous version 2.6.22 worked without issues.

Steps to Reproduce

Run cursor

Operating System

Linux

Version Information

Version: 3.0.4
VSCode Version: 1.105.1
Commit: 63715ffc1807793ce209e935e5c3ab9b79fddc80
Date: 2026-04-02T09:36:23.265Z
Layout: editor
Build Type: Stable
Release Track: Default
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
OS: Linux x64 6.19.10-200.fc43.x86_64

Does this stop you from using Cursor

Yes - Cursor is unusable

[deanrie]

Hey, thanks for the detailed report. The coredump and the info about the --verbose workaround are really helpful.

This is a known issue. Cursor 3.0.x is crashing with SIGSEGV code 139 on Linux for several users across different distros like Arch, CachyOS, and Fedora. It looks like a regression after an Electron or Chromium update.

As a temporary workaround, you can launch it with the --verbose flag, like you already found:

cursor --verbose

This makes startup stable, likely due to a race condition during sandbox or zygote initialization.

I’ve passed this to the team along with your report and info from other users. There’s no ETA yet, but your detailed analysis with the coredump, sandbox info, and the --verbose behavior helps with prioritization.

Let me know if --verbose stops working or if anything new shows up.