Red Hat Bugzilla – Bug 591467
[abrt] crash in ruby-184.108.40.2069-1.fc12: raise: Process /usr/bin/ruby was killed by signal 6 (SIGABRT)
Last modified: 2010-05-19 11:59:52 EDT
abrt 1.0.9 detected a crash.
Attached file: backtrace
cmdline: ruby /usr/bin/alexandria
reason: Process /usr/bin/ruby was killed by signal 6 (SIGABRT)
release: Fedora release 12 (Constantine)
How to reproduce: just closing Alexandria
Created attachment 413392 [details]
It seems that this is basically the same as bug 530407.
Ah, it seems wrong, sorry...
- Is this bug reproducible even if you remove (or backup)
~/.alexandria ? If not, would you attach the whole tree
- How often is this bug reproducible? Also would you write
the needed procedure before closing alexandria to reproduce
This was a one time bug: I just opened Alexandria to check if I already registered a book: I used the filter to find it, and as it was registered, I simply quit the application, which crashed, with no apparent reason.
Furthermore, there has been an update of alexandria this week-end, so I don't know if it's useful to upload my ~/.alexandria folder (which is 7,6 Mio big, because of the pictures of the covers)
Well, the change between 0.6.6 beta1 -> 0.6.6 beta2 is mainly
to add a new provider, and the crash reported on this bug is not
the syntax errors or so in alexandria scripts but segv having
occurred in ruby itself. So the update of alexandria shouldn't
affect this issue.
By the way now ruby 220.127.116.119-3 is in testing, which contains
a bug fix for null klass issue. Would you try the testing ruby?
Shouldn't I wait for the ruby 18.104.22.1689-4 to be pushed in testing, as I see you've submitted it in Bodhi ?
-4 addressed a issue completely different from this issue
and you can try -3.
I've updated with -4 which is now the testing update. I didn't reproduced this bug, but got another one: https://bugzilla.redhat.com/show_bug.cgi?id=593746
From backtrace the crash seem to be occuring at the same place.
Once closing as a duplicate of the new one you've filed for triage.
*** This bug has been marked as a duplicate of bug 593746 ***