Usr/local/bin/virtualenvwrapper.sh No Such File Or Directory

We use cookies for various purposes including analytics. By continuing to use Pastebin, you agree to our use of cookies as described in the Cookies Policy. OK, I Understand.

I am trying to install Virtualenv wrapper on Ubuntu 14.04. But whenever I start a terminal, I get the error saying bash:

/usr/share/virtualenvwrapper/virtualenvwrapper_lazy.sh: No such file or directory.

I also checked the bashrc script by using gedit ~/.bashrc, but there is no such line like that. Does anyone know where I am wrong?

6 Answers

I just had the same problem on Linux Mint.

The following file was causing the issue:/etc/bash_completion.d/virtualenvwrapper

I made a backup (just in case) and deleted it, and everything seems to be working fine now.

In my case, I had previously installed virtualenvwrapper using apt-get install virtualenvwrapper and later uninstalled it using apt-get remove virtualenvwrapper, which left the 'configuration' file /etc/bash_completion.d/virtualenvwrapper behind. This bash completion definition was sourced by bash (it had nothing to do with my .bashrc) and caused the error message.

The solution was to run:

Which purged all files related to virtualenvwrapper. The reason I uninstalled it was to use pip's version instead (more up-to-date), which can be installed globally using:

Following these instructions, I found that the error occurred when sourcing the virtualenvwrapper bash script, i.e.:

The script references the file /etc/bash_completion.d/virtualenvwrapper as pointed out by arcticfeather.

Open up the script using the following command:

This is where the non-existent file is being referenced. Simply replace /usr/share/virtualenvwrapper/virtualenvwrapper_lazy.sh with /usr/local/bin/virtualenvwrapper_lazy.sh and you should be good to go!

If none of the answers work like for myself, just create an empty file at the location giving out an error and shebang to it.

In the case of OP:

sudo nano /usr/share/virtualenvwrapper/virtualenvwrapper_lazy.sh

and write:

#!/bin/bash

Save it and try to open terminal again, did the trick for me

You can install Extension to virtualenv for managing multiple virtual Python environments (virtualenvwrapper) in Ubuntu 14.04 from the Ubuntu Software Center or from the terminal using the following command:

Add the following line to the end of .bashrc.

Save the changes to .bashrc and close gedit. Source your .bashrc for the changes to take effect.

I hope it help someone, in my case i was trying to create the virtualenv being inside a screen (screen -S whatever), the solution was closing the screen and executing the virtualenv command again being outside.

Not the answer you're looking for? Browse other questions tagged bashvirtualenv or ask your own question.

I've downloaded a game (Shank) but the bin file doesn't run. The error that is shown when I try to launch the executable is:

5 Answers

You're probably trying to run a 32-bit binary on a 64-bit system that doesn't have 32-bit support installed.

There are three cases where you can get the message “No such file or directory”:

• The file doesn't exist. I presume you've checked that the file does exist (perhaps because the shell completes it).
• There is a file by that name, but it's a dangling symbolic link.
• The file exists, and you can even read it (for example, the command file shank-linux-120720110-1-bin displays something like “ELF 32-bit LSB executable …”), and yet when you try to execute it you're told that the file doesn't exist.

The error message in this last case is admittedly confusing. What it's telling you is that a key component of the runtime environment necessary to run the program is missing. Unfortunately, the channel through which the error is reported only has room for the error code and not for this extra information that it's really the runtime environment that's to blame. If you want the technical version of this explanation, read Getting “Not found” message when running a 32-bit binary on a 64-bit system.

The file command will tell you just what this binary is. With a few exceptions, you can only run a binary for the processor architecture that your release of Ubuntu is for. The main exception is that you can run 32-bit (x86, a.k.a. IA32) binaries on 64-bit (amd64, a.k.a. x86_64) systems.

In Ubuntu up to 11.04, to run a 32-bit binary on a 64-bit installation, you need to install the ia32-libs package. You may need to install additional libraries (you'll get an explicit error message if you do).

Since 11.10 (oneiric) introduced multiarch support, you can still install ia32-libs, but you can choose a finer-grained approach, it's enough to get libc6-i386 (plus any other necessary library).

64 bit Ubuntu Multiarch systems

Follow this answer only if the output of file file-name shows,

To run 32bit executable file in a 64 bit multi-arch Ubuntu system, you have to add i386 architecture and also you have to install libc6:i386,libncurses5:i386,libstdc++6:i386 these three library packages.

By installing the deb for 32 bit I realized I was missing some libraries (in addition to ia32-libs and libc6). I first solved this problem by giving this command:

Then I got another error:

Obviously, these libraries were properly installed. Without going into details I had to link the libraries by hand. I realized then that could also an easier solution through Synaptic install the following packages:

After that the next problem was the black screen while playing, which I solved by replacing the executable in /Shank/bin with this:http://treefort.icculus.org/smb/smb-linux-mesa-hotfix-test.tar.bz2.

I hope it will be useful to someone.If you need more help or more details please feel free to contact me.

Here's a transcript showing a bit more about the nature of the problem, and how to fix it as of Ubuntu 16.04. Notice that even though file reports 'dynamically linked', ldd reports 'not a dynamic executable'.

Once you install libc6:i386, things start improving...

To complete the job, you may need to identify and install additional libraries one at a time...

I don't know if there is a systematic way of identifying the correct libraries to install. There is a bit of guesswork mapping the error messages to package names (tab completion helps).

To expand on @Gilles answer, there are at least three scenarios resulting in this error:

1. The file doesn't exist.
2. The file exists but is a dangling symbolic link.
3. The file exists (e.g. file command works), making for a puzzling error message. This may mean there's a problem with the loader.

Categories of loader problems:

1. An executable's loader does not exist. You can check this using the file command and see if the loader does exist. E.g.

   Notice interpreter /lib64/ld-lsb-x86-64.so.3; if this file does not exist, you need to install it. For this particular loader on 16.04, the answer turned out to be sudo apt-get install lsb.

2. Issues with a script's loader (see this answer).

3. Missing shared libraries -- use ldd <file-name> to check for any 'not found' libraries. See this answer for more info.

The loader not existing could be due to a 32/64 bit mismatch or some other reason. There might be other kinds of loader errors I don't know about.

protected by Community♦Aug 10 '16 at 15:54

Thank you for your interest in this question. Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).
Would you like to answer one of these unanswered questions instead?

Not the answer you're looking for? Browse other questions tagged 64-bitfilesgamesexecutable or ask your own question.