`Application Not Responding` workaround - Arch Linux + Hyprland

Guides
1

If you are using Arch or an Arch based distro like EndeavourOS, Athena, etc… + Hyprland, then you have likely started having crashes with cursor over the last month or so. I am not sure which update caused what, Hyprland, Arch, Cursor. BUT, one of the recent updates, has started making an otherwise stable setup unable to launch and run consistently.

Here are some of the ways “I”, have used to run Cursor:

note: I don’t have a clue what type of setup you have, or dotfiles, this works for me, hopefully it get’s you running again. Adjust as needed for your specific configs.

  1. if you just want it to run today, then clear cache and it’ll run
rm -rf ~/.config/Cursor/Code\ Cache ~/.config/Cursor/CachedData

This will likely only work for a day or so, before you have to re-run it. I have used it so that I can get it to run and troubleshoot, it is “Safe” but, you should know what the command does before trusting me lol.

  1. create an x11 wrapper, and point your menu and terminal at it
mkdir -p ~/bin

cat > ~/bin/cursor-x11-nogpu <<'EOF'
#!/usr/bin/env bash
# Cursor → X11 fallback for Arch + Hyprland

# make Cursor think it's on X11, not Wayland
unset WAYLAND_DISPLAY
export XDG_SESSION_TYPE=x11

# Override global Wayland hints just for this process
export ELECTRON_ENABLE_WAYLAND=0
export ELECTRON_OZONE_PLATFORM_HINT=x11
export OZONE_PLATFORM=x11

# Launch the AppImage (no GPU for stability)
exec /home/[YOUR_USER_HERE]/Applications/cursor.AppImage --disable-gpu "$@"
EOF

chmod +x ~/bin/cursor-x11-nogpu


nano ~/.local/share/applications/cursor.desktop

[Desktop Entry]
Name=Cursor
Comment=AI code editor
TryExec=/home/[YOUR_USER_HERE]/bin/cursor-x11-nogpu
Exec=/home/[YOUR_USER_HERE]/bin/cursor-x11-nogpu %U
Icon=cursor
Type=Application
Categories=Development;IDE;TextEditor;
StartupWMClass=Cursor
MimeType=text/plain;text/markdown;application/json;text/x-python;text/x-shellscript;
Terminal=false
NoDisplay=false

The refresh it

update-desktop-database ~/.local/share/applications 2>/dev/null || true

I also have the following items set for testing cursor builds + wayland

nano ~/bin/cursor-wayland

#!/usr/bin/env bash
export ELECTRON_ENABLE_WAYLAND=1
export OZONE_PLATFORM=wayland
exec /home/[YOUR_USER_HERE]/Applications/cursor.AppImage --disable-gpu “$@”

and cursor-wayland.desktop:

[Desktop Entry]
Name=Cursor (Wayland)
Comment=AI code editor
Exec=/home/[YOUR_USER_HERE]/bin/cursor-wayland %U
Terminal=false
Type=Application
Categories=Development;IDE;
Icon=cursor
StartupWMClass=Cursor

I had a symlink for cli, you may too. Here’s what I ran and changed to confirm:

ls -l ~/.local/bin/cursor
# → symlink → /home/[YOUR_USER_HERE]/Applications/cursor.AppImage


rm ~/.local/bin/cursor

cat > ~/.local/bin/cursor <<'EOF'
#!/usr/bin/env bash
exec /home/[YOUR_USER_HERE]/bin/cursor-x11-nogpu "$@"
EOF

chmod +x ~/.local/bin/cursor

Just know:

  1. Default Cursor → X11 wrapper
  2. Cursor (Wayland) → manually selectable if you ever want to test newer Cursor builds on Wayland again
  3. CLI cursor and the app menu use the same X11-stable path

Hope this helps.

Cheers,