48
votes

Whenever I go to a folder with a .rvmrc file, there is a warning:

Warning! PATH is not properly set up, '/home/me/.rvm/gems/ruby-2.0.0-p247/bin' is not available,
         usually this is caused by shell initialization files - check them for 'PATH=...' entries,
         to fix run: 'rvm use ruby-2.0.0-p247'.

I did rvm use ruby-2.0.0-p247, but the warning is still present.

Note: There are no errors, Im able to run my application just fine, but the warning is very annoying. Any ideas?

9
What is the output of echo $PATH?Andrew Marshall
/home/me/.rvm/gems/ruby-2.0.0-p247/bin:/home/me/.rvm/gems/ruby-2.0.0-p247@global/bin:/home/me/.rvm/rubies/ruby-2.0.0-p247/bin:/home/me/.rvm/bin:/usr/lib/lightdm/lightdm:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/gamesSanthosh
I met the same problem and by printing of $PATH, it all becomes clear that heroku's toolbelt somehow goes before ruby. Change it back solved my problem. Thanks @AndrewMarshalljames sa

9 Answers

8
votes

This was a bug and was handled with https://github.com/wayneeseguin/rvm/issues/2050 and was released as rvm stable 1.21.15 at 2013-07-29 19:15:30 -0700

131
votes

I was getting the same warning even after upgrading RVM to version 1.25.16. I was able to fix the warning by running:

rvm reset

Then when I ran:

rvm version

I did not receive the error anymore. Hope this helps!

29
votes

If you know what you're doing, and your PATH is set to what you want, you can suppress this message by putting the following in your ~/.rvmrc:

rvm_silence_path_mismatch_check_flag=1

This is handy if you use other path-manipulating programs like virtualenv, or if you just want to prefix your path with ~/bin or something.

13
votes

I was able to get rid of this by doing

rvm get head
6
votes

I had the same problem too, and rvm get head didn't work for me, finally it was solved by running rvm get head --auto-dotfiles, then restarted the terminal and the annoying warning message disappeared! And the solution is found here: https://github.com/wayneeseguin/rvm/issues/2074 Hope this will help.

2
votes

rvm get stable solved this for me

(as pointed out in comments on another answer by AndrewMarshall)

1
votes

Okay, so I ran an export PATH command without realizing the implications and ran into the identical error, but I also lost all control of my typical commands like cd and pwd. I didn't want to reset the rvm tools I'd already installed per some of the answers above.

First attempt was to some sort of mac default path (found on google):

$ export PATH="/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin"

Which actually solved my first problem of not having access to my typical command line tools, but was still getting the same error as @Santosh's initial problem. The next thing I did was navigate to my directory where I've set up rvm to start, and then to run a new export command as follows:

$ export PATH="$PATH"

This was how I initially set up rvm, and no more errors. Hope this helps someone

0
votes

Make sure that you add the following at the end of your ~/.bash_profile OR ~/.zshrc file.

In this example our ruby version is ruby-2.6.1. Replace this with your ruby version.

export PATH=~/.rvm/gems/ruby-2.6.1/bin:$PATH

# RVM manual script for loading rvm to shell
[[ -s "$HOME/.rvm/scripts/rvm" ]] && . "$HOME/.rvm/scripts/rvm"

This works for me.

0
votes

Solved!

Warning! PATH is not properly set up, '/home/vaibhav/.rvm/gems/ruby-2.3.1/bin' is not at first place, usually this is caused by shell initialization files - check them for 'PATH=...' entries, it might also help to re-add RVM to your dotfiles: 'rvm get stable --auto-dotfiles', to fix temporarily in this shell session run: 'rvm use ruby-2.3.1'.

rvm get stable --auto-dotfiles

Next you might get below Error:

RVM is not a function, selecting rubies with ‘rvm use …’ will not work. You need to change your terminal emulator preferences to allow login shell. Sometimes it is required to use /bin/bash --login as the command.