Bug 951748

Summary: [abrt] mate-panel-1.5.6-1.fc18: g_type_check_instance_cast: Process /usr/bin/mate-panel was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Randy <derstaz>
Component: mate-panelAssignee: Dan Mashal <dan.mashal>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: dan.mashal, glad08, raveit65.sun, rdieter, stefano
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:ac350925b3a11ca503a647a6b2ee7809ebc5df0e
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-07-09 08:40:22 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: var_log_messages
none
File: xsession_errors none

Description Randy 2013-04-13 00:43:15 UTC 
Description of problem:
deleted  bottom panel

Version-Release number of selected component:
mate-panel-1.5.6-1.fc18

Additional info:
backtrace_rating: 4
cmdline:        mate-panel
crash_function: g_type_check_instance_cast
executable:     /usr/bin/mate-panel
kernel:         3.8.6-203.fc18.x86_64
uid:            1000
ureports_counter: 1

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 g_type_check_instance_cast at gtype.c:3992
 #1 tasklist_update at window-list.c:71
 #2 display_all_workspaces_changed at window-list.c:229
 #3 g_cclosure_marshal_VOID__STRINGv at gmarshal.c:1004
 #4 _g_closure_invoke_va at gclosure.c:840
 #7 g_settings_real_change_event at gsettings.c:288
 #8 ffi_call_unix64 at ../src/x86/unix64.S:75
 #9 ffi_call at ../src/x86/ffi64.c:486
 #10 g_cclosure_marshal_generic_va at gclosure.c:1550
 #11 _g_closure_invoke_va at gclosure.c:840
Comment 1 Randy 2013-04-13 00:43:18 UTC 
Created attachment 735057 [details]
File: backtrace
Comment 2 Randy 2013-04-13 00:43:19 UTC 
Created attachment 735058 [details]
File: cgroup
Comment 3 Randy 2013-04-13 00:43:21 UTC 
Created attachment 735059 [details]
File: core_backtrace
Comment 4 Randy 2013-04-13 00:43:22 UTC 
Created attachment 735060 [details]
File: dso_list
Comment 5 Randy 2013-04-13 00:43:24 UTC 
Created attachment 735061 [details]
File: environ
Comment 6 Randy 2013-04-13 00:43:25 UTC 
Created attachment 735062 [details]
File: limits
Comment 7 Randy 2013-04-13 00:43:27 UTC 
Created attachment 735063 [details]
File: maps
Comment 8 Randy 2013-04-13 00:43:29 UTC 
Created attachment 735064 [details]
File: open_fds
Comment 9 Randy 2013-04-13 00:43:30 UTC 
Created attachment 735065 [details]
File: proc_pid_status
Comment 10 Randy 2013-04-13 00:43:32 UTC 
Created attachment 735066 [details]
File: var_log_messages
Comment 11 Randy 2013-04-13 00:43:33 UTC 
Created attachment 735067 [details]
File: xsession_errors
Comment 12 glad08 2013-04-29 12:04:05 UTC 
Delete panel from mate desktop. Panel was with only workspace switcher and nothing else. After deleting crash happens.
I try to add empty panel again, then add workspace switcher on it and then delete panel, crash happens again.

backtrace_rating: 4
cmdline:        mate-panel
crash_function: g_type_check_instance_cast
executable:     /usr/bin/mate-panel
kernel:         3.8.9-200.fc18.x86_64
package:        mate-panel-1.5.6-1.fc18
reason:         Process /usr/bin/mate-panel was killed by signal 11 (SIGSEGV)
uid:            1000
ureports_counter: 2
Comment 13 Wolfgang Ulbrich 2013-07-08 15:53:26 UTC 
Did this issue still exits with a updated MATE desktop, we're are on 1.6.x ?
Comment 14 glad08 2013-07-09 08:27:03 UTC 
mate-panel-1.6.0-3.fc18.x86_64
This issue went away now.
Comment 15 Wolfgang Ulbrich 2013-07-09 08:40:22 UTC 
Thank you for giving feedback, i'm glad to hear that the issue is gone.
If it happens again i will re-open the report.