Bug 1038360

Could you please provide more information? How to reproduce? What did you tried to execute?

Was it http://ruby-rbot.org/ by a chance?

Yes, it is rbot. It seems to run for a while, then crash. This problem only happened after I went from Fedora 17 to Fedora 20 Beta (current with yum updates).

(In reply to Vít Ondruch from comment #2)
> Was it http://ruby-rbot.org/ by a chance?

Hello. I run the latest rbot build on Jeff's Fedora v20 server. Yes, the uptimes are like hours long and then crashes.

I don't know if it is related, but I have to run rbot like this "/usr/bin/ruby-mri launch_here.rb". Fedora v18 and earlier did not have these problems. :(

Please kindly let us know if you need more details and whatever. Jeff is the administrator. I am the rbot owner on his server with no su(do)/root access [just a bash shell account].

Oops, I meant v17 and earlier.

I'm not entirely certain if this is related, but I encountered a similar bug like this too: http://paste.geekosphere.org/BZ

Its difficult to reproduce because it really only happens after running the bot for a few hours.

Maybe related: https://www.ruby-forum.com/topic/4418915

(In reply to Ant from comment #4)
> I don't know if it is related, but I have to run rbot like this
> "/usr/bin/ruby-mri launch_here.rb". Fedora v18 and earlier did not have
> these problems. :(

In F19, we are using rubypick now, which allows to choose from several Ruby implementations. Not sure what is the issue you are referring to (why you should use ruby-mri instead of ruby), but it looks unrelated. I'd love to hear more in separate issue.

Isn't ruby-mri, just plain ruby? The rubypick option allows me to choose jruby, but I'd rather not use jruby for a bot.

$ rpm -qf /usr/bin/ruby-mri
ruby-2.0.0.353-16.fc20.x86_64
[jeffgus@beta ~]$ rpm -ql ruby
/usr/bin/erb
/usr/bin/ruby-mri
/usr/bin/testrb
/usr/share/doc/ruby
/usr/share/doc/ruby/COPYING
/usr/share/doc/ruby/COPYING.ja
/usr/share/doc/ruby/GPL
/usr/share/doc/ruby/LEGAL
/usr/share/man/man1/erb.1.gz
/usr/share/man/man1/ruby.1.gz

(In reply to Jeff Gustafson from comment #8)
MRI is always first choice for rubypick.

Another user experienced a similar problem:

Using alexandria 0.6.9-8.fc20.

Right clicked in a book in the "No leído" (to read) library and the program closed unexpectedly.

Right clicking in the same book in "My library" worked fine.

reporter:       libreport-2.1.11
backtrace_rating: 4
cmdline:        /usr/bin/ruby-mri /usr/bin/alexandria
crash_function: rb_bug
executable:     /usr/bin/ruby-mri
kernel:         3.12.6-300.fc20.x86_64
package:        ruby-2.0.0.353-16.fc20
reason:         ruby-mri killed by SIGABRT
runlevel:       N 5
type:           CCpp
uid:            1000

(In reply to Jorge Martínez López from comment #10)
Is this reproducible? Does it crash every time?

Hello Vit,

I can't make it crash now so it's not reproduceable.

Thanks!

(In reply to Vít Ondruch from comment #11)
> (In reply to Jorge Martínez López from comment #10)
> Is this reproducible? Does it crash every time?

FYI, this issue still happens on Jeff's Fedora box with rbot. :( Please kindly let us know if you want us to dig deeper.

Sorry, but without reproducer, it is hard to do anything about it. You might want to try to contact upstream directly.

(In reply to Vít Ondruch from comment #14)
> Sorry, but without reproducer, it is hard to do anything about it. You might
> want to try to contact upstream directly.

Well, it is reproducable within hours these days. Just need a way to capture the crashes for you guys.

FYI from December 2013: http://pastie.org/private/dixpe11zpq4cyryexzdeia

I think I will another screen and capture the crash to see if it is different now.

http://pastie.org/private/vctadojhvqmwgwui5obqa as well. I wished there was a way to capture all of it.

http://pastie.org/pastes/9073997/text?key=btojieih9apvw5m1eo8mg for today's crash. Each crash seems to be similiar to each other in terms of filenames.

@Ant
You can save the screen backlog using Ctrl+A :hardcopy -h <filename>

Have you actually read my post from several months ago?? Check the script from here to reproduce this bug: https://www.ruby-forum.com/topic/4418915

Matthias, thanks! I never knew screen had that before.

Interesting links of yours. I was able to reproduce it: http://pastie.org/pastes/9074099/text ... So, still no fixes or did I misread it? I am just a QA tester. :)

Also, do I still need to capture this dump from rbot?

Yes this was fixed 3 months ago: https://bugs.ruby-lang.org/issues/9168
Update ruby. Btw in my rbot branch I do support ruby up to 2.1.1: https://github.com/4poc/rbot

(In reply to Matthias Hecker from comment #21)
> Yes this was fixed 3 months ago: https://bugs.ruby-lang.org/issues/9168
> Update ruby. Btw in my rbot branch I do support ruby up to 2.1.1:
> https://github.com/4poc/rbot

Ah, hmm no newer Red Hat package since it is the same version so far even if my administrator could install it for me:
$ yum info ruby.x86_64
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
 * fedora: mirror.prgmr.com
 * rpmfusion-free: mirror.web-ster.com
 * rpmfusion-free-updates: fr2.rpmfind.net
 * rpmfusion-nonfree: mirror.web-ster.com
 * rpmfusion-nonfree-updates: mirror.web-ster.com
 * updates: mirror.prgmr.com
Installed Packages
Name        : ruby
Arch        : x86_64
Version     : 2.0.0.353
Release     : 16.fc20
Size        : 63 k
Repo        : installed
From repo   : updates-testing
Summary     : An interpreter of object-oriented scripting language
URL         : http://ruby-lang.org/
License     : (Ruby or BSD) and Public Domain
Description : Ruby is the interpreted scripting language for quick and easy
            : object-oriented programming.  It has many features to process
            : text files and to do system management tasks (as in Perl).  It is
            : simple, straight-forward, and extensible.

Maybe I can get him to use a beta package. Or else I guess I will have to wait for now. :(

(In reply to Ant from comment #22)
> (In reply to Matthias Hecker from comment #21)
> > Yes this was fixed 3 months ago: https://bugs.ruby-lang.org/issues/9168
> > Update ruby. Btw in my rbot branch I do support ruby up to 2.1.1:
> > https://github.com/4poc/rbot
> 
> Ah, hmm no newer Red Hat package since it is the same version so far even if
> my administrator could install it for me:
> $ yum info ruby.x86_64
> Loaded plugins: fastestmirror
> Loading mirror speeds from cached hostfile
>  * fedora: mirror.prgmr.com
>  * rpmfusion-free: mirror.web-ster.com
>  * rpmfusion-free-updates: fr2.rpmfind.net
>  * rpmfusion-nonfree: mirror.web-ster.com
>  * rpmfusion-nonfree-updates: mirror.web-ster.com
>  * updates: mirror.prgmr.com
> Installed Packages
> Name        : ruby
> Arch        : x86_64
> Version     : 2.0.0.353
> Release     : 16.fc20
> Size        : 63 k
> Repo        : installed
> From repo   : updates-testing
> Summary     : An interpreter of object-oriented scripting language
> URL         : http://ruby-lang.org/
> License     : (Ruby or BSD) and Public Domain
> Description : Ruby is the interpreted scripting language for quick and easy
>             : object-oriented programming.  It has many features to process
>             : text files and to do system management tasks (as in Perl).  It
> is
>             : simple, straight-forward, and extensible.
> 
> Maybe I can get him to use a beta package. Or else I guess I will have to
> wait for now. :(

Yes, there is no new package, since it was not yet released as an official release.

But, you can try Ruby 2.1.1: https://koji.fedoraproject.org/koji/buildinfo?buildID=509933

Or I can prepare patched version of Ruby 2.0.0 for you to test and if it fixes your issues, I can apply the patch into Fedora's version.

Vít Ondruch: I will have to wait for my administrator (seems to be BUSY at the moment since I haven't seen/heard him for a few weeks) to see if he wants to try that prerelease package. Is it possible to use it without root/sudo for now?

(In reply to Ant from comment #24)
Well, in theory, you could extract the library from RPM somewhere and prepend the path to LD_LIBRARY_PATH, but that could do more harm than good.

(In reply to Vít Ondruch from comment #25)
> (In reply to Ant from comment #24)
> Well, in theory, you could extract the library from RPM somewhere and
> prepend the path to LD_LIBRARY_PATH, but that could do more harm than good.

Thanks. I won't bother to try that method then. I will have to wait for the administrator then.

It is weird that rbot didn't crashed over the weekend.

This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.