Does this issue occur when all extensions are disabled?: Yes/No

• VS Code Version: 1.91.1
• OS Version: Ubuntu 24.04 LTS running inside Termux Emulator

Steps to Reproduce:

I'm trying to set up vscode on my android tablet. I have Ubuntu 24.04 LTS installed with proot-distro in the Termux App (Github Release Version). Since proot treats every file as being owned by the current logged-in user, when launching VS Code I have to use the --no-sandbox argument. However if I use this argument and try to log into Github in VSCode it doesn't work because the URL Handler for VSCode is always pulled up without the --no-sandbox argument attached.
One workaround for this is to add a persistent disable-chromium-sandbox flag to ~/.vscode/argv.json since --no-sandbox is not supported for persistent arguments. However, when launching with code --disable-chromium-sandbox, vscode simply won't start and if turned on verbose mode it will complain about /usr/share/code/chrome-sandbox not being owned by root (because I'm launching from a non-root user).

1. Install Termux on any android device, then do apt install -y x11-repo proot-distro
2. proot-distro install ubuntu
3. Install Termux-X11, then attach to the ubuntu system by doing proot-distro login ubuntu
4. useradd a non-root account
5. Install VSCode 1.91.1 using the debian package
6. su to the new account
7. Use Termux X11 App to launch a new terminal window then type code --disable-chromium-sandbox --verbose