I've been using scanimage with my Fujitsu ScanSnap ix500 for a month or so. This has worked fine until today, when I get the following output:
[dfriberg at localhost test]$ scanimage -b -d fujitsu --format=tiff --resolution=300 Scanning -1 pages, incrementing by 1, numbering from 1 Scanning page 1 Scanned page 1. (scanner status = 5) Scanning page 2 scanimage: sane_start: Document feeder out of documents libusbx: warning [add_to_flying_list] failed to arm first timerfd (errno 9) libusbx: warning [libusb_close] internal signalling read failed, closing anyway libusbx: error [do_close] Device handle closed while transfer was still being processed, but the device is still connected as far as we know libusbx: error [do_close] A cancellation hasn't even been scheduled on the transfer for which the device is closing ^Cscanimage: received signal 2 scanimage: trying to stop scanner ^Cscanimage: received signal 2 scanimage: aborting [dfriberg at localhost test]$ scanimage --version scanimage (sane-backends) 1.0.24git; backend version 1.0.24 As you can see it hangs after the libusbx errors. However, it is producing output images. Dave Friberg phone: (402) 957-2480 On Tue, Jun 11, 2013 at 9:06 PM, Dale Amon <amon at vnl.com> wrote: > On Tue, Jun 11, 2013 at 09:55:15PM -0400, m. allan noah wrote: >> I just committed backend version 117 to our development tree. This >> includes a minor fix for a continuous feed problem with the iX500. All >> other 'normal' scanning features are supported. WiFi however, is not. >> Also, one user has reported some odd behavior related to higher >> resolution color scans. I have not been able to reproduce, but wonder >> if it might be related to USB 3 ports. >> >> This should be available from our git snapshots tomorrow night. I >> could walk you thru compiling it, or maybe someone builds a package >> for Ubuntu. I don't use Ubuntu, so I don't know. > > Thanks. If it means getting access to the new scanner, I will look > at doing the compile. If the diffs are not too large from the current > Ubuntu package, I might be able to unpack it, get a diff patch set, > run them against the old files to update them, and then generate > a new package with a name that will not get updated the next time > they do a bug fix... something which is absolutely certain to happen > at a worst case time. > > Lets chat about this a bit. It will be the weekend before I can put > in substantial time, but I can get prepped ahead of time. > > > > -- > sane-devel mailing list: sane-devel at lists.alioth.debian.org > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel > Unsubscribe: Send mail with subject "unsubscribe your_password" > to sane-devel-request at lists.alioth.debian.org
