getcursor
SIGSEGV
neofetch:
OS: NixOS 23.11.20231003.81e8f48 (Tapir) x86_64
Kernel: 6.1.55
Uptime: 5 days, 13 hours, 43 mins
Packages: 681 (nix-system), 1175 (nix-user), 2 (nix-default)
Resolution: 1366x768
DE: sway (Wayland)
Theme: Catppuccin-Mocha-Standard-Blue-dark [GTK2/3]
Icons: Fluent-dark [GTK2/3]
Terminal: tmux
CPU: Intel i5-4200U (4) @ 2.600GHz
GPU: Intel ThinkPad X240
Memory: 6247MiB / 7836MiB
~/Downloads $ chmod +x cursor-0.12.3-build-231008c5ursm0oj.AppImage
~/Downloads $ ./cursor-0.12.3-build-231008c5ursm0oj.AppImage
fish: Job 1, './cursor-0.12.3-build-231008c5u…' terminated by signal SIGSEGV (Address boundary error)
The latest release of cursor seems to not segfault when you try launching it in a pure wayland environment, instead it refuses to execute for me at all now and only works under Xwayland enabled environments. Even though this seems to not be an issue for regular vscode or electron in general, the cursor dev seemed to have disabled Ozone/Wayland support for some reason.
I just created a Nix flake for Cursor.
https://github.com/coder/cursor-arm
Try it out!
I just created a Nix flake for Cursor.
Try it out!
That has nothing to do with this issue here I suppose?
But thanks for bringing up that this was still open. The most recent version of cursor seems to have fixed this issue for me. So maybe we can close it?