Bug 1026832

Summary: [abrt] mate-notification-daemon-1.6.0-2.fc19: _dbus_string_free: Process /usr/libexec/mate-notification-daemon was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Brian J. Murrell <brian>
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: 19CC: dan.mashal, fedora, rdieter, stefano
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:abfda543af48f1f590449f79db3f32136e6cda58
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-12-29 09:18:26 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: exploitable
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Brian J. Murrell 2013-11-05 13:57:45 UTC 
Version-Release number of selected component:
mate-notification-daemon-1.6.0-2.fc19

Additional info:
reporter:       libreport-2.1.8
backtrace_rating: 4
cmdline:        /usr/libexec/mate-notification-daemon
crash_function: _dbus_string_free
executable:     /usr/libexec/mate-notification-daemon
kernel:         3.11.6-200.fc19.x86_64
runlevel:       N 5
type:           CCpp
uid:            1001

Truncated backtrace:
Thread no. 1 (6 frames)
 #1 _dbus_string_free at dbus-string.c:249
 #2 _dbus_header_free at dbus-marshal-header.c:477
 #3 dbus_message_finalize at dbus-message.c:1112
 #4 dbus_message_cache_or_finalize at dbus-message.c:716
 #5 dbus_message_unref at dbus-message.c:1629
 #12 gtk_main at gtkmain.c:1257
Comment 1 Brian J. Murrell 2013-11-05 13:57:49 UTC 
Created attachment 819762 [details]
File: backtrace
Comment 2 Brian J. Murrell 2013-11-05 13:57:53 UTC 
Created attachment 819763 [details]
File: cgroup
Comment 3 Brian J. Murrell 2013-11-05 13:57:56 UTC 
Created attachment 819764 [details]
File: core_backtrace
Comment 4 Brian J. Murrell 2013-11-05 13:58:00 UTC 
Created attachment 819765 [details]
File: dso_list
Comment 5 Brian J. Murrell 2013-11-05 13:58:06 UTC 
Created attachment 819766 [details]
File: environ
Comment 6 Brian J. Murrell 2013-11-05 13:58:10 UTC 
Created attachment 819767 [details]
File: exploitable
Comment 7 Brian J. Murrell 2013-11-05 13:58:14 UTC 
Created attachment 819768 [details]
File: limits
Comment 8 Brian J. Murrell 2013-11-05 13:58:20 UTC 
Created attachment 819769 [details]
File: maps
Comment 9 Brian J. Murrell 2013-11-05 13:58:24 UTC 
Created attachment 819770 [details]
File: open_fds
Comment 10 Brian J. Murrell 2013-11-05 13:58:28 UTC 
Created attachment 819771 [details]
File: proc_pid_status
Comment 11 Brian J. Murrell 2013-11-05 13:58:35 UTC 
Created attachment 819772 [details]
File: var_log_messages
Comment 12 Wolfgang Ulbrich 2013-11-11 09:59:22 UTC 
Can you describe a little more detailed what happend?
Did this issue occurs frequently ?
Comment 13 Brian J. Murrell 2013-11-11 14:38:54 UTC 
Unfortunately I don't know what caused this.  It was just a crash I found in the abrt GUI.