New @Docs "Failed to launch the browser process! [...] No usable sandbox!", chrome coredumps mentioned in the system log

[TiagoTiago]

Before submitting your bug report

• [X] I believe this is a bug. I'll try to join the Continue Discord for questions
• [X] I'm not able to find an open issue that reports the same bug
• [X] I've seen the troubleshooting guide on the Continue Docs

Relevant environment info

 - OS: Linux Mint 20.3 Kernel: 5.15.0-119-generic 
 - Continue: v0.8.47 AND v0.9.202 (pre-release)
 - IDE: VSCodium 
     Version: 1.92.2
     Release: 24228
     Commit: 21b1e2955ddda36eeba3a94e643128e465285b93
     Date: 2024-08-15T18:27:27.910Z
     Electron: 30.1.2
     ElectronBuildId: undefined
     Chromium: 124.0.6367.243
     Node.js: 20.14.0
     V8: 12.4.254.20-electron.0 
 - config.json: I tried deleting the existing one to start with a default one, still got the same results, so doesn't seem to be relevant

Description

Cannot create new custom Docs or use old ones; builtin chromium seems to always crash showing an error message on VSCodium (and a rare few times says it worked but the new docs do not show up).

Error message seems to suggest some issue with sandboxing chrome; and system log reports chrome coredumped.

To reproduce

Write @Docs, go to the bottom of the list to pick the option to create a new one, fill name and url (random example, SciPy and https://docs.scipy.org/doc/scipy/), click submit. Error pops up and the Doc is not created.

Log output

Extension Host] Error handling webview message: {
  "msg": {
    "messageId": "######################",
    "messageType": "context/addDocs",
    "data": {
      "startUrl": "https://docs.scipy.org/doc/scipy/",
      "title": "SciPy",
      "faviconUrl": ""
    }
  }
}

Error: Failed to launch the browser process!
[##################:FATAL:zygote_host_impl_linux.cc(########)] No usable sandbox! If you are running on Ubuntu 23.10+ or another Linux distro that has disabled unprivileged user namespaces with AppArmor, see https://chromium.googlesource.com/chromium/src/+/main/docs/security/apparmor-userns-restrictions.md. Otherwise see https://chromium.googlesource.com/chromium/src/+/main/docs/linux/suid_sandbox_development.md for more information on developing with the (older) SUID sandbox. If you want to live dangerously and need an immediate workaround, you can try using --no-sandbox.

(Numbers replaced by random count of #'s cause I dunno if they could be decoded as sensitive information, or used for fingerprinting etc. After this there are many lines I'm not sure how sensitive they are, lemme know if you're looking for something in specific there, or even if there actually nothing sensitive that could ever be shown there and it's all safe to copypaste)

As mentioned before, the system log reports chrome has core dumped; dunno how sensitive the info in there is.