Hopefully this will be of assistance, in case anyone looks at this bug.
I've run the following commands under the current kernel
(4.4.0-34-generic) and also a previous kernel (4.2.0-41-generic)

strace scanimage -L log_curr_kernel_not_work 2>&1   Scanner not detected
strace scanimage -L log2_prev_kernel_works 2>&1     Scanner works fine

Files attached.

Diffing the logs shows the interesting stuff at line 3072 
(log_curr_kernel_not_work) and line 3232 (log2_prev_kernel_works). It appears 
that there is an issue connecting under the current kernel that doesn't happen 
in previous kernels. Why? Beyond me I'm afraid, but its disappointing not to 
have scanning available now.
Any help appreciated. Thanks.

** Attachment added: "log2_prev_kernel_works"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1613027/+attachment/4729877/+files/log2_prev_kernel_works

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1613027

Title:
  Network scanner not detected by xsane after upgrade to 16.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1613027/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to