On Tue, 15 May 2012 16:57:26 +0100
Mick <michaelkintzios@gmail.com> wrote:
> On 15 May 2012 15:45, Alan McKinnon <alan.mckinnon@gmail.com> wrote:
> > On Tue, 15 May 2012 10:50:43 +0100
> > Mick <michaelkintzios@gmail.com> wrote:
>
> >> $ ssh -D localhost:12465 root@10.10.10.12
> >
> > This part is fine.
> >
> > I tried the next part. It didn't work nicely for me.
>
> Ah, thanks for this! It's reassuring to know that it's not just my
> system. :-)
>
>
> > So what I do now is:
> >
> > Firefox + FoxyProxy
>
> Firefox is less of a problem for me because I can set it up to
> socksify everything. It is Kmail that I am mostly interested in.
>
>
> > I see recent KDE now also supports socks. This is a nice new
> > addition so konqueror can also use it.
>
> Yes, but it does not work with the current stable kmail. The new
> KDEPIM is such a nightmare I do not plan moving to it anytime soon.
> It screwed up one box that I tried it on and that's enough for me.
> :-(
>
> Did you have any success with proxychains?
>
> I am not sure if the problem is related to the tsocks LD_PRELOAD
> error.
It almost certainly is, tsocks uses LD_PRELOAD to mangle it's magic so
that stuff works. I believe chromium has severe issues with tsocks
because of how it does it's sandboxing, but I honestly don't know how
to get around that.
On a properly setup Gentoo amd64 system, /lib is a link to /lib64, so
the error you get is not a path error, the chromium binary really
cannot (or will not) deal with tsocks.so
I don't see anything wrong with the rest of your config. I honestly
think you are dealing with a chromium feature not a chromium bug.
Have you searched chromium-specific sites to see what others have to
say?
>
>
> I also noticed that when I try to set up a proxy server in Chromium
> using the 'under the bonnet' tab, I get this:
>
> "When running Chromium under a supported desktop environment, the
> system proxy settings will be used. However, either your system is not
> supported or there was a problem while launching your system
> configuration.
>
> But you can still configure via the command line. Please see man
> chromium-browser for more information on flags and environment
> variables."
>
> Trying the command line did not fix it:
>
> [4742:4753:1575546819:ERROR

bject_proxy.cc(239)] Failed to call
> method: org.freedesktop.DBus.Error.ServiceUnknown: The name
> org.freedesktop.NetworkManager was not provided by any .service files
>
> That's what made me think that something on my system is not set up
> properly. :-/
>
>
> These are the libtsocks.so files in my system:
>
> # ls -la /lib*/libtsocks.so
> lrwxrwxrwx 1 root root 14 May 13 15:34 /lib/libtsocks.so ->
> libtsocks.so.1 lrwxrwxrwx 1 root root 14 May 13
> 15:34 /lib64/libtsocks.so -> libtsocks.so.1
>
> # ls -la /lib/libtsocks.so*
> lrwxrwxrwx 1 root root 14 May 13 15:34 /lib/libtsocks.so ->
> libtsocks.so.1 lrwxrwxrwx 1 root root 16 May 13
> 15:34 /lib/libtsocks.so.1 -> libtsocks.so.1.8
> -rwxr-xr-x 1 root root 42912 May 13 15:34 /lib/libtsocks.so.1.8
>
> # ls -la /lib64/libtsocks.so*
> lrwxrwxrwx 1 root root 14 May 13 15:34 /lib64/libtsocks.so ->
> libtsocks.so.1 lrwxrwxrwx 1 root root 16 May 13
> 15:34 /lib64/libtsocks.so.1 -> libtsocks.so.1.8
> -rwxr-xr-x 1 root root 42912 May 13 15:34 /lib64/libtsocks.so.1.8
>
> I can't see why it would not load it, unless it should be trying to
> load the '/lib64/libtsocks.so' instead of the '/lib/libtsocks.so' on
> an amd64 system? Shall I file a bug?
--
Alan McKinnnon
alan.mckinnon@gmail.com