Bug 1034621 - gconf-editor dumps core in certain situations
Summary: gconf-editor dumps core in certain situations
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: gconf-editor
Version: 20
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Ray Strode [halfline]
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-26 08:48 UTC by Joachim Backes
Modified: 2015-05-29 10:20 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-05-29 10:20:25 UTC
Type: Bug


Attachments (Terms of Use)

Description Joachim Backes 2013-11-26 08:48:54 UTC
Description of problem:
1. Starting gconf-editor and opening:

/desktop/gnome/shell/windows

2. Klick on some key abitrary key (theme for example)
3. Klick on the "shell" item again in the left side tree
4. Result: 

**
GConf:ERROR:gconf-client.c:2369:gconf_client_lookup: assertion failed: (last_slash != NULL)
Aborted (core dumped)


Version-Release number of selected component (if applicable):
gconf-editor-3.0.1-6.fc20.x86_64


How reproducible:
always as described

Steps to Reproduce:
1.see description
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Joachim Backes 2015-01-27 17:05:03 UTC
same in F21 with gconf-editor-3.0.1-8.fc21.x86_64

Comment 2 Fedora End Of Life 2015-05-29 09:51:25 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. 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 EOL if it remains open with a Fedora  'version'
of '20'.

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.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 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 this bug is closed as described in the policy above.

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 3 Joachim Backes 2015-05-29 10:20:25 UTC
Seems to be solved in F22


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