New idea regarding why scanner does not work: It may not have anything to do with kernel. Just a thought:
I tried to access cups through its built-in web interface (http://localhost:631), and it is not accessible in 13.04. If I go to my 12.04 installation (same machine, same hard drive, different boot) http://localhost:631 comes up without any problem. As I mentioned before, the scanner works on 12.04 and it does not work on 13.04. So my thinking is that 13.04 has some sort of security installed which is not on 12.04. The security prevents accessing ports on "localhost" (127.0.0.1). Even though the scanner is connected to the usb interface "sane" accesses it though the network as 127.0.1:6566. The reason I came to this idea is because (1) tried cups on 127.0.0.1:631, and (2) my custom print driver was prevented from executing by apparmor. So I put these two things together and concluded that ubuntu (or debian) has some sort of protection scheme preventing idiots like me to mess up the system. I have been playing with linux long enough to be dangerous. Unfortunately, I'm new to ubuntu and therefore do not know the internal workings of it. CONCLUSION: Normally scanner works through "saned", and the "xinetd" settings would allow it to use port 63566 on localhost. I do not see "xinetd" in ubuntu. What replaces its functionality? Apparently, the BUG is in the implementation of the alternate method and related other security schemes (apparmor??). Thank you for your understanding and help, Janos -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1184165 Title: Scanner does not work: Simple scan gives a device busy error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1184165/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
