Bug 668565 - [abrt] xfce4-notifyd-0.1.0-3.fc12: handle_error: Process /usr/libexec/xfce4-notifyd was killed by signal 6 (SIGABRT)
Summary: [abrt] xfce4-notifyd-0.1.0-3.fc12: handle_error: Process /usr/libexec/xfce4-n...
Keywords:
Status: CLOSED DUPLICATE of bug 679792
Alias: None
Product: Fedora
Classification: Fedora
Component: xfce4-notifyd
Version: 14
Hardware: x86_64
OS: Unspecified
low
medium
Target Milestone: ---
Assignee: Christoph Wickert
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:1bf0235d3c84a7f22ab88a90fa2...
: 678124 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-01-10 19:47 UTC by guntis
Modified: 2011-02-23 20:27 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-02-23 20:27:58 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (26.98 KB, text/plain)
2011-01-10 19:47 UTC, guntis 		no flags Details
View All

Description guntis 2011-01-10 19:47:37 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: 1294687085
uid: 500

How to reproduce
-----
1.
2.
3.
3 time
Comment 1 guntis 2011-01-10 19:47:39 UTC 
Created attachment 472674 [details]
File: backtrace
Comment 2 guntis 2011-01-19 09:44:04 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 3 Christoph Wickert 2011-01-27 02:21:31 UTC 
*** Bug 671886 has been marked as a duplicate of this bug. ***
Comment 4 Christoph Wickert 2011-01-27 02:25:44 UTC 
Thanks for submitting this bug report. Please provide more info.

1. What did you do when the application crashed?
2. Can you reproduce the crash reliably?
3. What application was it that sent a notification to the notification-daemon?
Comment 5 guntis 2011-01-28 11:06: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.
11
Comment 6 Christoph Wickert 2011-01-28 14:13:31 UTC 
Please tell me more about the crash instead of submitting the same report over and over again. Thanks!
Comment 7 Fedora Update System 2011-02-02 22:54:36 UTC 
xfce4-notifyd-0.2.0-1.fc14 has been submitted as an update for Fedora 14.
https://admin.fedoraproject.org/updates/xfce4-notifyd-0.2.0-1.fc14
Comment 8 Christoph Wickert 2011-02-02 22:57:28 UTC 
Sorry, the correct update is
https://admin.fedoraproject.org/updates/xfce4-notifyd-0.1.1-1.fc14
Comment 9 guntis 2011-02-15 17:13:28 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 10 Christoph Wickert 2011-02-18 11:03:34 UTC 
*** Bug 678124 has been marked as a duplicate of this bug. ***
Comment 11 Christoph Wickert 2011-02-18 11:10:31 UTC 
Please try the update from https://admin.fedoraproject.org/updates/xfce4-notifyd-0.1.1-1.fc14
Comment 12 Christoph Wickert 2011-02-21 09:07:45 UTC 
To install this update you need to enable the updates-testing repo. You can do this with the command

yum --enablerepo=updates-testing update xfce4-notifyd
Comment 13 Fedora Update System 2011-02-22 04:55:44 UTC 
xfce4-notifyd-0.1.1-1.fc14 has been pushed to the Fedora 14 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update xfce4-notifyd'.  You can provide feedback for this update here: https://admin.fedoraproject.org/updates/xfce4-notifyd-0.1.1-1.fc14
Comment 14 Christoph Wickert 2011-02-23 20:27:58 UTC 

*** This bug has been marked as a duplicate of bug 679792 ***
Note You need to log in before you can comment on or make changes to this bug.