Bug 610108

Summary: [abrt] kadu-0.6.5.2-3.fc12: begin: Process /usr/bin/kadu was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: tomek.by
Component: kaduAssignee: Radek Lisowski <radoslaw.lisowski>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 14CC: extras-orphan, gajownik
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: abrt_hash:e514cef5bdc5e9e9cdab76a07840bb863ec25c95
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-03-20 16:51:07 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 tomek.by 2010-07-01 15:11:35 UTC 
abrt version: 1.1.5
architecture: x86_64
Attached file: backtrace
cmdline: kadu
component: kadu
crash_function: begin
executable: /usr/bin/kadu
global_uuid: e514cef5bdc5e9e9cdab76a07840bb863ec25c95
kernel: 2.6.35-0.2.rc3.git0.fc14.x86_64
package: kadu-0.6.5.2-3.fc12
rating: 4
reason: Process /usr/bin/kadu was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Rawhide)
time: 1277897225
uid: 500
Comment 1 tomek.by 2010-07-01 15:11:37 UTC 
Created attachment 428467 [details]
File: backtrace
Comment 2 Fedora Admin XMLRPC Client 2010-07-28 17:19:51 UTC 
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.
Comment 3 Bug Zapper 2010-07-30 12:22:34 UTC 
This bug appears to have been reported against 'rawhide' during the Fedora 14 development cycle.
Changing version to '14'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Comment 4 abrt-bot 2012-03-20 16:51:07 UTC 
Backtrace analysis found this bug to be similar to bug #608261, closing as duplicate.

This comment is automatically generated.

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