Bug 956579

Summary: [abrt] mate-panel-1.5.6-1.fc17: g_type_check_instance_cast: Process /usr/bin/mate-panel was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: cqi
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: 17CC: dan.mashal, raveit65.sun, rdieter, stefano
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:59f44580f2ad3eb84429215a922dc6e4176276c3
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-07-08 12:42:23 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: smolt_data
none
File: var_log_messages
none
File: xsession_errors none

Description cqi 2013-04-25 09:02:46 UTC
Version-Release number of selected component:
mate-panel-1.5.6-1.fc17

Additional info:
backtrace_rating: 4
cmdline:        mate-panel
crash_function: g_type_check_instance_cast
executable:     /usr/bin/mate-panel
kernel:         3.8.4-102.fc17.x86_64
uid:            1000
ureports_counter: 1

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 g_type_check_instance_cast at gtype.c:4000
 #1 pager_update at workspace-switcher.c:89
 #2 all_workspaces_changed at workspace-switcher.c:415
 #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 cqi 2013-04-25 09:02:51 UTC
Created attachment 739732 [details]
File: backtrace

Comment 2 cqi 2013-04-25 09:02:58 UTC
Created attachment 739733 [details]
File: cgroup

Comment 3 cqi 2013-04-25 09:03:01 UTC
Created attachment 739734 [details]
File: core_backtrace

Comment 4 cqi 2013-04-25 09:03:05 UTC
Created attachment 739735 [details]
File: dso_list

Comment 5 cqi 2013-04-25 09:03:08 UTC
Created attachment 739736 [details]
File: environ

Comment 6 cqi 2013-04-25 09:03:12 UTC
Created attachment 739737 [details]
File: limits

Comment 7 cqi 2013-04-25 09:03:14 UTC
Created attachment 739738 [details]
File: maps

Comment 8 cqi 2013-04-25 09:03:18 UTC
Created attachment 739739 [details]
File: open_fds

Comment 9 cqi 2013-04-25 09:03:21 UTC
Created attachment 739740 [details]
File: proc_pid_status

Comment 10 cqi 2013-04-25 09:03:24 UTC
Created attachment 739741 [details]
File: smolt_data

Comment 11 cqi 2013-04-25 09:03:27 UTC
Created attachment 739742 [details]
File: var_log_messages

Comment 12 cqi 2013-04-25 09:03:30 UTC
Created attachment 739743 [details]
File: xsession_errors

Comment 13 Wolfgang Ulbrich 2013-06-29 14:43:07 UTC
Can you describe a little more detailed what's happend?
Does this error ocours frequently?

Comment 14 Fedora End Of Life 2013-07-03 21:55:52 UTC
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '17'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 17's end of life.

Bug Reporter:  Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 17 is end of life. If you 
would still like  to see this bug fixed and are able to reproduce it 
against a later version  of Fedora, you are encouraged  change the 
'version' to a later Fedora version prior to Fedora 17's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.