<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Oct 28, 2014 at 11:28 PM, Olaf Meeuwissen <span dir="ltr"><<a href="mailto:olaf.meeuwissen@avasys.jp" target="_blank">olaf.meeuwissen@avasys.jp</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><span class=""><br>
Mike Cloaked writes:<br>
<br>
> Secondly i set up wireshark this afternoon, and got it all running to<br>
> capture usb data on the bus that the scanner is connected to. Having<br>
> completed a capture for a vuescan run scanning the same docuument as<br>
> previously. I then reset the scanner, and wireshark, and ran a scan in<br>
> xsane - but instead of hanging it worked! The only change since the<br>
> previous time I booted the same laptop is that I ran a system update - but<br>
> there was no obvious package that was updated that would have contributed<br>
> to the changed behaviour!<br>
<br>
</span>Not obvious to you perhaps but maybe someone else? Would you happen to<br>
have the full list of packages (as well as their old and new versions)?<br>
Maybe someone will spot something.<br>
<br>
BTW, did you boot with the same kernel?<br>
<span class="im"><br>
Hope this helps,<br>
--<br>
Olaf Meeuwissen, LPIC-2 FLOSS Engineer -- AVASYS CORPORATION<br>
</span><div class=""><div class="h5">FSF Associate Member #1962 Help support software freedom<br>
<a href="http://www.fsf.org/jf?referrer=1962" target="_blank">http://www.fsf.org/jf?referrer=1962</a><br>
</div></div></blockquote></div><br><div class="gmail_extra">Yes I do have the full list of packages that were updated in the pacman log - I am away from that laptop at the moment, but later today I will post the full list of updated packages from the pacman log. Yes it was booted with the same kernel though the kernel was updated from 3.16 to 3.17 only a few days ago and is now running with the new kernel.</div><div class="gmail_extra"><br></div><div class="gmail_extra">The other thing I had wondered/thought about was that it might be a partial hardware failure. However the same usb3 port on the laptop where the scanner was plugged in was used to plug in an external usb hard drive and that works without any problems. Also the scanner was plugged in to a different laptop with only usb2 ports and it was fine with xsane on that laptop. So that suggests that the hardware is not the problem either at the laptop port or for the scanner.</div><div class="gmail_extra"><br></div><div class="gmail_extra">I also separately have a multifunction printer/scanner (Samsung SCX4500W) that was working fine as both printer and scanner when connected via usb2 to a previous desktop that only had usb2 ports, but that machine is now replaced with a new desktop that only has usb3 ports - the MFP works without any error connected to a usb3 port for the printer functions but the scanner hangs xsane whilst connected to the same physical port. However the scanner when connected via its ethernet wired network connection works fine from xsane using tcp. So the scanner function seems to work provided it is not connected to a usb3 port. That desktop also runs arch linux. A few months ago I tested this MFP plugging into the laptop with usb3 ports and xsane hung when scanning was attempted on the laptop via usb3 as well.</div><div class="gmail_extra"><br></div><div class="gmail_extra">The combined set of information from these tests seems to indicate that there is an issue with usb2 printers connected to a machine via usb3 when using sane, though of course I only have archlinux so I don't know if the same scanners would work properly when connected via usb3 to a machine running a different version of linux where the package sets are versioned differently? If anyone has either of the two scanners that I have, and are running Ubuntu, Fedora,Mint or another version of linux in a machine with usb3 ports it would be a very useful comparison?</div><div class="gmail_extra"><br></div><div class="gmail_extra">This evening I should have a bit more time to try the Canon LIDE 210 again on the laptop that I have been having usb3 problems for scanning, and will try to capture usb data for a partial scan and fail situation, and I will post the package update list in the same post.</div><div><br></div>-- <br>mike c
</div></div>