Bitwarden 2025.11.0: The SUID sandbox helper binary was found

tibitts · November 17, 2025, 9:25am

Bitwarden Password Manager desktop app 2025.11.0 on openSUSE Linux.
When attempting to start Bitwarden it fails with the following error:

./Bitwarden-2025.11.0-x86_64.AppImage
[191838:1116/112543.453330:FATAL:sandbox/linux/suid/client/setuid_sandbox_host.cc:169] 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 /tmp/.mount_bitwarDUO2z0/chrome-sandbox is owned by root and has mode 4755.
/tmp/.mount_bitwarDUO2z0/bitwarden: line 28: 191838 Trace/breakpoint trap $APP_PATH/bitwarden-app $PARAMS “$@”
<[1116/112543.485745:ERROR:base/i18n/icu_util.cc:224] Invalid file descriptor to ICU data received.

This problem did not exist with Bitwarden 2025.10.0.
Any ideas?

Nail1684 · November 17, 2025, 11:21am

@tibitts Welcome to the forum!

If I’m not mistaken, it’s the same issue as this one:

github.com/bitwarden/clients

Issue running desktop app after upgrade to `2025.11.0`

opened 10:07PM - 13 Nov 25 UTC

yermulnik

bug desktop

### Steps To Reproduce 1. Download `Bitwarden-2025.11.0-amd64.deb` from https:/…/github.com/bitwarden/clients/releases/tag/desktop-v2025.11.0 2. Install using APT package manager 3. Try to start the app ### Expected Result Desktop app starts without issues. ### Actual Result App doesn't start. Running it directly from CLI, reveals the cause: ```shell > bitwarden [3111444:1114/000039.147684:FATAL:sandbox/linux/suid/client/setuid_sandbox_host.cc:169] 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 /opt/Bitwarden/chrome-sandbox is owned by root and has mode 4755. Trace/breakpoint trap [3111447:0100/000000.174665:ERROR:content/zygote/zygote_linux.cc:660] write: Broken pipe (32) ``` ### Screenshots or Videos _No response_ ### Additional Context The suggested solution (`sudo chmod 4755 /opt/Bitwarden/chrome-sandbox`) fixes the issue. ### Operating System Linux ### Operating System Version Ubuntu 22.04.5 LTS ### Installation method Other ### Build Version 2025.11.0 ### Issue Tracking Info - [x] I understand that work is tracked outside of GitHub. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.

Someone posted a workaround there.

tibitts · November 17, 2025, 7:26pm

It appears to be the same problem, however I’m using the AppImage version of Bitwarden. No workaround for the AppImage version works here. So I’m sticking with v2025.10.0 for the time being. Hope this will be fixed soon.

Nail1684 · November 17, 2025, 9:41pm

I’m no Linux expert by any means… But that issue here: AppImage refuses to start after latest auto-update · Issue #17408 · bitwarden/clients · GitHub was closed as a duplicate of the other one - and it was mentioned there, that the same workaround also would work with the AppImage version.

tibitts · November 17, 2025, 9:46pm

Yeah, that’s what I tried, but I couldn’t get Bitwarden to start.

blackstar · November 30, 2025, 9:35pm

I’m facing the same issue with Bitwarden-2025.11.2-x86_64.AppImage on Ubuntu 22.04.5 LTS (Jammy Jellyfish). To bypass it, at the moment, I launched the appimage with the parameter –appimage-extract. It deflated the subfolder “squashfs-root”. I found a files/folder tree within it and the executable “bitwarden-app” among the files. Running directly this executable, temporarily resolves the issue getting Bitwarden working again.
However, according to the mentioned Issue running desktop app after upgrade to `2025.11.0` · Issue #17375 · bitwarden/clients · GitHub , launching the AppImage as
Bitwarden-2025.11.2-x86_64.AppImage --no-sandbox > /dev/null 2>&1 &
works as well for now.