Bug 1369980

Summary: [abrt] mate-panel: mate_panel_applet_locked_change_notify(): mate-panel killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Nivag <gavinflower>
Component: mate-panelAssignee: Wolfgang Ulbrich <fedora>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 25CC: fedora, stefano
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/b558bcf3633534c059dde23fe3313abccc5387df
Whiteboard: abrt_hash:580b06cb25d4bb89f4a0b8ae2453674a5dfee5b8;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-07-15 08:32:21 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 Nivag 2016-08-24 23:23:58 UTC 
Description of problem:
just upgraded from f24 to f25, about an hour ago
I think I was trying to remove an icon from my top panel

Version-Release number of selected component:
mate-panel-1.15.0-2.fc25

Additional info:
reporter:       libreport-2.7.2
backtrace_rating: 4
cmdline:        mate-panel
crash_function: mate_panel_applet_locked_change_notify
executable:     /usr/bin/mate-panel
global_pid:     1689
kernel:         4.8.0-0.rc2.git3.1.fc25.x86_64
pkg_fingerprint: 4089 D8F2 FDB1 9C98
pkg_vendor:     Fedora Project
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 mate_panel_applet_locked_change_notify at applet.c:186
 #1 g_cclosure_marshal_VOID__STRINGv at gmarshal.c:1794
 #2 _g_closure_invoke_va at gclosure.c:867
 #5 g_settings_real_change_event at gsettings.c:386
 #6 ffi_call_unix64 at ../src/x86/unix64.S:76
 #7 ffi_call at ../src/x86/ffi64.c:525
 #8 g_cclosure_marshal_generic_va at gclosure.c:1604
 #9 _g_closure_invoke_va at gclosure.c:867
 #12 settings_backend_path_changed at gsettings.c:461
 #13 g_settings_backend_invoke_closure at gsettingsbackend.c:267

Potential duplicate: bug 1134145
Comment 1 Nivag 2016-08-24 23:24:03 UTC 
Created attachment 1193828 [details]
File: backtrace
Comment 2 Nivag 2016-08-24 23:24:04 UTC 
Created attachment 1193829 [details]
File: cgroup
Comment 3 Nivag 2016-08-24 23:24:06 UTC 
Created attachment 1193830 [details]
File: core_backtrace
Comment 4 Nivag 2016-08-24 23:24:07 UTC 
Created attachment 1193831 [details]
File: dso_list
Comment 5 Nivag 2016-08-24 23:24:08 UTC 
Created attachment 1193832 [details]
File: environ
Comment 6 Nivag 2016-08-24 23:24:09 UTC 
Created attachment 1193833 [details]
File: exploitable
Comment 7 Nivag 2016-08-24 23:24:10 UTC 
Created attachment 1193834 [details]
File: limits
Comment 8 Nivag 2016-08-24 23:24:11 UTC 
Created attachment 1193835 [details]
File: maps
Comment 9 Nivag 2016-08-24 23:24:13 UTC 
Created attachment 1193836 [details]
File: mountinfo
Comment 10 Nivag 2016-08-24 23:24:14 UTC 
Created attachment 1193837 [details]
File: namespaces
Comment 11 Nivag 2016-08-24 23:24:15 UTC 
Created attachment 1193838 [details]
File: open_fds
Comment 12 Nivag 2016-08-24 23:24:16 UTC 
Created attachment 1193839 [details]
File: proc_pid_status
Comment 13 Nivag 2016-08-24 23:24:17 UTC 
Created attachment 1193840 [details]
File: var_log_messages
Comment 14 Wolfgang Ulbrich 2017-05-16 13:14:56 UTC 
Is the issue reproducible with current stable f25?
Comment 15 Wolfgang Ulbrich 2017-07-15 08:32:21 UTC 
No answer from reporter!