That doesn't get to the root of the problem. The real problem is why the OS thinks the printer is a scanner in the first place. Having Ubuntu not run xsane when a scanner is plugged in will solve the problem, but why does it even think it's a scanner? I guess the problem is not with xsane, but with whatever detects that a scanner is plugged in and then calls xsane.
-- xsane starts when printer plugged in https://bugs.launchpad.net/bugs/485667 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
