I solved my problem by telling uptrack not to check gconf for network
proxy settings.
In the general case, how are cron jobs supposed to query gconf with this
new behavior? Or is that not supported?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
The uptrack cron job on my headless server started to produce this
output every 30 minutes since the upgrade to oneiric:
(process:7032): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Unable to autolaunch a dbus-daemon without a $DISPLAY for X11
I suppose this is related to this
Ping! Anything happening with this bug?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/812940
Title:
dbus behaviour change from natty to oneiric: now enables X11
autolaunch
To manage notifications