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 656867 - with patch to use object path, gnome will fail to start
with patch to use object path, gnome will fail to start
Status: RESOLVED WONTFIX
Product: GConf
Classification: Deprecated
Component: gconf
3.1.x
Other Linux
: Normal major
: ---
Assigned To: GConf Maintainers
GConf Maintainers
gnome[unmaintained]
Depends on:
Blocks:
 
 
Reported: 2011-08-19 07:53 UTC by Joey Zheng
Modified: 2018-08-17 13:57 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Joey Zheng 2011-08-19 07:53:01 UTC
I am using openSUSE 12.1 and with updating gconf to 3.1.6, which uses the patch for "Bug 655656 - uses type 's' for object paths", gnome will fail to start.
If I revert the patch to use string back, gnome will start without any problems.

Probably it is caused by that g-s-d does not use the compatibility bit, but not confirmd.
Comment 1 André Klapper 2011-09-02 13:39:37 UTC
Is this still an issue in 3.1.90?
Comment 2 Joey Zheng 2011-09-03 09:26:41 UTC
I have not tested 3.1.90, but I tested 3.1.6 + git#d6f22138dc0362c706f7958bc3f42aef7af02d46, which still has the same issue.

By reading the git log, I think there is no more commits related with this issue. And I guessed that this is related with g-s-d. So I think this should still be an issue in 3.1.90.

I am afraid that I will not be able to confirm that these days, since I do not have the machine in hand now and will take a business trip in next 2 weeks.Sorry.
Comment 3 Rob Bradford 2011-09-19 15:49:51 UTC
I think the problem might be that gnome-settings-daemon is often compiled with an rpath (to get the gnome bluetooth applet library which is in a non-standard location.)

This rpath means that it can still pull in the wrong gconf from /usr/lib even if you have the library path set.
Comment 4 André Klapper 2018-08-17 13:57:17 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!