From: Giovanni Biscuolo <g@xelera.eu>
To: Andrea Rossi <p@a9i.it>, 44891@debbugs.gnu.org
Subject: bug#44891: Chromium does not start
Date: Fri, 27 Nov 2020 09:32:34 +0100 [thread overview]
Message-ID: <87r1of9p3x.fsf@roquette.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <5cf157d8-7da4-c0b7-090a-c233775fffc1@a9i.it>
[-- Attachment #1: Type: text/plain, Size: 1770 bytes --]
Ciao Andrea,
To the list: Andrea is a friend and a collegue, I'm helping him starting
using Guix as a package manager.
Andrea: next time when reporting bugs on Guix please mention you are
using it on a foreign distro (not as Guix System), in your case Debian.
Andrea Rossi via Bug reports for GNU Guix <bug-guix@gnu.org> writes:
> after the installation of ungoogled-chromium I tried to run it,
> receiving this message:
>
> [20998:20998:1126/122306.639343:FATAL:zygote_host_impl_linux.cc(117)] No
> usable sandbox! Update your kernel or see
> https://chromium.9oo91esource.qjz9zk/chromium/src/+/master/docs/linux/suid_sandbox_development.md
> for more information on developing with the SUID sandbox. If you want to
> live dangerously and need an immediate workaround, you can try using
> --no-sandbox.
>
> Maybe I'm missing something, or is the case of a proper bug?
In Jan this year I had the same issue, reported in help-guix, on Debian
as foreign distro and Marius Bakke [1] helped me solve it:
1. sudo sysctl -w kernel.unprivileged_userns_clone=1
2. sudo su -c "echo 'kernel.unprivileged_userns_clone=1' > /etc/sysctl.d/00-local-userns.conf"
This is because (ungoogled-)chromium sandbox relies on user namespaces
support in the kernel but Debian [2] disables user namespaces by
default, the above commands enables them for your current boot session
and permanently for next reboots.
Andrea please try the above fixes and tell us if they solve your issue.
Ciao, Gio'
[1] https://lists.gnu.org/archive/html/help-guix/2020-01/msg00059.html
[2] Chromium on Debian uses an alternative sandboxing method that relies
on a setuid binary, Guix do not use this :-)
--
Giovanni Biscuolo
Xelera IT Infrastructures
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 849 bytes --]
next prev parent reply other threads:[~2020-11-27 8:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-26 15:53 bug#44891: Chromium does not start Andrea Rossi via Bug reports for GNU Guix
2020-11-27 3:41 ` raingloom
2020-11-27 8:40 ` Giovanni Biscuolo
2020-11-27 8:32 ` Giovanni Biscuolo [this message]
2020-11-27 10:55 ` Andrea Rossi via Bug reports for GNU Guix
2020-11-27 15:29 ` Giovanni Biscuolo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r1of9p3x.fsf@roquette.i-did-not-set--mail-host-address--so-tickle-me \
--to=g@xelera.eu \
--cc=44891@debbugs.gnu.org \
--cc=p@a9i.it \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.