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 533494 - gconftool-2 now only works under X
gconftool-2 now only works under X
Status: RESOLVED FIXED
Product: GConf
Classification: Deprecated
Component: gconf
CVS HEAD
Other Linux
: Normal major
: ---
Assigned To: GConf Maintainers
GConf Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-05-16 22:19 UTC by Kjartan Maraas
Modified: 2008-05-21 18:56 UTC
See Also:
GNOME target: ---
GNOME version: 2.23/2.24


Description Kjartan Maraas 2008-05-16 22:19:34 UTC 
After the dbus changes went in recently you can no longer use gconftool-2 on the console.
Comment 1 Ray Strode [halfline] 2008-05-17 03:50:40 UTC 
So the available options that I can think of are:

1) assume --direct if there's no session bus
2) launch our own bus if there isn't one running
3) back out the patch and use kernel keyring instead
4) back out the patch and reopen the bugs it fixes

2 is pretty bogus because it effectively does 1 in a round about way.  3 is only going to work on linux.  4 is an option but it's still early in the devel cycle so I'd like to avoid it for now.

That means 1 is looking like the best bet.
Comment 2 Ray Strode [halfline] 2008-05-21 18:56:59 UTC 
This should be set in trunk.

2008-05-21  Ray Strode  <rstrode@redhat.com>

        * gconf/gconftool.c (main): Fall back to local
        database access if not in active session. (bug 533494)

        * gconf/gconf-internals.c (get_ior):
        Don't bother trying to autolaunch bus if DISPLAY isn't
        set.