Cursor Remote SSH crashes on Ubuntu 22.04 VMware VM while VS Code Remote SSH works

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Title: Cursor Remote SSH crashes on Ubuntu 22.04 VMware VM while VS Code Remote SSH works

Environment

  • Cursor Remote SSH
  • Remote OS: Ubuntu 22.04.2 LTS
  • Kernel: 5.15.0-179-generic
  • Hypervisor: VMware
  • CPU: Intel Xeon Gold 6226R (virtualized)
  • Cursor remote Node version: v20.18.2
  • VS Code remote Node version: v22.22.1

Problem

Cursor Remote SSH fails to connect to the remote VM.

The remote server starts successfully, binds to a port, and launches the Extension Host. Shortly afterwards the Extension Host crashes with SIGSEGV.

VS Code Remote SSH connects successfully to the same VM using the same user and SSH configuration.

Cursor Remote Log

Extension host agent started.

Launched Extension Host Process.

Extension Host Process exited with code: null, signal: SIGSEGV.

Additional Logs

Failed to apply sandbox: Failed to apply Landlock

Landlock V3 filesystem restrictions not supported.

Ensure Landlock LSM is enabled (CONFIG_SECURITY_LANDLOCK=y) on a kernel with V3 support.
[ExtHostShellExec] Sandbox support detected: false

Verification Performed

  • Deleted ~/.cursor-server and reinstalled
  • Reproduced issue by manually starting cursor-server
  • Cursor server starts and binds successfully
  • Extension Host crashes with SIGSEGV
  • Removed ~/.cursor-server/extensions and retried
  • Verified Ubuntu 22.04.2 environment
  • Verified SSH connectivity
  • Verified VS Code Remote SSH works correctly on the same VM

Landlock Status

CONFIG_SECURITY_LANDLOCK=y

Kernel configuration contains Landlock support, but Cursor reports Landlock V3 filesystem restrictions are unsupported.

Expected Result

Cursor Remote SSH should connect successfully, similar to VS Code Remote SSH.

Actual Result

Extension Host process crashes with SIGSEGV and connection fails.

Steps to Reproduce

connect to remote host.
server installed, still crashes.

Expected Behavior

segfault on vm

Operating System

Linux

Version Information

version: 3.6

Does this stop you from using Cursor

Yes - Cursor is unusable

Hey @Sudhir!

This looks like the same issue reported over here.

Could you try the workaround in the thread to confirm if it’s the same issue?

If so, we’ll reopen the ticket which was closd for inactivity.

it worked, thanks