Bug 575835

Summary: [abrt] crash in cssed-0.4.0-9.fc12: Process /usr/bin/cssed was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Filip Hornak <sleepy771>
Component: cssedAssignee: Thomas Janssen <thomasj>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 12CC: rafalzaq
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard: abrt_hash:33152914dbe417ac3f5c5896a7942681dbc9daa5
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-06-16 19:18:00 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 Filip Hornak 2010-03-22 14:15:50 UTC 
abrt 1.0.8 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: cssed
component: cssed
executable: /usr/bin/cssed
kernel: 2.6.32.9-70.fc12.i686
package: cssed-0.4.0-9.fc12
rating: 4
reason: Process /usr/bin/cssed was killed by signal 11 (SIGSEGV)
release: Fedora release 12 (Constantine)
Comment 1 Filip Hornak 2010-03-22 14:15:53 UTC 
Created attachment 401776 [details]
File: backtrace
Comment 2 Fedora Admin XMLRPC Client 2010-04-29 11:39:14 UTC 
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.
Comment 3 Thomas Janssen 2010-05-01 12:52:06 UTC 
Is it possible to reproduce the crash? If yes, how?
Comment 4 Thomas Janssen 2010-06-16 19:18:00 UTC 
Ok, looks like no.