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

Aperta
#323 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
30/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
linux, shell
Ambito
desktop, security

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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

Lingua principale
Shell
Stelle
1.1k
Fork
63
Merge medio
28m
PR unite (30g)
11

Preparare l'ambiente

  • Nessun Dockerfile né file Docker Compose
  • Ha un modello di pull request
  • Nessuna guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di imputnet/helium-linux

Tutte le issue di imputnet/helium-linux

Issue simili

Altre issue su Shell/Bash

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.