Bug 980101

Summary: [abrt] mate-panel-1.6.0-3.fc17: g_logv: Process /usr/bin/mate-panel was killed by signal 5 (SIGTRAP)
Product: [Fedora] Fedora Reporter: javier del cristo <javlopez22>
Component: mate-panelAssignee: Dan Mashal <dan.mashal>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 17CC: dan.mashal, fedora, rdieter, stefano
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:0550cf2ffc7a44d563bb0cff004447456d9441e7
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-07-31 23:28:35 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

Description javier del cristo 2013-07-01 12:30:45 UTC
Description of problem:
this program don't open and I unknow what happen in this case

Version-Release number of selected component:
mate-panel-1.6.0-3.fc17

Additional info:
backtrace_rating: 4
cmdline:        mate-panel
crash_function: g_logv
executable:     /usr/bin/mate-panel
kernel:         3.9.7-100.fc17.x86_64
runlevel:       unknown
uid:            1000
ureports_counter: 1
xsession_errors: 

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 g_logv at gmessages.h:101
 #2 g_settings_set_property at gsettings.c:492
 #3 object_set_property at gobject.c:1352
 #4 g_object_constructor at gobject.c:1863
 #6 g_object_new_valist at gobject.c:1830
 #8 g_settings_new at gsettings.c:869
 #9 panel_bindings_initialise at panel-bindings.c:190
 #10 panel_bindings_set_entries at panel-bindings.c:228
 #11 type_class_init_Wm at gtype.c:2219
 #12 g_type_class_ref at gtype.c:2926

Comment 1 javier del cristo 2013-07-01 12:30:50 UTC
Created attachment 767381 [details]
File: backtrace

Comment 2 javier del cristo 2013-07-01 12:30:53 UTC
Created attachment 767382 [details]
File: cgroup

Comment 3 javier del cristo 2013-07-01 12:30:56 UTC
Created attachment 767383 [details]
File: core_backtrace

Comment 4 javier del cristo 2013-07-01 12:30:59 UTC
Created attachment 767384 [details]
File: dso_list

Comment 5 javier del cristo 2013-07-01 12:31:03 UTC
Created attachment 767385 [details]
File: environ

Comment 6 javier del cristo 2013-07-01 12:31:06 UTC
Created attachment 767386 [details]
File: limits

Comment 7 javier del cristo 2013-07-01 12:31:10 UTC
Created attachment 767387 [details]
File: maps

Comment 8 javier del cristo 2013-07-01 12:31:14 UTC
Created attachment 767388 [details]
File: open_fds

Comment 9 javier del cristo 2013-07-01 12:31:17 UTC
Created attachment 767389 [details]
File: proc_pid_status

Comment 10 javier del cristo 2013-07-01 12:31:21 UTC
Created attachment 767390 [details]
File: var_log_messages

Comment 11 Wolfgang Ulbrich 2013-07-01 12:57:03 UTC
Which program don't open?
Can you describe a little more detailed what happend?
Did this issue occurs frequently ?

Comment 12 Fedora End Of Life 2013-07-03 21:56:01 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.

Comment 13 Fedora End Of Life 2013-07-31 23:28:38 UTC
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.