Error message when opening cursor-Terminal sandbox could not start

Support Bug Reports
, ,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Terminal sandbox could not start. This may be caused by an AppArmor configuration on your Linux system (kernel 6.2+). See the documentation for how to resolve this.

Steps to Reproduce

just lunch cursor, message there.
terminal is working fine

Expected Behavior

not getting error messahes

Screenshots / Screen Recordings

cursor screen.png
cursor screen.png836×651 25.8 KB

Operating System

Linux

Version Information

Version: 2.6.20
VSCode Version: 1.105.1
Commit: b29eb4ee5f9f6d1cb2afbc09070198d3ea6ad760
Date: 2026-03-17T01:50:02.404Z
Build Type: Stable
Release Track: Default
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
OS: Linux x64 6.17.0-19-generic

Does this stop you from using Cursor

No - Cursor works, but with this issue

4

Hey, this is a known issue on Linux with kernel 6,2+ and we already have a full thread about it: Terminal Sandbox Issue Linux

Since your terminal works fine, the easiest option is to click Don’t Show Again in the notification and it won’t show up anymore.

If you want to try fixing the sandbox properly, try creating an AppArmor profile:

  1. Create /etc/apparmor.d/cursor-system:
abi <abi/4.0>,
include <tunables/global>
profile cursor-system "/usr/share/cursor/cursor" flags=(unconfined) {
  userns,
  include if exists <local/cursor>
}
  1. Load it:
sudo apparmor_parser -r /etc/apparmor.d/cursor-system
  1. Restart Cursor.

The team is aware of this issue. Let me know if any of this helps.

5

A post was merged into an existing topic: Terminal Sandbox Issue Linux