I’ve checked the Cursor GitHub issues and forums (assuming GitHub · Where software is built or similar) as of March 21, 2025, and didn’t find an exact match for this issue with the specific AppImage version and hardware. However, I recommend the team confirm if similar VAAPI or glibc compatibility issues have been reported.
The Cursor AppImage (Cursor-0.47.8-82ef0f61c01d079d1b7e5ab04d88499d5af500e3.deb.glibc2.25-x86_64.AppImage) crashes with a “trace trap (core dumped)” error on Arch Linux when run natively. Initial attempts revealed a VAAPI initialization failure under Wayland (libva error: /usr/lib/dri/iHD_drv_video.so init failed), which was resolved by switching to X11, where the i965_drv_video.so driver works for my older Intel GPU. However, the crash persists even with VAAPI functioning, suggesting a deeper compatibility issue, possibly related to glibc (AppImage targets 2.25, Arch uses a newer version). Running in a container (Ubuntu 16.04) to match glibc 2.25 fails due to FUSE setup issues.
how to reproduce the bug (if known)
-
Download the AppImage: Cursor-0.47.8-82ef0f61c01d079d1b7e5ab04d88499d5af500e3.deb.glibc2.25-x86_64.AppImage.
-
Set execute permissions: chmod +x ./Cursor-0.47.8-82ef0f61c01d079d1b7e5ab04d88499d5af500e3.deb.glibc2.25-x86_64.AppImage.
-
Run on Arch Linux with an Intel
-
On Wayland: ./Cursor-0.47.8-82ef0f61c01d079d1b7e5ab04d88499d5af500e3.deb.glibc2.25-x86_64.AppImage → Crashes with “trace trap” and VAAPI error.
-
On X11: Switch session to X11, verify VAAPI with vainfo, then run the AppImage → Still crashes with “trace trap” but no VAAPI error.
- (Optional) Run in a Podman container: podman run -it --rm -v $(pwd):/app -w /app -e DISPLAY=$DISPLAY -v /tmp/.X11-unix:/tmp/.X11-unix --device /dev/fuse ubuntu:16.04 bash, install libfuse2 and dependencies, then run → Fails with FUSE error.
Attach screenshots or recordings (e.g., .jpg, .png, .mp4)
- Terminal output on Wayland:
➜ ~ ./Cursor-0.47.8-82ef0f61c01d079d1b7e5ab04d88499d5af500e3.deb.glibc2.25-x86_64.AppImage --appimage-extract-and-run
libva error: /usr/lib/dri/iHD_drv_video.so init failed
[1] <pid> trace trap (core dumped)
- vainfo on Wayland:
Trying display: wayland
error: failed to resolve wl_drm_interface(): /usr/lib/libEGL_mesa.so.0: undefined symbol: wl_drm_interface
libva error: /usr/lib/dri/i965_drv_video.so init failed
vaInitialize failed with error code -1 (unknown libva error), exit
- vainfo on X11 (working):
Trying display: x11
vainfo: VA-API version: 1.22 (libva 2.22.0)
vainfo: Driver version: Intel i965 driver for Intel(R) Ironlake Mobile - 2.4.1
[Supported profiles: MPEG2Simple, H264Main, etc.]
- Terminal output on X11:
➜ ~ ./Cursor-0.47.8-82ef0f61c01d079d1b7e5ab04d88499d5af500e3.deb.glibc2.25-x86_64.AppImage
[1] <pid> trace trap (core dumped)
- Container output:
root@<container-id>:/app# ./Cursor-0.47.8-82ef0f61c01d079d1b7e5ab04d88499d5af500e3.deb.glibc2.25-x86_64.AppImage
fuse: device not found, try 'modprobe fuse' first
Cannot mount AppImage, please check your FUSE setup.
Tell us your operating system and your Cursor version
-
OS: Arch Linux (rolling release, as of March 21, 2025)
-
Cursor Version: Cursor-0.47.8-82ef0f61c01d079d1b7e5ab04d88499d5af500e3.deb.glibc2.25-x86_64.AppImage
-
Hardware: Intel Core Processor Integrated Graphics Controller (Ironlake Mobile), i915 kernel module
-
glibc: [Run ldd --version and insert, e.g., 2.39]
Tell us if the issue stops you from using Cursor
Yes, this issue completely prevents me from using Cursor. The AppImage crashes consistently on Arch Linux, and workarounds (X11 switch, container) haven’t succeeded yet due to VAAPI, glibc, or FUSE issues.