Bug 1306108

Summary: [abrt] mate-disk-usage-analyzer: baobab_ringschart_set_subfoldertips_enabled(): mate-disk-usage-analyzer killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Yonatan <yonatan.el.amigo>
Component: mate-utilsAssignee: Wolfgang Ulbrich <fedora>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 23CC: fedora, stefano
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/5997670d8a0ced2294a9ddf555f5ab4328edc403
Whiteboard: abrt_hash:71c59deb73e35e1845fc7a12fe584b8a0b95cab5;VARIANT_ID=workstation;
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-08-13 09:19:46 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
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: mountinfo
none
File: namespaces
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Yonatan 2016-02-10 02:58:54 UTC 
Version-Release number of selected component:
mate-disk-usage-analyzer-1.12.0-1.fc23

Additional info:
reporter:       libreport-2.6.3
backtrace_rating: 4
cmdline:        mate-disk-usage-analyzer
crash_function: baobab_ringschart_set_subfoldertips_enabled
executable:     /usr/bin/mate-disk-usage-analyzer
global_pid:     14655
kernel:         4.1.6-201.fc22.i686
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 baobab_ringschart_set_subfoldertips_enabled at baobab-ringschart.c:672
 #1 baobab_settings_subfoldertips_changed at baobab.c:719
 #2 g_cclosure_marshal_VOID__STRINGv at gmarshal.c:1794
 #3 _g_closure_invoke_va at gclosure.c:864
 #6 g_settings_real_change_event at gsettings.c:386
 #7 ffi_call_SYSV at ../src/x86/sysv.S:65
 #8 ffi_call at ../src/x86/ffi.c:382
 #9 g_cclosure_marshal_generic_va at gclosure.c:1600
 #10 g_type_class_meta_marshalv at gclosure.c:1021
 #11 _g_closure_invoke_va at gclosure.c:864
Comment 1 Yonatan 2016-02-10 02:59:03 UTC 
Created attachment 1122630 [details]
File: backtrace
Comment 2 Yonatan 2016-02-10 02:59:06 UTC 
Created attachment 1122631 [details]
File: cgroup
Comment 3 Yonatan 2016-02-10 02:59:10 UTC 
Created attachment 1122632 [details]
File: core_backtrace
Comment 4 Yonatan 2016-02-10 02:59:14 UTC 
Created attachment 1122633 [details]
File: dso_list
Comment 5 Yonatan 2016-02-10 02:59:32 UTC 
Created attachment 1122634 [details]
File: environ
Comment 6 Yonatan 2016-02-10 03:00:10 UTC 
Created attachment 1122635 [details]
File: exploitable
Comment 7 Yonatan 2016-02-10 03:01:48 UTC 
Created attachment 1122636 [details]
File: limits
Comment 8 Yonatan 2016-02-10 03:01:59 UTC 
Created attachment 1122637 [details]
File: maps
Comment 9 Yonatan 2016-02-10 03:02:14 UTC 
Created attachment 1122638 [details]
File: mountinfo
Comment 10 Yonatan 2016-02-10 03:02:35 UTC 
Created attachment 1122639 [details]
File: namespaces
Comment 11 Yonatan 2016-02-10 03:02:49 UTC 
Created attachment 1122640 [details]
File: open_fds
Comment 12 Yonatan 2016-02-10 03:03:13 UTC 
Created attachment 1122641 [details]
File: proc_pid_status
Comment 13 Yonatan 2016-02-10 03:03:45 UTC 
Created attachment 1122642 [details]
File: var_log_messages
Comment 14 Wolfgang Ulbrich 2016-04-14 10:32:16 UTC 
Can you provide a valid description?
Steps to reproduce?
Did this issue occurs frequently ?
Is the problem still exists with the latest updates?
Comment 15 Wolfgang Ulbrich 2016-08-13 09:19:46 UTC 
Sadly no answer from reporter!