Bug 1254807

Summary: [abrt] mate-panel: panel_toplevel_get_monitor_geometry(): mate-panel killed by SIGSEGV
Product: [Fedora] Fedora Reporter: fedora-mate-testing <fedora-mate-testing>
Component: mate-panelAssignee: Wolfgang Ulbrich <raveit65.sun>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 22CC: raveit65.sun, stefano
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/b5c8661efaa4a1326fc72b1d836c0c82b4764bee
Whiteboard: abrt_hash:d81dc36759521129b0c15b95e9e5e906f186bd58
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-04-14 10:11: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: 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 fedora-mate-testing 2015-08-18 22:37:18 UTC 
Version-Release number of selected component:
mate-panel-1.10.0-1.fc22

Additional info:
reporter:       libreport-2.5.1
backtrace_rating: 4
cmdline:        mate-panel
crash_function: panel_toplevel_get_monitor_geometry
executable:     /usr/bin/mate-panel
global_pid:     1434
kernel:         4.0.4-301.fc22.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 panel_toplevel_get_monitor_geometry at panel-toplevel.c:299
 #1 panel_toplevel_get_maximum_size at panel-toplevel.c:5738
 #2 panel_properties_dialog_update_orientation at panel-properties-dialog.c:629
 #3 panel_properties_dialog_toplevel_notify at panel-properties-dialog.c:681
 #4 g_cclosure_marshal_VOID__STRINGv at gmarshal.c:1794
 #5 _g_closure_invoke_va at gclosure.c:831
 #8 g_settings_real_change_event at gsettings.c:296
 #9 ffi_call_unix64 at ../src/x86/unix64.S:76
 #10 ffi_call at ../src/x86/ffi64.c:525
 #11 g_cclosure_marshal_generic_va at gclosure.c:1561
Comment 1 fedora-mate-testing 2015-08-18 22:37:22 UTC 
Created attachment 1064548 [details]
File: backtrace
Comment 2 fedora-mate-testing 2015-08-18 22:37:23 UTC 
Created attachment 1064549 [details]
File: cgroup
Comment 3 fedora-mate-testing 2015-08-18 22:37:25 UTC 
Created attachment 1064550 [details]
File: core_backtrace
Comment 4 fedora-mate-testing 2015-08-18 22:37:26 UTC 
Created attachment 1064551 [details]
File: dso_list
Comment 5 fedora-mate-testing 2015-08-18 22:37:28 UTC 
Created attachment 1064552 [details]
File: environ
Comment 6 fedora-mate-testing 2015-08-18 22:37:29 UTC 
Created attachment 1064553 [details]
File: limits
Comment 7 fedora-mate-testing 2015-08-18 22:37:31 UTC 
Created attachment 1064554 [details]
File: maps
Comment 8 fedora-mate-testing 2015-08-18 22:37:33 UTC 
Created attachment 1064555 [details]
File: mountinfo
Comment 9 fedora-mate-testing 2015-08-18 22:37:34 UTC 
Created attachment 1064556 [details]
File: namespaces
Comment 10 fedora-mate-testing 2015-08-18 22:37:36 UTC 
Created attachment 1064558 [details]
File: open_fds
Comment 11 fedora-mate-testing 2015-08-18 22:37:37 UTC 
Created attachment 1064559 [details]
File: proc_pid_status
Comment 12 fedora-mate-testing 2015-08-18 22:37:39 UTC 
Created attachment 1064560 [details]
File: var_log_messages
Comment 13 Wolfgang Ulbrich 2015-08-26 12:30:45 UTC 
Can you provide a valid description?
Steps to reproduce?
Did this issue occurs frequently ?
Comment 14 fedora-mate-testing 2015-08-26 20:32:51 UTC 
The issue occurred while randomly pressing right mouse button on a hidden (auto-hide preference set) panel located at the top of the screen. The report has been created automatically using the crash submission form, which appeared just after the crash. The issue does not occur frequently and I could not reproduce.
Comment 15 Wolfgang Ulbrich 2016-04-14 10:11:26 UTC 
No answer from reporter!