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? -- saned cannot access the scanner in Hardy https://bugs.launchpad.net/bugs/229343 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
