After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 147443 - tree model play can cause corruption and SEGV
tree model play can cause corruption and SEGV
Status: VERIFIED INCOMPLETE
Product: gconf-editor
Classification: Applications
Component: general
2.6.x
Other Linux
: Normal critical
: ---
Assigned To: Gconf Editor Maintainers
Gconf Editor Maintainers
Depends on:
Blocks:
 
 
Reported: 2004-07-12 19:57 UTC by Zack Cerza
Modified: 2009-08-15 18:40 UTC
See Also:
GNOME target: ---
GNOME version: 2.5/2.6


Attachments
two backtraces from gdb (728 bytes, application/x-gzip)
2004-07-12 19:58 UTC, Zack Cerza
Details

Description Zack Cerza 2004-07-12 19:57:18 UTC
Description of problem:
Unexpected feature: gconf-editor has the ability to corrupt its own
tree model.

Version-Release number of selected component (if applicable):
2.6.0

How reproducible:
Always

Steps to Reproduce:
1. Open gconf-editor.
2. Expand the /desktop/gnome node.
3. Collapse the /desktop node.
4. Expand the /desktop node. Notice that most of the nodes disappear.
5. Collapse the /desktop node.
6. Expand the /desktop node. Segfault.

  
Actual results:
Segfault.

Expected results:
Normal operation.

Additional info:
There seem to be variants of this bug. I'll do more testing and report
others as necessary.
Comment 1 Zack Cerza 2004-07-12 19:58:57 UTC
Created attachment 29477 [details]
two backtraces from gdb
Comment 2 Fernando Herrera 2004-07-12 20:06:58 UTC
Hum, when collapsing /desktop node, every child node is collapsed so you
shoudn't view /desktop/gnome contents. There was a tree corruption bug in early
2.6 version. What version are you using?.
Looking at the stack trace shows that maybe there is a problem escaping some
keys. Please can you attach the output of:
gconftool-2 -R /desktop/gnome
Comment 3 Fernando Herrera 2004-07-12 20:10:20 UTC
Oh, I've realized that you were using 2.6.0.
I think the bug you are seeing was fixed on 2.6.1 and 2.7.x series:

        * src/gconf-tree-model.c: (gconf_tree_model_free_node),
        (gconf_tree_model_clear_node), (gconf_tree_model_unref_node): Reverted
        wrong patch for #124662 . New unref code. Real Fix(tm) for
        #124662 and #136631

Please, try newer versions.
Comment 4 Zack Cerza 2004-08-15 17:16:55 UTC
Yep, you were right, I now have 2.7.1 now and it's fine. Thanks :)