Cursor 0.46.9-5 Crashes on Launch (Hyprland, Arch Linux, SIGTRAP)

Bug Reports
1

Bug Description

After updating to Cursor 0.46.9-5, the application immediately crashes on launch with a SIGTRAP (core dumped) error. The issue was not present in previous versions. This occurs on Wayland (Hyprland) with Arch Linux.

Steps to Reproduce

  1. Install Cursor from cursor-bin via yay or manually via .pkg.tar.zst.
  2. Run Cursor:

sh

CopyEdit

cursor
  1. Cursor crashes immediately with the following error:

scss

CopyEdit

[1] trace trap (core dumped) cursor
  1. Additional attempts with flags such as --no-sandbox, --disable-gpu, and XDG_SESSION_TYPE=x11 do not resolve the issue.
  2. coredumpctl gdb cursor confirms that the crash is happening deep within Cursor’s Electron runtime.
  3. journalctl -xe | grep cursor shows multiple SIGTRAP core dumps.
  4. Reinstalling Cursor and ensuring dependencies like fuse2, xdg-desktop-portal, and xdg-desktop-portal-hyprland are installed does not fix the issue.

Expected Behavior

Cursor should launch normally as it did in previous versions.

Additional Debugging Information

  • OS: Arch Linux
  • Window Manager: Hyprland (Wayland)
  • Cursor Version: 0.46.9-5
  • Error Logs:
    • coredumpctl output:

sql

CopyEdit

Process (cursor) dumped core with signal 5/TRAP
  • strace output (truncated):

csharp

CopyEdit

+++ killed by SIGTRAP (core dumped) +++
  • journalctl output (truncated):

sql

CopyEdit

Process (cursor) of user 1000 terminated abnormally with signal 5/TRAP

Is This Blocking Usage?

:prohibited: Yes – Cursor does not launch at all after this update.

Workarounds & Notes

  • Rolling back to a previous version might work, but I no longer have the old package to test.
  • Other Wayland users on Hyprland are experiencing similar crashes, suggesting a regression in the latest update.
  • This may be an Electron-related issue affecting Wayland environments.

Request

Please investigate whether 0.46.9-5 introduced a regression for Wayland users, especially those on Hyprland. Let me know if I can provide additional logs or debugging info.

2 Likes
2

I’m also having this issue on arch linux gnome (wayland)

3

I just downgraded to 0.45. I’ll try again with 0.46 or later (maybe).

4

It seems they reverted to 0.46.8. The aur package cursor-bin also has been rolled back. I just tried it and it launched now!

Version: 0.46.8
VSCode Version: 1.96.2
Commit: be4f0962469499f009005e66867c8402202ff0b0
Date: 2025-02-28T19:38:20.821Z
Electron: 32.2.6
Chromium: 128.0.6613.186
Node.js: 20.18.1
V8: 12.8.374.38-electron.0
OS: Linux x64 6.13.5-arch1-1
5

Interesting. I may give that a try. Thanks.

1 Like
6

Opening cursor with cursor . broke btw. See my aur comment

1 Like
7

This page also usually contains old versions: Downloads | Cursor - The AI Code Editor

1 Like
8

And the AUR version of 0.46.11-1 was a fail this morning. It did not work at all. I got the same errors in terminal and it never opened. I rolled back (again) to 0.45.14. I may try the appimage of 0.46.8 that @ardasevinc said worked and install it on the side to test.

9

Looks like all of this is about this glib2 issue
It was actually fixed by setting XDG_DATA_DIRS before launching cursor. See this aur comment

@flaturtha give it a try with the XDG_DATA_DIRS fix. I just tried with the latest 0.46 version on AUR and can verify it works

1 Like
10

I’m finally getting back to working in Cursor today so I’ll give this a try. I was having issues with general pacman updates this morning.

EDIT. I upgraded to 0.46.11-1 and ran with the XDG fix and it seems to be working well. Thanks!!

1 Like
11

enjoy!

12

Fixed in v0.47.9