all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Mark H Weaver <mhw@netris.org>
To: Nikita Karetnikov <nikita@karetnikov.org>
Cc: guix-devel@gnu.org
Subject: Re: torify w3m: ERROR: ld.so: object ‘libtorsocks.so’ cannot be preloaded
Date: Tue, 06 May 2014 12:21:55 -0400	[thread overview]
Message-ID: <87a9auzxlo.fsf@yeeloong.lan> (raw)
In-Reply-To: <87d2frt21w.fsf@karetnikov.org> (Nikita Karetnikov's message of "Tue, 06 May 2014 18:27:39 +0400")

Nikita Karetnikov <nikita@karetnikov.org> writes:

> ‘torify w3m https://check.torproject.org’ returns the following error
> message before showing “Congratulations. This browser is configured to
> use Tor.”  Is it harmless?
>
> ERROR: ld.so: object
> /gnu/store/2g7lx2qz06vlb241gfr6bpyp6mc5a24z-torsocks-1.2/lib/torsocks/libtorsocks.so'
> from LD_PRELOAD cannot be preloaded: ignored.

No, this is an important error.  I'm reasonably sure it means that w3m
is not getting torified at all.  One possibility is that torsocks and
w3m both link to the same shared library, but they are using different
versions of that library.  Try rebuilding both w3m and torsocks to make
sure they are harmonious.

FWIW, I've never tried torifying w3m in this way.  Instead, I use
privoxy.  I configured privoxy to use Tor via SOCKS5, and I set the
http_proxy and https_proxy environment variables so that most web
clients (including w3m and guile 2.0.11) use privoxy.  IIRC, this is
recommended over using torify in most cases.

     Mark

  parent reply	other threads:[~2014-05-06 16:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-06 14:27 torify w3m: ERROR: ld.so: object ‘libtorsocks.so’ cannot be preloaded Nikita Karetnikov
2014-05-06 16:17 ` Ludovic Courtès
2014-05-06 16:21 ` Mark H Weaver [this message]
2014-05-06 19:30   ` Ludovic Courtès
2014-05-07 15:08   ` Nikita Karetnikov

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87a9auzxlo.fsf@yeeloong.lan \
    --to=mhw@netris.org \
    --cc=guix-devel@gnu.org \
    --cc=nikita@karetnikov.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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.