# Javascript debug tool is not working at v 3.5.33

**URL:** <https://forum.cursor.com/t/javascript-debug-tool-is-not-working-at-v-3-5-33/161467>\
**Category:** Bug Reports\
**Tags:** linux, extensions\
**Created:** [May 24, 2026, 8:30pm UTC](https://forum.cursor.com/t/javascript-debug-tool-is-not-working-at-v-3-5-33/161467 "2026-05-24T20:30:04Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![deanrie](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/deanrie/32/1263_2.png) [@deanrie](https://forum.cursor.com/u/deanrie)\
**Post date:** [May 25, 2026, 4:58am UTC](https://forum.cursor.com/t/javascript-debug-tool-is-not-working-at-v-3-5-33/161467/5 "2026-05-25T04:58:28Z")

</div>

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:

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

```

Option B: enable unprivileged user namespaces:

```bash
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](https://forum.cursor.com/t/activating-extensions-message-extensions-dont-work-solution/146013)

Let me know if either option helped.

---

_[View the full topic](https://forum.cursor.com/t/javascript-debug-tool-is-not-working-at-v-3-5-33/161467)._