VSCodium fails to start when installed as a .deb package on Ubuntu 24.04

[leaf-node]

Describe the bug

After upgrading from Ubuntu 23.10 to 24.04 (Noble Numbat), Codium no longer starts.

Please confirm that this problem is VSCodium-specific

• This bug doesn't happen if I use Microsoft's Visual Studio Code. It only happens in VSCodium.

Please confirm that the issue/resolution isn't already documented

• I checked the Docs page and the Troubleshooting page and my issue is not mentioned there.

To Reproduce
Steps to reproduce the behavior:

1. Upgrade from Ubuntu 23.10 to 24.04 on an amd64 install
2. Install the latest version (1.88.1.24104) of VSCodium via apt
3. Run the codium command, or click on the launch icon

Expected behavior
My goal is to start the Codium editor.

What happens instead is nothing. The first couple of times that I tried launching it, a dialog showed up with debug info, but that stopped appearing eventually, so I don't have its details. If I see it again, I can post info here.

Desktop (please complete the following information):

• OS: Ubuntu 24.04
• Architecture: amd64
• Version: 1.88.1.24104
• App Manager: Apt
• Sandboxed: no

Additional context
The codium command exits with exit code 0 when run from the command line.

[leaf-node]

$ codium --verbose
[56568:0425/211043.079940:FATAL:credentials.cc(127)] Check failed: . : Permission denied (13)

File permissions are correct under the config directory:

chmod -R u+rwX ~/.config/VSCodium
chown -R andrew:andrew ~/.config/VSCodium

[daiyam]

Weird! What about ~/.vscode-oss?

[leaf-node]

Weird! What about ~/.vscode-oss?

Same issue after changing permissions on that directory.

As odd as it seems, perhaps this is a Chromium bug triggered by the kernel version?

[daiyam]

As odd as it seems, perhaps this is a Chromium bug triggered by the kernel version?

Yeah. Same error... even vscode is mentioned in comments

[leaf-node]

The Snap and Flatpak versions do work. The Snap version seems to act less containerized, so it's able to access system dependencies like /usr/bin/clang++, which is needed for Flutter integration, for example.

[darealshinji]

Strange. Using the installation method from the link (https://vscodium.com/#install-on-debian-ubuntu-deb-package) works for me.
But running it from the AppImage or the extracted .tar.gz archive doesn't work:

$ ./bin/codium --verbose
[26098:0502/005812.130922:FATAL:setuid_sandbox_host.cc(158)] The SUID sandbox helper binary was found, but is not configured correctly. Rather than run without sandboxing I'm aborting now. You need to make sure that /home/djcj/Downloads/chrome-sandbox is owned by root and has mode 4755.

$ ./VSCodium-1.88.1.24104.glibc2.17-x86_64.AppImage --verbose
sed: /tmp/.mount_VSCodi59dztj/lib/x86_64-linux-gnu/libselinux.so.1: no version information available (required by sed)
codium: /tmp/.mount_VSCodi59dztj/lib/x86_64-linux-gnu/libselinux.so.1: no version information available (required by /lib/x86_64-linux-gnu/libgio-2.0.so.0)
codium: /tmp/.mount_VSCodi59dztj/lib/x86_64-linux-gnu/libselinux.so.1: no version information available (required by /lib/x86_64-linux-gnu/libmount.so.1)
The setuid sandbox is not running as root. Common causes:
  * An unprivileged process using ptrace on it, like a debugger.
  * A parent process set prctl(PR_SET_NO_NEW_PRIVS, ...)
Failed to move to new namespace: PID namespaces supported, Network namespace supported, but failed: errno = Operation not permitted
[26108:0502/005837.571071:FATAL:zygote_host_impl_linux.cc(201)] Check failed: . : Das Argument ist ungültig (22)
/tmp/.mount_VSCodi59dztj/usr/share/codium/codium: /tmp/.mount_VSCodi59dztj/lib/x86_64-linux-gnu/libselinux.so.1: no version information available (required by /lib/x86_64-linux-gnu/libgio-2.0.so.0)
/tmp/.mount_VSCodi59dztj/usr/share/codium/codium: /tmp/.mount_VSCodi59dztj/lib/x86_64-linux-gnu/libselinux.so.1: no version information available (required by /lib/x86_64-linux-gnu/libmount.so.1)
Trace/Breakpoint ausgelöst (Speicherabzug geschrieben)

Ubuntu Cinnamon 24.04 LTS x86_6
Kernel: 6.8.0-31-generic

[Drasli-Tana]

Same issue here, the issue was resolved for me by allowing user namespace creation for VSCodium in apparmor profile