It isn't a matter of being able to work around the problem; an experienced user can do that, I agree. As I pointed out, it's that squid not running on moving to run level 2 isn't obvious to the admin that's just made the change. It has to affect users before the admin gets to know about the problem and investigate. A bug which affects the users of the system before the admin notices, and the admin will then have to spend time investigating *why* squid isn't running, doesn't seem low priority. Working around the bug is trivial, it's the upset and work it causes before the workaround stage is reached that's the problem.
-- squid is not started on runlevel transition 1 -> 2 https://bugs.launchpad.net/bugs/561779 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs