From: Luis Felipe <luis.felipe.la@protonmail.com>
To: "Daniel Meißner" <daniel.meissner-i4k@ruhr-uni-bochum.de>,
"help guix" <help-guix@gnu.org>
Subject: Re: Running graphical apps with guix shell --container
Date: Fri, 28 Jan 2022 15:22:01 +0000 [thread overview]
Message-ID: <Lra2DTHeKsP0cGuqcUlGzA5FdACqps6NEx4RQpax0A_uX_QT_7Exgu_nr4uICEGeNW4XwAC8WoCkmpBd0NyiDATJArGY7PMvEJ8geXJQlwI=@protonmail.com> (raw)
In-Reply-To: <877daks3vs.fsf@ruhr-uni-bochum.de>
[-- Attachment #1.1: Type: text/plain, Size: 2185 bytes --]
Hi Daniel,
On Friday, January 28th, 2022 at 7:42 AM, Daniel Meißner <daniel.meissner-i4k@ruhr-uni-bochum.de> wrote:
> > Also, trying the following example from Guix manual, the browser does not start:
> >
> > EXAMPLE:
> > $ guix shell --container --network --no-cwd ungoogled-chromium
> > --preserve='^DISPLAY$' -- chromium
> > Authorization required, but no authorization protocol specified
>
> This example only works on foreign distros. See the mails [1-3] on
> help-guix. However, this seems to be known much longer [4]. However,
> IMHO it is not really documented in the manual. Maybe it's time to do
> something about it since this question has now come up three times in
> the last two months. I am willing to write something but I do not feel
> compentent enough since I don't really know much about X.
Somehow I missed those messages... Daniel, I think it would be good to report the issue to https://issues.guix.gnu.org/ with the information in https://lists.gnu.org/archive/html/help-guix/2021-12/msg00088.html, and provide the command below as a proposed replacement, which I can confirm launches chromium in Guix System. I think that would be a start at least. Would you like to do that, or should I do it?
> Concerning the chromium example, for me this works:
>
> --8<---------------cut here---------------start------------->8---
> guix shell --container --network --no-cwd ungoogled-chromium \
> --preserve='^DISPLAY$' --preserve='^XAUTHORITY$' \
> --expose=$XAUTHORITY -- chromium
> --8<---------------cut here---------------end--------------->8---
>
> Maybe for your example (I couldn't check since I didn't find any package
> called mazo or python-mazo) this would work:
Yeah, sorry, I should have mentioned that "mazo" is an application I'm writing. It's not in Guix yet.
> --8<---------------cut here---------------start------------->8---
> guix shell -C --preserve='^DISPLAY$' --preserve='^XAUTHORITY$' \
> --expose=$XAUTHORITY
> --8<---------------cut here---------------end--------------->8---
Unfortunately, this didn't work. I got the same result as before.
Daniel, thanks for taking a look at this.
[-- Attachment #1.2: publickey - luis.felipe.la@protonmail.com - 0x12DE1598.asc --]
[-- Type: application/pgp-keys, Size: 1815 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 509 bytes --]
next prev parent reply other threads:[~2022-01-28 15:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-27 23:51 Running graphical apps with guix shell --container Luis Felipe
2022-01-28 10:11 ` Edouard Klein
2022-01-28 15:42 ` Luis Felipe
2022-01-28 21:12 ` Edouard Klein
[not found] ` <877daks3vs.fsf@ruhr-uni-bochum.de>
2022-01-28 15:22 ` Luis Felipe [this message]
2022-01-28 16:01 ` Luis Felipe
2022-01-29 20:15 ` Luis Felipe
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='Lra2DTHeKsP0cGuqcUlGzA5FdACqps6NEx4RQpax0A_uX_QT_7Exgu_nr4uICEGeNW4XwAC8WoCkmpBd0NyiDATJArGY7PMvEJ8geXJQlwI=@protonmail.com' \
--to=luis.felipe.la@protonmail.com \
--cc=daniel.meissner-i4k@ruhr-uni-bochum.de \
--cc=help-guix@gnu.org \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).