Activity log for bug #327190
Date | Who | What changed | Old value | New value | Message |
---|---|---|---|---|---|
2009-02-09 14:15:57 | Martin Owens | bug | added bug | ||
2009-02-09 17:15:04 | C. Cooke | cron: status | New | Invalid | |
2009-02-09 17:15:04 | C. Cooke | cron: statusexplanation | |||
2009-02-09 18:11:47 | Martin Owens | cron: status | Invalid | New | |
2009-02-09 18:11:47 | Martin Owens | cron: statusexplanation | 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. | ||
2011-02-08 18:34:15 | Γουργιώτης Γιώργος (aka Gourgi) | bug | added subscriber Γουργιώτης Γιώργος (aka Gourgi) | ||
2014-10-20 09:42:50 | Christian Kastner | cron (Ubuntu): status | New | Opinion | |
2014-10-20 09:43:16 | Christian Kastner | cron (Ubuntu): status | Opinion | Invalid |