GNOME Bugzilla – Bug 77121
gconf error when editing non-leaf category
Last modified: 2004-12-22 21:47:04 UTC
Launch the "File types and Internet Services" control panel (gnome2-file-types-properties) and double click on "Documents". An error dialog appears reporting: An error occurred while loading or saving configuration information for gnome2-file-types-properties. Some of your configuration settings may not work properly. The "Details" button reveals: Bad key or directory name: "/desktop/gnome/file-types-categories//Documents/default-action-id": Can't have two slashes (/) in a row Any non-leaf category yields a similar error. Each error appears only once, though: the second time you try to edit the same category, there is no error. However, if you close and relaunch the control panel, you're back to getting errors again.
Updating all cc bugs that have the GNOME2 keyword set to the GNOME2.0 milestone, to help jrb triage/prioritize cc bugs. Filter on 'luis doing GNOME2 work' to ignore this spam.
I recall this being talked about; is it fixed in CVS?
Fixed a while ago.
On 2002-04-16, Jody Goldberg said this had been fixed "a while ago". But I'm using Ximian's 2002-04-19 snapshot, and the bug is still present. Is there any reason I shouldn't reopen this bug?
The executable is no longer called gnome2-... just gnome-... make sure you don't have stale files hanging around. You may also just have some bogus data in your mime directory as a result of previously fixed bugs.
I have no stale files lying around; the executable has been renamed but the bug is still there. I can reproduce the bug easily and consistently using a test account with an empty home directory, so this is not just a matter of bogus data in my mime directory as a result of previously fixed bugs. Jody's not crazy, but neither am I. If the bug was supposed to have been fixed long ago, perhaps the change got lost or unapplied somewhere along the line? Perhaps it was applied on a different branch?
Try wiping your ~/.gnome/mime-info There was a bug that would spew random memory into some of the fields in there.
Crud in ~/.gnome/mime-info is not the problem. As I wrote earlier, I can reproduce the bug easily and consistently using a test account with an *empty home directory*.
I can still replicate this with the most recent Ximian snapshot (7 May) on Red Hat 7.2, and like Ben, there's nothing in my ~/.gnome/mime-info. What's more, Frederic Crozat is reporting the problem on Mandrake cooker as well. I'm going to reopen this bug just to be safe. Please corner me on IRC or something if there's anything I can do to help track this problem down.
*** Bug 81025 has been marked as a duplicate of this bug. ***
I still can not replicate this. Please grab me on irc (jody on irc.gnome.org)
This appears to be a compiler bug in gcc 2.96. Jacob has a small test case that replicates the problem when compiled with optimization.
Golly. Nice sleuthing! So if this is RESOLVED/FIXED, what is the fix? Has the source been changed to avoid the bug? Have the configure scripts been changed to detect bad gcc versions and refuse to use them?
i just checked in a simple workaround. this affects at least red hat 7.2 and 7.3, so it's easiest to just work around. 2002-05-10 jacob berkman <jacob@ximian.com> * mime-type-info.c (mime_category_info_get_full_description): (mime_category_info_get_full_name): work around a gcc 2.96 bug (fixes #77121)
Verified as fixed in control-center2-1.99.10.0.200205240531-0.snap.ximian.1. Thanks!