From: Julian Flake <julian@flake.de>
To: help-guix@gnu.org
Cc: Caleb Herbert <csh@bluehome.net>
Subject: Re: Cannot start Tor Browser
Date: Thu, 30 Nov 2023 12:07:49 +0100 [thread overview]
Message-ID: <8734wnh4zk.fsf@flake.de> (raw)
In-Reply-To: <87fs0oky7o.fsf@bluehome.net>
Dear Caleb,
this is how I currently start a Tor browser, if needed:
https://github.com/nuthub/guix-shell-examples#tor-browser
Best Regards,
Julian Flake
On Wed, Nov 29 2023, Caleb Herbert wrote:
> [[PGP Signed Part:Undecided]]
> Hi Guix,
>
> I cannot start Tor Browser from following the instructions on
> the FHS
> article.
>
> https://guix.gnu.org/en/blog/2023/the-filesystem-hierarchy-standard-comes-to-guix-containers/
>
> $ ls
> Browser/ start-tor-browser.desktop
> $ guix shell --container \
> --network --emulate-fhs \
> --preserve='^DISPLAY$' --preserve='^XAUTHORITY$'
> --expose=$XAUTHORITY \
> alsa-lib bash coreutils dbus-glib file gcc:lib \
> grep gtk+ libcxx pciutils sed \
> -- ./start-tor-browser.desktop -v
> guix shell: package 'gcc' has been superseded by 'gcc-toolchain'
> guix shell: error: package `gcc-toolchain@11.3.0' lacks output
> `lib'
> $
>
> --
> Caleb Herbert
> https://bluehome.net/csh/
> OpenPGP fingerprint: 631C C434 A56B 5CBD FF21 2346 9764 3795
> FA3E 4BCE
> What's a fingerprint? https://emailselfdefense.fsf.org/
>
> [[End of PGP Signed Part]]
next prev parent reply other threads:[~2023-11-30 11:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-29 22:10 Cannot start Tor Browser Caleb Herbert
2023-11-30 11:07 ` Julian Flake [this message]
2023-11-30 20:25 ` Caleb Herbert
2023-11-30 20:18 ` Georgios Athanasiou
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=8734wnh4zk.fsf@flake.de \
--to=julian@flake.de \
--cc=csh@bluehome.net \
--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).