Bug 953073

Summary: [abrt] mate-notification-daemon-1.5.1-1.fc18: g_return_if_fail_warning: Process /usr/libexec/mate-notification-daemon was killed by signal 5 (SIGTRAP)
Product: [Fedora] Fedora Reporter: gwir <gilles.renault>
Component: mate-notification-daemonAssignee: Dan Mashal <dan.mashal>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: alihosseini65, dan.mashal, raveit65.sun, rdieter, stefano
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:b21b7d8f7f315f89660f439d219aa7b3a8839f47
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-07-06 18:58:11 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: xsession_errors none

Description gwir 2013-04-17 09:52:43 UTC 
Version-Release number of selected component:
mate-notification-daemon-1.5.1-1.fc18

Additional info:
backtrace_rating: 4
cmdline:        /usr/libexec/mate-notification-daemon
crash_function: g_return_if_fail_warning
executable:     /usr/libexec/mate-notification-daemon
kernel:         3.8.6-203.fc18.x86_64
uid:            1000
ureports_counter: 12
var_log_messages: Apr 17 11:05:38 k-cri-017 abrt[14009]: Saved core dump of pid 13989 (/usr/libexec/mate-notification-daemon) to /var/tmp/abrt/ccpp-2013-04-17-11:05:37-13989 (34627584 bytes)

Truncated backtrace:
Thread no. 1 (9 frames)
 #2 g_return_if_fail_warning at gmessages.c:1012
 #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
Comment 1 gwir 2013-04-17 09:52:46 UTC 
Created attachment 736756 [details]
File: backtrace
Comment 2 gwir 2013-04-17 09:52:49 UTC 
Created attachment 736757 [details]
File: cgroup
Comment 3 gwir 2013-04-17 09:52:51 UTC 
Created attachment 736758 [details]
File: core_backtrace
Comment 4 gwir 2013-04-17 09:52:53 UTC 
Created attachment 736759 [details]
File: dso_list
Comment 5 gwir 2013-04-17 09:52:56 UTC 
Created attachment 736760 [details]
File: environ
Comment 6 gwir 2013-04-17 09:52:58 UTC 
Created attachment 736761 [details]
File: limits
Comment 7 gwir 2013-04-17 09:53:01 UTC 
Created attachment 736762 [details]
File: maps
Comment 8 gwir 2013-04-17 09:53:04 UTC 
Created attachment 736763 [details]
File: open_fds
Comment 9 gwir 2013-04-17 09:53:07 UTC 
Created attachment 736764 [details]
File: proc_pid_status
Comment 10 gwir 2013-04-17 09:53:09 UTC 
Created attachment 736765 [details]
File: xsession_errors
Comment 11 Wolfgang Ulbrich 2013-06-29 14:47:08 UTC 
Can you describe a little more detailed what's happend?
Does this error ocours frequently?