Janos G. Komaromi, regarding your comments https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1184165/comments/62 : >"1) If the kernel configuration is the same for a kernel that scanner works >and for another kernel that the scanner does not work what is the point of >bisecting kernels? Please, explain."
This question doesn't make any sense. At this time, this report is focused on the kernel version you are testing when it does and doesn't work, only for the hardware you originally reported against, not anything else. Bisection will allow a developer to know precisely what commit caused the problem. Then it can be best judged if reverting the commit, or improving upon it is the best way to go. Unless this is done, at best, it is onerous to address this issue. >"(2) Apparently the kernel recognizes the scanner devices, but something takes it over and causes it to report as being busy. Shouldn't we direct our investigation towards that?" That's what a bisection is, an investigation directed at exactly that. >"Also, I installed 12.04 on my Acer laptop, abandoned my W7 boot and use only my Xubuntu on it, completely happy." If you are happy to use Precise, as it's EOL date is after Raring and Saucy, you are welcome to mark the Status Invalid. -- 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: 03f0:1205 [Asus A7N266VM] 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
