Subject: bug#44891: closed (Re: bug#44891: Chromium does not start)

From: [email-masked] (GNU bug Tracking System)
Date: Fri, 27 Nov 2020 15:30:02 +0000

Your bug report

#44891: Chromium does not start

which was filed against the guix package, has been closed.

The explanation is attached below, along with your original report.
If you require more details, please reply to [email-masked].

-- 
44891: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=44891
GNU Bug Tracking System
Contact [email-masked] with problems

Subject: Re: bug#44891: Chromium does not start
From: Giovanni Biscuolo <[email-masked]>
To: Andrea Rossi <[email-masked]>, [email-masked]
Date: Fri, 27 Nov 2020 16:29:12 +0100
List-Id: <debbugs-submit.debbugs.gnu.org>

Andrea Rossi via Bug reports for GNU Guix <[email-masked]> writes:

> On 27/11/20 09:32, Giovanni Biscuolo wrote:
>> [...]
>> 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" 
>
> It works!

Fine! Closing this bug.

Ciao, Gio'

-- 
Giovanni Biscuolo

Xelera IT Infrastructures

Subject: Chromium does not start
From: Andrea Rossi <[email-masked]>
To: [email-masked]
Date: Thu, 26 Nov 2020 16:53:29 +0100
List-Id: <debbugs-submit.debbugs.gnu.org>

Hi,
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?

Regards,
-- 
Andrea