Where does the bug appear (feature/product)?
Cursor IDE
Describe the Bug
Updating to Cursor 2.4.21 on Linux with AppArmor enabled causes Remote SSH to hang at “Opening Remote” and Remote SSH Settings to show “No Settings Found”. This is caused by a rename of the sandbox helper binary that breaks existing AppArmor profiles.
Steps to Reproduce
Install an older Cursor Linux version that required AppArmor workarounds
Have a cursor_sandbox AppArmor profile loaded
Update to Cursor 2.4.21
Launch Cursor
Attempt a Remote SSH connection
Results:
Remote SSH hangs indefinitely at “Opening Remote”
Remote SSH Settings shows “No Settings Found”
No actionable error surfaced in the UI
Expected Behavior
Extension should connect to remote system and allow extension configuration.
Operating System
Linux
Version Information
Cursor Version: 2.4.21
VSCode Version: 1.105.1
Commit: dc8361355d709f306d5159635a677a571b277bc0
Date: 2026-01-22T16:57:59.675Z
Build Type: Stable
Release Track: Default
Electron: 39.2.7
Chromium: 142.0.7444.235
Node.js: 22.21.1
V8: 14.2.231.21-electron.0
OS: Linux x64 6.17.0-8-generic (Ubuntu)
Additional Information
Ubuntu 24.10 with Cursor debian package.
The update renamed the sandbox helper from “cursor-sandbox” to “cursorsandbox” under:
/usr/share/cursor/resources/app/resources/helpers/
Systems with an existing AppArmor profile named cursor_sandbox continue to have that profile loaded in the kernel. AppArmor applies it to the renamed helper, causing signal denials between sandboxed processes and cursor-system. This prevents the Electron extension host and Remote SSH from initializing.
I don’t remember creating the cursor-sandbox AppArmor profile. I assume it was created automatically when the debian package was installed.
Kernel logs show repeated denials such as:
apparmor=“DENIED” operation=“signal”
profile=“cursor_sandbox”
peer=“cursor-system”
Does this stop you from using Cursor
Yes - Cursor is unusable