From: "Daniel Meißner" <daniel.meissner-i4k@rub.de>
To: t@fullmeta.me
Cc: zimoun <zimon.toutoune@gmail.com>, help-guix@gnu.org
Subject: Re: Emacs inside container: preserved DISPLAY unavailable etc
Date: Wed, 05 Jan 2022 15:48:17 +0100 [thread overview]
Message-ID: <19752F73-2063-41BA-A8A0-6AB3D68C521E@rub.de> (raw)
In-Reply-To: <b4f27d76-3b76-4ac3-a04d-0be2d9e3154d@www.fastmail.com>
t@fullmeta.me writes:
> > Authorization required, but no authorization protocol specified
>
> Actually, mine only said "No protocol specified" making it vague, yours at least hint at something to investigate.
Yes, the error message changed indeed the last time I tried the container example. I just blindly copied and pasted the output from my shell without noticing really.
> Googling around shows people don't seem to know what they are doing and afraid to dig into X internals, so most posts are just cargo-culting and trying random stuff. Sadly, I'm in that group, so lets just randomly try stuff:
>
> $ echo $XAUTHORITY
> /run/user/1000/gdm/Xauthority
>
> which stores some magic cookie, so lets add
>
> --expose=$XAUTHORITY --preserve='^XAUTHORITY$'
>
> standing ovation, everyone congratulates everyone, noone really understands what just happened
>
> I guess manual needs to be updated, or maybe guix shell --container Scheme code. Dunno
>
> Thank you very much for that STDERR hint
Happy my comment helped and thank you for your solution I will try that for the chromium example as well.
Best,
Daniel
prev parent reply other threads:[~2022-01-05 14:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-04 12:29 Emacs inside container: preserved DISPLAY unavailable etc t
2022-01-04 17:03 ` zimoun
2022-01-04 17:11 ` Vlad Kozin
2022-01-05 12:39 ` Daniel Meißner
2022-01-05 13:09 ` t
2022-01-05 14:48 ` Daniel Meißner [this message]
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=19752F73-2063-41BA-A8A0-6AB3D68C521E@rub.de \
--to=daniel.meissner-i4k@rub.de \
--cc=help-guix@gnu.org \
--cc=t@fullmeta.me \
--cc=zimon.toutoune@gmail.com \
/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).