GNU bug report logs - #61697
Chromium with guix shell container from the manual doesn't work.

Previous Next

To reply to this bug, email your comments to 61697 AT debbugs.gnu.org.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: "email <at> msavoritias.me" <email <at> msavoritias.me>
To: bug-guix <at> gnu.org
Subject: Chromium with guix shell container from the manual doesn't work.
Date: Tue, 21 Feb 2023 18:50:29 +0200

Followed the manual for guix shell here: 
https://guix.gnu.org/en/manual/devel/en/guix.html#Invoking-guix-shell

Initially I wanted to setup an icecat container so I just removed 
chromium for icecat, I got this error:

```

guix shell --container --network --no-cwd icecat --preserve='^DISPLAY$' 
-- icecat
Authorization required, but no authorization protocol specified
Unable to init server: Could not connect: Connection refused
Error: cannot open display: :0.0

```


I tried chromium too. It still errors out but with a different error:

```

guix shell --container --network --no-cwd ungoogled-chromium 
--preserve='^DISPLAY$' -- chromium
Authorization required, but no authorization protocol specified
[1:1:0221/164151.354628:ERROR:ozone_platform_x11.cc(238)] Missing X 
server or $DISPLAY
[1:1:0221/164151.354678:ERROR:env.cc(255)] The platform failed to 
initialize.  Exiting.

```


Chromium starts just fine without the container flag so the problem 
seems to be in the container flag specifically.


Msavoritias

Message #8 received at 61697 <at> debbugs.gnu.org (full text, mbox):

From: "email <at> msavoritias.me" <email <at> msavoritias.me>
To: 61697 <at> debbugs.gnu.org
Subject: bug#61697: Chromium with guix shell container from the manual doesn't
 work.
Date: Mon, 6 Mar 2023 15:07:04 +0200

The problem was that in xorg you need the specific option:

```

--share=/tmp

```

So the command would look like:

```

guix shell --container --network --share=/tmp --no-cwd icecat 
--preserve='^DISPLAY$' -- icecat

```


While in wayland it works as is.

Next step would be documenting this in the manual.

Message #11 received at 61697 <at> debbugs.gnu.org (full text, mbox):

From: Simon Tournier <zimon.toutoune <at> gmail.com>
To: email <at> msavoritias.me
Cc: 61697 <at> debbugs.gnu.org
Subject: Re: bug#61697: Chromium with guix shell container from the manual
 doesn't work.
Date: Tue, 11 Apr 2023 15:36:14 +0200

Hi,

On lun., 06 mars 2023 at 15:07, "email <at> msavoritias.me" <email <at> msavoritias.me> wrote:

> Next step would be documenting this in the manual.

Do you want to give a try in fixing the example provided by the manual?  WDYT?


Cheers,
simon

Message #14 received at 61697 <at> debbugs.gnu.org (full text, mbox):

From: Виталий Ковалев
 <kvp94best <at> gmail.com>
To: 61697 <at> debbugs.gnu.org
Date: Sun, 16 Apr 2023 10:37:32 +0000

[Message part 1 (text/plain, inline)]

Still have the same error with specifying --share=/tmp. Maybe I should add
something else?
```
kovalev <at> mirage ~$ guix shell --container --network --preserve="^DISPLAY$"
--no-cwd --share=/tmp ungoogled-chromium -- chromium
Authorization required, but no authorization protocol specified
[1:1:0416/103619.358790:ERROR:ozone_platform_x11.cc(238)] Missing X server
or $DISPLAY
[1:1:0416/103619.358806:ERROR:env.cc(255)] The platform failed to
initialize.  Exiting.
```
```
kovalev <at> mirage ~$ guix shell --container --network --preserve="^DISPLAY$"
--no-cwd --share=/tmp icecat -- icecat
Authorization required, but no authorization protocol specified
Unable to init server: Could not connect: Connection refused
Error: cannot open display: :1
```

[Message part 2 (text/html, inline)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.