cron jobs are started by the cron daemon which is completely unrelated
to your GUI session, or any other session that might be active for the
user.
As ccooke pointed out, if you want access to an unrelated session,
you're going to have to do it manually.
** Changed in: cron (Ubuntu)
Status
This is the same issue as +bug/94933 and +bug/113988 from 2007 only with
an added ACL issue. I disagree that this is only a feature request,
this behavior used to be made to work by forcing the setting of $DISPLAY
and was broken again, this time by the X ACL(access control list). It
can again be
That's a toxic work around, this bug should stay open until the actual
problem is properly fixed.
I disagree with your assessment that this problem is an idea, the
inability to modify gconf via cron is a bug. It's never been a part of
the design of cron to be denied access to vital user space conf
Hi,
It is actually possible for programs run from cron to acquire settings
from the GUI; it's just rather arcane and tricky to make it reliable.
Making it automatic would be possible, but probably require some
additional work.
If you just want something that will work *NOW*, you can find directio
