Hey, you’ve run into two well-known issues at the same time. I’ll go through them in order.
- Corrupted state.vscdb around 16 GB
This is a known bug. state.vscdb can grow out of control. Your corrupted file is 16 GB, which matches what we’ve seen from other users. The team is aware.
Related threads:
- Cursor state.vscdb growing at 1 GB in a day
- Deleting global state.vscdb causes infinite 'Loading Chat' in projects, history not recoverable without corrupted backup
What you did, moving the corrupted files out, is the right workaround. Cursor created a new state.vscdb 188 KB, which is a normal size. The side effect is that you lose some settings, including trusted folders, so you’ll see the Workspace Trust dialog. That’s expected behavior, not a new feature.
- AppArmor denial
cursor_sandbox
This is also a known issue. The AppArmor profile shipped with Cursor is incomplete. It’s missing network rules and some other permissions. A detailed breakdown and a workaround are here: AppArmor cursor-sandbox profile incomplete on Linux — sandbox does not work correctly (missing network, signal, userns)
Quick but less safe option:
sudo sysctl -w kernel.apparmor_restrict_unprivileged_userns=0
Better option is to patch the AppArmor profile manually using the instructions in that thread.
- No Connect transport provider registered
This error was most likely caused by the corrupted state combined with an SSH remote workspace. After recreating state.vscdb, it should go away. If it still happens, let me know.
One question: is the project stored on NFS or another network filesystem? That can be a cause of corruption.