I'm not sure how to reply to comment #2. My sequence of commands showed that: (1) gconfd was not running at the beginning of the sequence, (2) gconftool --spawn started it properly, (3) gconftool --ping then could not find the running daemon. I'm glad that gconftool --ping works right for you, but the sequence I'm demonstrating worked well in karmic and has ceased working in lucid.
Re comment #3, regarding practical user issue, I start gconfd with "gconftool-2 --ping || gconftool-2 --spawn" in my xsession because I'm not running a full gnome setup but I want to modify some settings prior to application launch. -- gconftool-2 can't find running gconfd-2 https://bugs.launchpad.net/bugs/529577 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
