Comment 11 for bug 229343

I've since upgraded our boxes here to Jaunty, and this issue has again reared its head. The solution for me was to follow the HowTo at https://help.ubuntu.com/community/ScanningHowTo , and then change the RUN_AS_USER line in /etc/default/saned such that saned runs as "root". Doesn't jive well with Ubuntu's normal security model, but it works.

That said, it's been a year since this bug was opened. If I can work around it (if somewhat insecurely) on my end with a one-word change to a single configuration file, why has it not been fixed properly? Why does this issue still persist a year later?