Bug 550898

Summary: [abrt] crash in ruby-1.8.6.383-4.fc12
Product: [Fedora] Fedora Reporter: mdmpsyd <mdmpsyd>
Component: rubyAssignee: Jeroen van Meeuwen <vanmeeuwen+fedora>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 12CC: jeremy, mtasaka, tagoh, vanmeeuwen+fedora
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard: abrt_hash:f1dd2fb14b0714742c887de750e5878fffc4ade5
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-12-28 16:41:36 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace none

Description mdmpsyd@gmail.com 2009-12-28 01:54:10 UTC 
abrt 1.0.0 detected a crash.

Attached file: backtrace
cmdline: ruby /usr/bin/alexandria
component: ruby
executable: /usr/bin/ruby
kernel: 2.6.31.9-174.fc12.i686.PAE
package: ruby-1.8.6.383-4.fc12
rating: 4
reason: Process was terminated by signal 6 (Aborted)
Comment 1 mdmpsyd@gmail.com 2009-12-28 01:54:13 UTC 
Created attachment 380579 [details]
File: backtrace
Comment 2 Mamoru TASAKA 2009-12-28 15:18:04 UTC 
Is this the same as bug 550868?
Comment 3 mdmpsyd@gmail.com 2009-12-28 16:13:08 UTC 
In all likelihood, yes. By that time I was not reporting individual crashes and waited until I was done to do the reporting. ABRT lumped many together and kept separate some that I thought were duplicates. But I can not say with certainty which crash report went with what event.
Comment 4 Mamoru TASAKA 2009-12-28 16:41:36 UTC 
Thank you, once closing.

*** This bug has been marked as a duplicate of bug 550868 ***