unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Georgios Athanasiou <yorgath@gmail.com>
To: Caleb Herbert <csh@bluehome.net>, help-guix@gnu.org
Subject: Re: Cannot start Tor Browser
Date: Thu, 30 Nov 2023 22:18:08 +0200	[thread overview]
Message-ID: <8c61b2af-97b4-4102-82ab-eaaf2b1e4c94@gmail.com> (raw)
In-Reply-To: <87fs0oky7o.fsf@bluehome.net>

Hi Caleb,

On 11/30/23 00:10, Caleb Herbert wrote:
> 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'
> $
>
Hopefully you'll be able to get it running using Julian's advice. If 
everything else fails, there's always Flatpak on Guix OS. Tor Browser 
Launcher is on Flathub.

(Please do note that this is *not* an endorsement. I haven't done much 
research on this launcher's trustworthiness, since I don't feel my use 
cases are that sensitive privacy-wise (I don't enjoy corporations 
tracking me across the Web is all). Do your research before trusting it 
with sensitive information.)

Best Regards,

G.




      parent reply	other threads:[~2023-11-30 20:18 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
2023-11-30 20:25   ` Caleb Herbert
2023-11-30 20:18 ` Georgios Athanasiou [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=8c61b2af-97b4-4102-82ab-eaaf2b1e4c94@gmail.com \
    --to=yorgath@gmail.com \
    --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).