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 configuration
based on some misconstrued security model. This bug was inconceivable,
not inappropriate.
** Changed in: cron (Ubuntu)
Status: Invalid => New
--
User Crontab is outside of GUI session
https://bugs.launchpad.net/bugs/327190
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
