Bug 678311 - [abrt] GConf2-2.28.1-1.fc13: __open_catalog: Process /usr/bin/gconftool-2 was killed by signal 6 (SIGABRT)
Summary: [abrt] GConf2-2.28.1-1.fc13: __open_catalog: Process /usr/bin/gconftool-2 was...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: GConf2
Version: 13
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Ray Strode [halfline]
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:f5e6062d1cbadeb65656d905366...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-02-17 14:48 UTC by Rafi Baig
Modified: 2011-06-27 12:12 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-06-27 12:12:33 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (6.65 KB, text/plain)
2011-02-17 14:48 UTC, Rafi Baig
no flags Details

Description Rafi Baig 2011-02-17 14:48:04 UTC
abrt version: 1.1.14
architecture: i686
Attached file: backtrace
cmdline: /usr/bin/gconftool-2 --shutdown
component: GConf2
crash_function: __open_catalog
executable: /usr/bin/gconftool-2
kernel: 2.6.34.7-63.fc13.i686.PAE
package: GConf2-2.28.1-1.fc13
rating: 4
reason: Process /usr/bin/gconftool-2 was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)
time: 1292282430
uid: 500

How to reproduce
-----
1. I have no idea
2.
3.

Comment 1 Rafi Baig 2011-02-17 14:48:07 UTC
Created attachment 479343 [details]
File: backtrace

Comment 2 Bug Zapper 2011-05-30 11:20:12 UTC
This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13.  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 '13'.

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 13'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 13 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 please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

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.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 3 Rafi Baig 2011-05-30 15:36:14 UTC
I have now successfully upgraded to Fedora 14 and the bug seems to have disappeared.

For your information... the problem occured only after I tried to upgrade to f14 using the preupgrade facility... the upgrade was not successful - and I encountered a number of errors and bugs. I eventually burned a cd of f14 and did a fresh install... no problems.

I suggest that this bug is not a bug in its own right, rather a consequence of an unsuccessful attempt to upgrade... perhaps there is a problem with preupgrade?

In any case I think this bug can be closed or archived... whichever you think most appropriate.

Comment 4 Bug Zapper 2011-06-27 12:12:33 UTC
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 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.


Note You need to log in before you can comment on or make changes to this bug.