Javascript debug tool is not working at v 3.5.33

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Javascript debug extension not working

Steps to Reproduce

when i try to open new javascript debug terminal, i only getting Activating extensions message on the left bottom side of the window. Same if i try to run node js application via npm run --inspect mode

Expected Behavior

js debugging tool working normally

Screenshots / Screen Recordings

Operating System

Linux

Version Information

IDE:
Version: 3.5.33
VSCode Version: 1.105.1
Commit: aac81804b986d739acab348ed96b8bea6e83cc50
Date: 2026-05-22T06:47:48.039Z
Layout: editor
Build Type: Stable
Release Track: Default
Electron: 42.2.0
Chromium: 148.0.7778.97
Node.js: 24.15.0
V8: 14.8.178.14-electron.0
OS: Linux x64 7.0.9-arch2-1

Does this stop you from using Cursor

No - Cursor works, but with this issue

Hey, this is a known issue with cursor-sandbox on Arch Linux. Kernel 7.x+ restricts unprivileged user namespaces by default, so the extension host can’t start and gets stuck on Activating Extensions.

There are two workarounds:

Option A: set setuid on cursor-sandbox:

sudo chmod 4755 /usr/share/cursor/resources/app/resources/helpers/cursor-sandbox

Option B: enable unprivileged user namespaces:

sudo sysctl -w kernel.unprivileged_userns_clone=1
sudo sysctl -w kernel.apparmor_restrict_unprivileged_userns=0

To keep it after reboot, add these to /etc/sysctl.d/99-cursor.conf.

More details and discussion here: "Activating Extensions" message, extensions don't work -- solution

Let me know if either option helped.

Hi! Thanks for reaching me! I tried all the methods you send me, but none of them helped me unfortunately, the only thing that worked for me is to use official AppImage :woozy_face:

Glad the AppImage worked. That’s a valid workaround since it ships its own environment and the cursor-sandbox issue doesn’t reproduce there.

If you want to finish debugging the installed version, can you share:

  1. Which package did you install (AUR cursor-bin, cursor-extracted, or something else)? The cursor-sandbox path might be different from /usr/share/cursor/resources/app/resources/helpers/cursor-sandbox. Please check with find / -name cursor-sandbox 2>/dev/null and run chmod 4755 on the file it finds.
  2. After the sysctl commands, what’s the output of sysctl kernel.unprivileged_userns_clone kernel.apparmor_restrict_unprivileged_userns? On Arch with AppArmor you might also need sudo aa-teardown or to disable the Cursor profile.
  3. Start Cursor from a terminal and paste the output, it should show the sandbox errors.

If the AppImage is fine for you, it’s totally OK to stay on it, that’s a normal solution on Arch.

Thanks for helping me again! But i think i`ll stay on AppImage solution, maybe somebody will fix this in the newer versions :grin:

OK, AppImage on Arch is totally fine, a lot of users stick with it. The report will help, we’re seeing more cases like this with kernel 7.x.

If you want to try the AUR build again later and you hit cursor-sandbox again, just reply here or open a new thread and we’ll sort it out.

Hi, the new aur cursor-bin 3.6.31-1 is released, and now the problem is gone completely :+1: