Original bug report at https://bugzilla.redhat.com/show_bug.cgi?id=660549 abrt version: 1.1.14 architecture: x86_64 Attached file: backtrace cmdline: /usr/lib64/xfce4/notifyd/xfce4-notifyd component: xfce4-notifyd crash_function: xfce_notify_daemon_finalize executable: /usr/lib64/xfce4/notifyd/xfce4-notifyd kernel: 2.6.37-0.rc4.git0.1.fc15.x86_64 package: xfce4-notifyd-0.2.0-1.fc14 rating: 4 reason: Process /usr/lib64/xfce4/notifyd/xfce4-notifyd was killed by signal 11 (SIGSEGV) release: Fedora release 14 (Laughlin) time: 1291695972 uid: 500 comment ----- I don't know how to duplicate this. Perhaps upstream can make something of the backtrace? How to reproduce ----- 1. was switching desktops 2. some notify might have come up, but it crashed so fast I couldn't tell what it was 3. it respawned fast enough to show the abrt trace from the crash
Created attachment 3240 backtrace of the crash
Seems to be quite common: 2 crash reports although the package is still in updates-testing. Another report of this crash at https://bugzilla.redhat.com/show_bug.cgi?id=661141 comment: Just was opening a Terminal to check cpufreq-info... Unexpected Error. How to reproduce ----- 1.Had open Add/Remove Software 2.Opened Terminal 3.Run command cpufreq-info
According to the reporters it crashes on every notification. This is almost certainly caused by libnotify 0.7.0, because on Fedora 14 it works fine.
Sadly, I am seeing this crash on f14 and have: libnotify-0.5.1-1.fc14.x86_64 so, not sure it's libnotify related.
Thank you for the bug report. I can't reproduce this and the backtrace is not very helpful, I don't get how xfce_notify_daemon_finalize can be called every time and trigger a crash: it's supposed to exit the daemon. Could you try to build xfce4-notifyd with debugging support and provide the console output of xfce4-notifyd before the crash + the backtrace of this crash? To do that, kill the current xfce4-notifyd daemon and launch a new one in a terminal with something like 'gdb /usr/lib/xfce4/notifyd/xfce4-notifyd/'. Thanks in advance!
I fixed two potential crashers in the git master branch, I would appreciate it if one of you could test this and tell me if this fixes your issues. I'm still not able to reproduce that so I need help here if you want to see this fixed. Thanks in advance!
No feedback since last release, marking this as fixed.
Sorry for not providing feedback. I consider this fixes because I didn't get this crash report again. The downstream bug in Fedora is closed, too. Thanks for your fast response on this one!