'libproxychains.so.3' from LD_PRELOAD cannot be preloaded

Bug #1513727 reported by Steve Zhang
24
This bug affects 5 people
Affects Status Importance Assigned to Milestone
proxychains (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

It always notics this message "'libproxychains.so.3' from LD_PRELOAD cannot be preloaded".
I installed proxychains from Software Center on Ubuntu 15.10.
The proxychains version is 3.1-6.

```log
proxychains ping www.google.com
ProxyChains-3.1 (http://proxychains.sf.net)
ERROR: ld.so: object 'libproxychains.so.3' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
PING www.google.com (173.194.72.106) 56(84) bytes of data.
```

Counld you please review the problem?

DistroRelease: Ubuntu 15.10
Package: libproxychains3 3.1-6.so
Uname: Linux 4.2.0-16-generic x86_64
CurrentDesktop: Unity
Date: Fri Nov 6 2015
SourcePackage: proxychains

description: updated
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in proxychains (Ubuntu):
status: New → Confirmed
Revision history for this message
weakish (weakish) wrote :

Same issue on ProxyChains-3.1 (Ubuntu 14.04).

In `/usr/bin/proxychains`:

```
export LD_PRELOAD=libproxychains.so.3
```

The path is wrong.

For example, on a amd64 machine, this line should be:

```
export LD_PRELOAD=/usr/lib/x86_64-linux-gnu/libproxychains.so.3
```

Revision history for this message
Farab (farabf33) wrote :

In my case,

    export LD_PRELOAD=/usr/lib/x86_64-linux-gnu/libproxychains.so.3

did not work. I also added this line to my `.bashrc` and refreshed it by `source ~/.bashrc`

**Solution:**
You need to add/edit it to `proxychains` by:

    sudo gedit /usr/bin/proxychains

if on 32bit Ubuntu and derivatives, replace `x86_64-linux-gnu` with `i386-linux-gnu`

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.