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 583326 - GConf broken for panel applets
GConf broken for panel applets
Status: RESOLVED WONTFIX
Product: GConf
Classification: Deprecated
Component: gconf
unspecified
Other Linux
: Normal major
: ---
Assigned To: GConf Maintainers
GConf Maintainers
gnome[unmaintained]
Depends on:
Blocks:
 
 
Reported: 2009-05-20 12:30 UTC by Vincent Untz
Modified: 2018-08-17 13:56 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Vincent Untz 2009-05-20 12:30:48 UTC
When smoketesting 2.26.2, I found out that GConf 2.26.1 and 2.26.2 are broken for panel applets: they don't see the default values anymore.

It worked fine in 2.26.0.
Comment 1 Vincent Untz 2009-05-20 12:42:02 UTC
So, I have a libpanel-applet patch sitting around that has the side-effect of working around the issue. I'll do a panel release with it, I guess.

FWIW, I believe the issue is something like this:

 + preload a directory
 + create a new key in this directory by associating it with a schema
 + try to access the key. GConf probably believes it's cached, but finds nothing

My patch probably makes this work because there's a gconf_client_unset() call that will empty the cache for this key.

Still an issue with gconf, though.
Comment 2 Mike Auty 2009-06-02 17:21:55 UTC
Hiya, I think that bug 582865 might be a duplicate of this.  Could someone take a look and let us know if it's linked or not?  I'm happy to run any other tests or answer questions that might help determine if it's the same bug...
Comment 3 Francisco Pina Martins 2009-06-02 19:06:39 UTC
It does look like the same issue.

Just posted to say I'm willing to test anything you need me to as well.
Comment 4 Mike Auty 2009-06-16 21:01:39 UTC
Vincent, you mentioned a patch, is this available anywhere for testing?

Also, is there anything we can do to help track down the problem (git/svn -bisect for instance)?  Would creating a small test-case be useful?  It appears easy to create a reproducible segfault using the hardware-monitor applet, if that makes identifying the underlying problem simpler?

Please do let us know if we can help in any way...
Comment 5 Vincent Untz 2009-06-16 21:12:50 UTC
(In reply to comment #4)
> Vincent, you mentioned a patch, is this available anywhere for testing?

I mentioned a libpanel-applet patch to work around the issue in gnome-panel. It's in gnome-panel 2.26.2.
Comment 6 Mike Auty 2009-06-16 21:17:17 UTC
Ah cool, ok.  I've got gnome-panel-2.26.2 but am still experiencing the crashes in hardware-monitor (bug 582865), so I guess it's either a different bug, or they're not using libpanelapplet to do their gconf accesses...  5:(
Comment 7 Francisco Pina Martins 2009-06-17 08:31:06 UTC
I'm using gnome-panel 2.26.2-1 (Arch Linux) and I can confirm that hardware-monitor is still crashing.

So it must be a different bug after all...

I remember having some problems with compiling an older version that were related to libpanelapplet, so it is being used.

Maybe we should contact the author and ask him directly?
Comment 8 André Klapper 2018-08-17 13:56:59 UTC
GConf has been deprecated since 2011.

GConf is not under active development anymore. Its codebase has been archived:
https://gitlab.gnome.org/Archive/gconf/commits/master

dconf and gsettings are its successors. See https://developer.gnome.org/gio/stable/ch34.html and https://developer.gnome.org/GSettings/ for porting info.

Closing this report as WONTFIX as part of Bugzilla Housekeeping to reflect
reality. Feel free to open a task in GNOME Gitlab if the issue described in this task still applies to a recent + supported version of dconf/gsettings. Thanks!