Bug 679792 - [abrt] xfce4-notifyd-0.1.1-1.fc14: handle_error: Process /usr/libexec/xfce4-notifyd was killed by signal 6 (SIGABRT)
Summary: [abrt] xfce4-notifyd-0.1.1-1.fc14: handle_error: Process /usr/libexec/xfce4-n...
Keywords:
Status: CLOSED DUPLICATE of bug 706677
Alias: None
Product: Fedora
Classification: Fedora
Component: xfce4-notifyd
Version: 14
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Christoph Wickert
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:b0a2eb2e6c475033cb442c087ce...
: 668565 671886 681523 689569 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-02-23 14:30 UTC by guntis
Modified: 2011-05-22 10:43 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2011-05-22 10:43:58 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (28.35 KB, text/plain)
2011-02-23 14:30 UTC, guntis
no flags Details

Description guntis 2011-02-23 14:30:06 UTC
abrt version: 1.1.17
architecture: x86_64
Attached file: backtrace, 29026 bytes
cmdline: /usr/libexec/xfce4-notifyd
component: xfce4-notifyd
Attached file: coredump, 2138112 bytes
crash_function: handle_error
executable: /usr/libexec/xfce4-notifyd
kernel: 2.6.35.11-83.fc14.x86_64
package: xfce4-notifyd-0.1.1-1.fc14
rating: 4
reason: Process /usr/libexec/xfce4-notifyd was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
time: 1298471105
uid: 500

How to reproduce
-----
1.
2.
3.
4

Comment 1 guntis 2011-02-23 14:30:09 UTC
Created attachment 480465 [details]
File: backtrace

Comment 2 Christoph Wickert 2011-02-23 20:26:23 UTC
Please provide more info on this crash. You are the only person who is affected by it and I cannot reproduce it.

1. What did you do when the application crashed?
2. Was there an application that tries to display a notification?
3. Can you reproduce this crash?

Comment 3 Christoph Wickert 2011-02-23 20:27:58 UTC
*** Bug 668565 has been marked as a duplicate of this bug. ***

Comment 4 Christoph Wickert 2011-02-23 20:32:36 UTC
*** Bug 671886 has been marked as a duplicate of this bug. ***

Comment 5 Christoph Wickert 2011-03-06 13:58:48 UTC
*** Bug 681523 has been marked as a duplicate of this bug. ***

Comment 6 Christoph Wickert 2011-03-06 14:02:52 UTC
Copying over the releavant info from bug 681523:

> How to reproduce: I get this bug when I changed network connection from mobile
> device (usb modem for GPRS) to LAN.

1. Does this happen every time you do this?
2. Are there other applications that crash the xfce4-notifyd?
3. Do you have GNOME's notification-deamon installed?
4. What is the output of the command 'rpm -V xfce4-notifyd'?

Comment 7 guntis 2011-03-07 08:06:04 UTC
Not every time.
No, other applications not crash.
No, I not have GNOME's notification-deamon.
output of the command 'rpm -V xfce4-notifyd':

rpm -V xfce4-notifyd
prelink: /usr/bin/xfce4-notifyd-config: at least one of file's dependencies has changed since prelinking
S.?......    /usr/bin/xfce4-notifyd-config
prelink: /usr/libexec/xfce4-notifyd: at least one of file's dependencies has changed since prelinking
S.?......    /usr/libexec/xfce4-notifyd

Comment 8 guntis 2011-03-11 10:50:38 UTC
I think problems is in "Separate X screen mode". If I use fedora with out external monitor all work correctly. If I use external monitor in "Separate X screen mode" I get error message (bug message).

Comment 9 Christoph Wickert 2011-03-21 19:53:28 UTC
*** Bug 689569 has been marked as a duplicate of this bug. ***

Comment 10 Wolfgang Ulbrich 2011-03-22 11:37:18 UTC
Package: xfce4-notifyd-0.2.1-2.fc15
Architecture: x86_64
OS Release: Fedora release 15 (Lovelock)


How to reproduce
-----
1. Downloading 4 kernel-rpms from koji with firefox
2. After the downloads ends xfce4-notifyd crashed
3. found this crashed in abrt

Comment 11 Christoph Wickert 2011-05-22 10:43:58 UTC
We still have this bug in F15 with 0.2.1. Let's track this in bug 706677 because it has the newer backtrace and more info.

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


Note You need to log in before you can comment on or make changes to this bug.