[Bug 285937] Re: gconftool-2 in Intrepid not working from cron

2009-01-06 Thread Loïc Minier
The best thing to do in your crons is to source the correct file in ~/.dbus/session-bus. The layout is $(cat /var/lib/dbus/machine- id)-$DISPLAY. You could try all displays in the case of GConf. -- gconftool-2 in Intrepid not working from cron https://bugs.launchpad.net/bugs/285937 You received

[Bug 285937] Re: gconftool-2 in Intrepid not working from cron

2009-01-05 Thread Thierry Daucourt
adding the line below, inside the script that is launched by cron, solved my problem: export $(xargs -n 1 -0 echo https://bugs.launchpad.net/bugs/285937 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list deskt

[Bug 285937] Re: gconftool-2 in Intrepid not working from cron

2009-01-05 Thread kraftb
Hi ! I think it is easier to get the DBUS_SESSION_BUS_ADDRESS from: /home/myUser/.dbus/session-bus/ In this directory you find a list of files for each dbus (gnome?) session ... You could either simply "source" it or otherwise add the variables in there to your environment. -- gconftool-2 in

Re: [Bug 285937] Re: gconftool-2 in Intrepid not working from cron

2008-10-19 Thread Loïc Minier
On Sun, Oct 19, 2008, mike2357 wrote: > Thanks for the advice. I was able to capture DBUS_SESSION_BUS_ADDRESS. > Now what do I do with it so I can call gconftool-2 from cron? You set it in the env of gconftool-2. -- Loïc Minier -- gconftool-2 in Intrepid not working from cron https://bugs.la

[Bug 285937] Re: gconftool-2 in Intrepid not working from cron

2008-10-19 Thread mike2357
Thanks for the advice. I was able to capture DBUS_SESSION_BUS_ADDRESS. Now what do I do with it so I can call gconftool-2 from cron? -- gconftool-2 in Intrepid not working from cron https://bugs.launchpad.net/bugs/285937 You received this bug notification because you are a member of Ubuntu Deskt

[Bug 285937] Re: gconftool-2 in Intrepid not working from cron

2008-10-19 Thread Loïc Minier
This is related to the move of gconf from corba to DBus. Because gconf is now over the session dbus, you can't talk to it from cron. There's a way around this, which is to locate one process running in your dbus session and reading the "DBUS_SESSION_BUS_ADDRESS" env var from it; for instance: x

[Bug 285937] Re: gconftool-2 in Intrepid not working from cron

2008-10-19 Thread Sebastien Bacher
thank you for your bug report, that's not a bug though gconf just uses dbus now so it needs a session bus running, you can run the command using dbus-launch which should work correctly ** Changed in: gconf (Ubuntu) Importance: Undecided => Low Assignee: (unassigned) => Ubuntu Desktop Bugs

[Bug 285937] Re: gconftool-2 in Intrepid not working from cron

2008-10-19 Thread gnudoc
I get exactly the same result. Some background discussion at http://ubuntuforums.org/showthread.php?t=952452 ** Changed in: gconf (Ubuntu) Status: New => Confirmed -- gconftool-2 in Intrepid not working from cron https://bugs.launchpad.net/bugs/285937 You received this bug notification be

[Bug 285937] Re: gconftool-2 in Intrepid not working from cron

2008-10-19 Thread mike2357
** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/18691700/Dependencies.txt -- gconftool-2 in Intrepid not working from cron https://bugs.launchpad.net/bugs/285937 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gc