RVM and RBenv are actually similar tools. There
are no practical reasons to keep them alongside
each other in one session (and on one machine most
of the time). They both rely on modifying
PATH environment variable to get the
Ruby and supplementary binaries closer for easy
And that's what RVM complains about:
PATH is not what it expects to be.
That said, RBEnv apparently tampered with it.
Since these tools do their best to overtake
irb and stuff, they may very well
conflict with each other on occasions.
So, remove one of them. Which one, is up to
you. Removing RVM is as easy as:
...that will remove RVM's files, rubies and
gems for them, but you might also want to inspect
.bashrc for relevant lines.
The uninstallation process for RBEnv seems to
be the manual one: remove the folder, review the
files listed above for relevant lines.