[solved] ruby traceback error after package upgrade

lnx · 2018-01-06 14:56:25

I did an upgrade last night. When I logged in the following message was shown:

Traceback (most recent call last):
1: from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in `require'
/usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in `require': cannot load such file -- ubygems (LoadError)

According to pacman -Qs ruby and ruby-thor were installed. I tried to downgrade both packages. But when I restarted my PC, I could still log in as a regular user. But every command I tried, resulted in 'command not found' I had to upgrade ruby to be able to use startx again.
Assuming that 59 means line 59, I looked in /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb, but I can't make sense of it:

57 if Gem::Specification.unresolved_deps.empty? then
58 RUBYGEMS_ACTIVATION_MONITOR.exit
59 return gem_original_require(path)
60 end

So, can any body tell what this traceback message means?

Last edited by lnx (2018-01-06 16:36:38)

V1del · 2018-01-06 16:07:35

What are you running in your startup files/bashrc/profile whatever that tries to start ruby? You probably have an AUR package that needs a rebuild.

lnx · 2018-01-06 16:36:19

After putting the whole traceback message in duckduckgo, I found the answer on a website cloudypoint.com:

gem update --system

anatolik · 2018-01-06 19:36:18

This error message says that long-time deprecated `-rubygems` flag is removed from `ruby` tool. If you use `ruby -rubygems` please remove the flag. Here is an example https://git.archlinux.org/svntogit/pack … c1bd432e90

Fuxy · 2018-01-08 08:29:11

Cool. Thx Inx that fixed it for me as well.

No idea what ruby program it was but it's all good as long as its fixed.

PS. The only significant thing in my .bashrc would be

# Bash path update
export PATH="${PATH}:$(ruby -rubygems -e "puts Gem.user_dir")/bin:/home/user/.composer/vendor/bin"

# Basic system stats
archey3

The path was like that to begin with so it didn't need to be updated

Last edited by Fuxy (2018-01-08 08:50:07)

anatolik · 2018-01-09 00:23:32

Fuxy wrote:

Cool. Thx Inx that fixed it for me as well.
No idea what ruby program it was but it's all good as long as its fixed.
PS. The only significant thing in my .bashrc would be
# Bash path update
export PATH="${PATH}:$(ruby -rubygems -e "puts Gem.user_dir")/bin:/home/user/.composer/vendor/bin"

# Basic system stats
archey3
The path was like that to begin with so it didn't need to be updated

Please remove `-rubygems` from you .bashrc. This flag is invalid starting with ruby 2.5.

Arch Linux

#1 2018-01-06 14:56:25

[solved] ruby traceback error after package upgrade

#2 2018-01-06 16:07:35

Re: [solved] ruby traceback error after package upgrade

#3 2018-01-06 16:36:19

Re: [solved] ruby traceback error after package upgrade

#4 2018-01-06 19:36:18

Re: [solved] ruby traceback error after package upgrade

#5 2018-01-08 08:29:11

Re: [solved] ruby traceback error after package upgrade

#6 2018-01-09 00:23:32

Re: [solved] ruby traceback error after package upgrade

Board footer