Rubygems freezes with expand_path error

Hi,
Rubygems went crazy.
Here is the command sequence:

gem list

*** LOCAL GEMS ***

actionmailer (2.3.5)
actionpack (2.3.5)
activerecord (2.3.5)
activeresource (2.3.5)
activesupport (2.3.5)
calendar_date_select (1.16.1)
cgi_multipart_eof_fix (2.5.0)
daemons (1.0.10)
eventmachine (0.12.10)
fastthread (1.0.7)
gem_plugin (0.2.3)
image_science (1.2.1)
memcache-client (1.8.3)
mime-types (1.16)
mongrel (1.1.5)
mysql (2.8.1)
rack (1.0.1)
rails (2.3.5)
rake (0.8.7)
rcov (0.9.8)
rspec (1.3.0)
ruby-fcgi (0.8.9)
ruby-lsapi (4.0)
RubyInline (3.8.4)
sqlite3-ruby (1.2.5)
starling (0.10.1)
thin (1.2.7)
webroar (0.3.1)
will_paginate (2.3.12)
ZenTest (4.3.1)

webroar stop

Stopping webroar-head … done.
Stopping webroar-analyzer process … done.

webroar uninstall

Removing executables … done.
Removing admin panel application database … done.
WebROaR uninstalled successfully.
Removing files …
Removing log rotate file … done.
Removing service script … done.

gem list

/usr/lib/ruby/1.8/rubygems.rb:471:in expand_path': No such file or directory - getcwd (Errno::ENOENT) from /usr/lib/ruby/1.8/rubygems.rb:471:infind_files’
from /usr/lib/ruby/1.8/rubygems.rb:470:in map' from /usr/lib/ruby/1.8/rubygems.rb:470:infind_files’
from /usr/lib/ruby/1.8/rubygems.rb:1103
from /usr/bin/gem:8:in `require’
from /usr/bin/gem:8

what happened?

regards

   from /usr/bin/gem:8

what happened?

regards

Posted via http://www.ruby-forum.com/.

Looks like the current working directory for the ruby process was erased
as part of the earlier gem uninstall. “getcwd (Errno::ENOENT)”

After uninstalling rubygems and installing it again, it worked :slight_smile:

James H.on wrote:

   from /usr/bin/gem:8

what happened?

regards

Posted via http://www.ruby-forum.com/.

Looks like the current working directory for the ruby process was erased
as part of the earlier gem uninstall. “getcwd (Errno::ENOENT)”

On May 22, 2010, at 14:42, Bruno S. wrote:

After uninstalling rubygems and installing it again, it worked :slight_smile:

That didn’t fix it.

Your current directory disappeared cd ~ (or similar) fixed it.