Cursor AppImage updater crashes with SIGSEGV while updating to 3.0.4 on Linux

Support Bug Reports
, ,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Cursor AppImage updater crashes with SIGSEGV while updating to 3.0.4 on Linux

Steps to Reproduce

  1. Start with Cursor installed as an AppImage on Linux. Note: I use Gear Lever to manage AppImages, I don’t know if that is part of the problem here
  2. Let Cursor attempt to self-update to Cursor 3.0.4, or run the bundled updater directly:
    squashfs-root/usr/share/cursor/resources/appimageupdatetool.AppImage
    -u ‘zsync|https://downloads.cursor.com/production/63715ffc1807793ce209e935e5c3ab9b79fddc85/linux/x64/Cursor-3.0.4-
    x86_64.AppImage.zsync’
    -O /home/ebendler/AppImages/cursor.appimage
  3. Observe updater output and crash.

Expected Behavior

Cursor should check for updates and replace the AppImage successfully, or fail with a normal error message. It should not segfault.

Operating System

Linux

Version Information

System Information:
OS: Fedora 44 x86_64
Install type: Cursor AppImage
Target version: Cursor 3.0.4 x86_64 AppImage

Version Information:
The crash happened during update from an older AppImage to Cursor 3.0.4.
The bundled updater reports:
zsync2 version 2.0.0-alpha-1 (commit 362e637), build 223, built 2024-12-25 15:11:37 UTC

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

Other Notes

If you could add the proper metadata (I think it’s just a static link to latest version) for Gear Lever to update the app as well, that would be helpful. GitHub - mijorus/gearlever: Manage AppImages with ease 📦 · GitHub

5

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

6

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Cursor 3.0 crashing after opening (code 139).

Steps to Reproduce

Open Cursor on Arch Linux

Expected Behavior

Its supposed to open without crashing

Screenshots / Screen Recordings

Operating System

Linux

Version Information

Cursor 3.0.6

Does this stop you from using Cursor

Yes - Cursor is unusable

7

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

Screenshot_20260402_195720.png
Screenshot_20260402_195720.png1281×807 24.3 KB

Operating System

Linux

Version Information

version 3.0.4

Does this stop you from using Cursor

Yes - Cursor is unusable

10

Hi there,

This is now fixed. Update to Cursor 3.0.9 (or later) and the crash should be resolved.

If you’re still on 3.0.4, you can either:

  • Wait for the auto-updater to pick up 3.0.9, or

  • Download the latest AppImage from cursor.com/download

Let us know if the issue persists after updating.

11

As expected, 3.0.4 still crashed in the appimage updater. I manually loaded 3.0.9 and will let you know what happens on the next update.