Description of problem: Don't know. Version-Release number of selected component: mate-notification-daemon-1.6.0-2.fc19 Additional info: reporter: libreport-2.1.5 backtrace_rating: 4 cmdline: /usr/libexec/mate-notification-daemon crash_function: g_return_if_fail_warning executable: /usr/libexec/mate-notification-daemon kernel: 3.9.8-300.fc19.x86_64 runlevel: N 5 uid: 1000 var_log_messages: Jul 10 12:10:56 tcit-pc abrt[32117]: Saved core dump of pid 32087 (/usr/libexec/mate-notification-daemon) to /var/tmp/abrt/ccpp-2013-07-10-12:10:55-32087 (21442560 bytes) xsession_errors: Truncated backtrace: Thread no. 1 (9 frames) #2 g_return_if_fail_warning at gmessages.c:1019 #3 gdk_pixbuf_new_from_data at gdk-pixbuf-data.c:60 #4 _notify_daemon_pixbuf_from_data_hint at daemon.c:971 #5 notify_daemon_notify_handler at daemon.c:1453 #6 dbus_glib_marshal_notification_daemon_VOID__STRING_UINT_STRING_STRING_STRING_BOXED_BOXED_INT_POINTER at notificationdaemon-dbus-glue.h:102 #7 invoke_object_method at dbus-gobject.c:1899 #8 object_registration_message at dbus-gobject.c:2161 #9 _dbus_object_tree_dispatch_and_unlock at dbus-object-tree.c:862 #16 gtk_main at gtkmain.c:1257 Potential duplicate: bug 953073
Created attachment 771709 [details] File: backtrace
Created attachment 771710 [details] File: cgroup
Created attachment 771711 [details] File: core_backtrace
Created attachment 771712 [details] File: dso_list
Created attachment 771714 [details] File: environ
Created attachment 771715 [details] File: limits
Created attachment 771716 [details] File: maps
Created attachment 771717 [details] File: open_fds
Created attachment 771718 [details] File: proc_pid_status
I'm pretty shure this issue was caused after updating to mate-notification-daemon-1.6.0-2.fc19. But this should not happens again. I'll leave this report open for a while, pls report here if it happens again.