abrt 1.0.0 detected a crash. Attached file: backtrace cmdline: /usr/libexec/notification-daemon component: notification-daemon executable: /usr/libexec/notification-daemon kernel: 2.6.31.5-127.fc12.i686.PAE package: notification-daemon-0.4.1-0.20090923.4.fc12 rating: 4 reason: Process was terminated by signal 6
Created attachment 375273 [details] File: backtrace
Looks like a problem with NimbusRcStyle
Mark, what version of nimbus are you running? rpm -q nimbus
I don't have that package installed (not 100% sure I didn't remove it).
Ah, sorry, that was the name of the source package, the binaries have a different name. rpm -q nimbus-icon-theme nimbus-theme-gnome gtk-nimbus-engine
[mark@Fedora ~]$ rpm -q nimbus-icon-theme nimbus-theme-gnome gtk-nimbus-engine nimbus-icon-theme-0.1.4-2.fc12.noarch nimbus-theme-gnome-0.1.4-2.fc12.noarch gtk-nimbus-engine-0.1.4-2.fc12.i686
Thanks, but I need some more info: When did the crash happen? There was the update to nimbus 0.1.4 yesterday, so was the crash before or after that? Use rpm -qa --last | grep nimbus to find out if/when it was installed). And if the crash was with 0.1.4, then I need a new backtrace with the nimbus-debuginfo packages installed. Somehow the package is not in the repo, download it from https://koji.fedoraproject.org/koji/buildinfo?buildID=142499 Make sure to select the right arch, i686 or x86_64
I can not get into https://koji.fedoraproject.org/koji/buildinfo?buildID=142499 : An error occurred during a connection to koji.fedoraproject.org. SSL peer was unable to negotiate an acceptable set of security parameters. (Error code: ssl_error_handshake_failure_alert) The ABRT gui reports the last crash at 7:03 pm yesterday which seems to be before I updated [mark@Fedora ~]$ rpm -qa --last | grep nimbus nimbus-theme-gnome-0.1.4-2.fc12 Tue 01 Dec 2009 07:30:51 PM EST nimbus-icon-theme-0.1.4-2.fc12 Tue 01 Dec 2009 07:29:17 PM EST nimbus-metacity-theme-0.1.4-2.fc12 Tue 01 Dec 2009 07:27:30 PM EST gtk-nimbus-engine-0.1.4-2.fc12 Tue 01 Dec 2009 07:24:16 PM EST I copied all the crash reports from /var/log/abrt-logger into a text file but they appear to be from the previous version (notification-daemon-0.4.1-0.20090923.4.fc12) let me know if you want that information. Has anyone considered including a time and date field in the ABRTd so we can know when the crash occurred? Or maybe it's there and I can't find it.
(In reply to comment #8) > I can not get into https://koji.fedoraproject.org/koji/buildinfo?buildID=142499 Try http then: http://koji.fedoraproject.org/koji/buildinfo?buildID=142499 > I copied all the crash reports from /var/log/abrt-logger into a text file but > they appear to be from the previous version > (notification-daemon-0.4.1-0.20090923.4.fc12) let me know if you want that > information. Thanks, but without the necessary debuginfo its pretty useless. I'm going to close this bug now because three people confirmed the problem is fixed with the new version. The old version had a reference to a notification-engine that doesn't exist, but I have fixed this in the new version so there is absolutely no connection from the theme to the daemon. > Has anyone considered including a time and date field in the ABRTd so we can > know when the crash occurred? Good catch. There is a timestamp, you can see it in the abrt tool, but it's not in the info that is submitted. If you ever happen to see the crash again, please install the debuginfo before you submit the bug. Thanks for your report. *** This bug has been marked as a duplicate of bug 536993 ***