[Bug]: Helium does not run without --no-sandbox on Bedrock Linux

Open
#323 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
30/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
linux, shell
Domain
desktop, security

Research direction

The failure is the 'No usable sandbox' fatal from content/browser/zygote_host/zygote_host_impl_linux.cc in upstream Chromium, which Helium builds on, and the packaging here is a shell-based Linux launcher. Start by reproducing the launch on a Bedrock Linux strata, or compare the sandbox and user-namespace setup against ungoogled-chromium on the same system. Done means Helium starts without --no-sandbox on that setup, or the cause is documented.

Written by the indexing model from the issue text.

Description

bug
Version

0.14.2.1

Have you tested that this is not an upstream issue or an issue with your configuration?
  • I have tried reproducing this issue in Chrome and it could not be reproduced there
  • I have tried reproducing this issue in ungoogled-chromium and it could not be reproduced there
  • I have tried reproducing this issue in Helium with a new and empty profile using --user-data-dir command line argument and it could not be reproduced there
Description

Helium installed on Bedrock Linux does not launch due to sandbox issues, ungoogled-chromium works

How to Reproduce?
  1. Setup Bedrock Linux (on my system i am using Alpine as a base)
  2. Add a secondary strata of a supported distro (tested both Fedora and Arch)
  3. Install Helium on the aforementioned strata
  4. Launch Helium
Actual behavior

Helium refuses to launch due to lack of a "usable sandbox"

$ helium-browser
[28598:28598:0702/224752.779209:FATAL:content/browser/zygote_host/zygote_host_impl_linux.cc:128] 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.9oo91esource.qjz9zk/chromium/src/+/main/docs/security/apparmor-userns-restrictions.md. Otherwise see https://chromium.9oo91esource.qjz9zk/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.
Trace/breakpoint trap
Expected behavior

Helium to launch fine, as with ungoogled-chromium installed on same strata.

Image
Additional context

No response

Dominant language
Shell
Stars
1.1k
Forks
63
Avg merge
28m
Merged PRs (30d)
11

Getting set up

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from imputnet/helium-linux

All issues in imputnet/helium-linux

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.