Bug 678124

Summary: [abrt] xfce4-notifyd-0.1.0-3.fc12: Process /usr/libexec/xfce4-notifyd was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: guntis
Component: xfce4-notifydAssignee: Christoph Wickert <christoph.wickert>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: christoph.wickert
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:f3469d9641e7fdadc46562b4628ff5de94a16e4e
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-02-18 11:03:34 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 guntis 2011-02-16 20:21:53 UTC 
abrt version: 1.1.14
architecture: x86_64
Attached file: backtrace
cmdline: /usr/libexec/xfce4-notifyd
component: xfce4-notifyd
executable: /usr/libexec/xfce4-notifyd
kernel: 2.6.35.11-83.fc14.x86_64
package: xfce4-notifyd-0.1.0-3.fc12
reason: Process /usr/libexec/xfce4-notifyd was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
How to reproduce: I close Midori.
time: 1297887592
uid: 500
Comment 1 guntis 2011-02-16 20:21:55 UTC 
Created attachment 479207 [details]
File: backtrace
Comment 2 guntis 2011-02-17 12:24:28 UTC 
Package: xfce4-notifyd-0.1.0-3.fc12
Architecture: x86_64
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----

I working with rdesktop and vmware. I try extra 500 MB zip file.
Comment 3 guntis 2011-02-18 10:18:40 UTC 
Package: xfce4-notifyd-0.1.0-3.fc12
Architecture: x86_64
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----

I starting Fedora
Comment 4 Christoph Wickert 2011-02-18 11:03:34 UTC 
Please do not submit the same crash over and over again. Please do not send me private messages. We need to track this down in the bug tracker, so our efforts are visbile to everybody.

Please respond to my questions in bug 668565. Thanks!

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