Bug 671886

Summary: [abrt] xfce4-notifyd-0.1.0-3.fc12: handle_error: Process /usr/libexec/xfce4-notifyd was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: guntis
Component: xfce4-notifydAssignee: Christoph Wickert <cwickert>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: cwickert
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:ac2f40b6e8160ef3450c2982a2d4fb8aec122586
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-01-27 02:21:31 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace none

Description guntis 2011-01-22 14:34:18 UTC 
abrt version: 1.1.14
architecture: x86_64
Attached file: backtrace
cmdline: /usr/libexec/xfce4-notifyd
component: xfce4-notifyd
crash_function: handle_error
executable: /usr/libexec/xfce4-notifyd
kernel: 2.6.35.10-74.fc14.x86_64
package: xfce4-notifyd-0.1.0-3.fc12
rating: 4
reason: Process /usr/libexec/xfce4-notifyd was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
time: 1295706143
uid: 500

How to reproduce
-----
1.
2.
3.
8
Comment 1 guntis 2011-01-22 14:34:21 UTC 
Created attachment 474736 [details]
File: backtrace
Comment 2 guntis 2011-01-26 15:40:11 UTC 
Package: xfce4-notifyd-0.1.0-3.fc12
Architecture: x86_64
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1.
2.
3.
3
Comment 3 guntis 2011-01-26 18:33:52 UTC 
Package: xfce4-notifyd-0.1.0-3.fc12
Architecture: x86_64
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1.
2.
3.
4
Comment 4 guntis 2011-01-26 20:05:46 UTC 
Package: xfce4-notifyd-0.1.0-3.fc12
Architecture: x86_64
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1.
2.
3.
5
Comment 5 Christoph Wickert 2011-01-27 02:21:31 UTC 

*** This bug has been marked as a duplicate of bug 668565 ***
Comment 6 Christoph Wickert 2011-02-23 20:32:36 UTC 

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