Bug 638648

Summary: [abrt] kadu-0.6.5.4-4.fc13: raise: Process /usr/bin/kadu was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Wojciech <telpher78>
Component: kaduAssignee: Radek Lisowski <radoslaw.lisowski>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 13CC: gajownik, radoslaw.lisowski
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: abrt_hash:3609657b0a6df7ce5b557a6f5f84b5bac7c1cf98
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-11-09 13:06:26 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 Wojciech 2010-09-29 15:22:05 UTC 
abrt version: 1.1.13
architecture: x86_64
Attached file: backtrace
cmdline: /usr/bin/kadu
comment: dont stop working  boys..its  really good things what u doing.thx
component: kadu
crash_function: raise
executable: /usr/bin/kadu
kernel: 2.6.33.3-85.fc13.x86_64
package: kadu-0.6.5.4-4.fc13
rating: 4
reason: Process /usr/bin/kadu was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)
time: 1285772638
uid: 500

How to reproduce
-----
1.ok just ended installing fedora 13

2.updated firefox ,java and yum
3.then using yum ive installed kadu
4 then i order update my new fedora
5 rebooted ,
6started kadu  eneter my numer client numer  and  passwd
7 i agree and..kadu gone...
Comment 1 Wojciech 2010-09-29 15:22:08 UTC 
Created attachment 450506 [details]
File: backtrace
Comment 2 Karel Klíč 2010-11-09 13:06:26 UTC 

*** This bug has been marked as a duplicate of bug 600736 ***
Comment 3 Karel Klíč 2010-11-09 13:06:26 UTC 
This bug appears to have been filled using a buggy version of ABRT, because
it contains a backtrace which is a duplicate of backtrace from bug #600736.

Sorry for the inconvenience.