Created attachment 903235 [details] Output from strace. Description of problem: Plugged in this scanner as identified by lsusb Bus 003 Device 063: ID 04a9:220e Canon, Inc. CanoScan N1240U/LiDE 30 Attempted to identify it with sane-find-scanner, got this error found USB scanner (vendor=0x04a9 [Canon], product=0x220e [CanoScan]) at libusb:003:015 could not fetch string descriptor: Pipe error could not fetch string descriptor: Pipe error could not fetch string descriptor: Pipe error # Your USB scanner was (probably) detected. It may or may not be supported by # SANE. Try scanimage -L and read the backend's manpage. Attempting to scan with either simple scan or xsane produces a "no scanners found" result. Scanner works OK on a 32 bit machine running an earlier version of Fedora. Version-Release number of selected component (if applicable): Current Fedora 20 all updates installed. How reproducible: Every time. Steps to Reproduce: 1. Plug in scanner 2. sane-find-scanner 3. Actual results: Error as above Expected results: Fails to find scanner Additional info: Running sane-find-scanner under strace shows that the error is: ioctl(16, USBDEVFS_REAPURBNDELAY, 0x7fffe87b7330) = -1 EAGAIN (Resource temporarily unavailable) Full trace output attached This machine is on a client's site, so getting further information may take time as it is an hour drive each way to get to the machine.
Hi, USBDEVFS_REAPURBNDELAY sometimes returning -EAGAIN is normal, and libusb already contains code to deal with this. At this point I see no reason to assume that this is a libusb bug, changing component. Regards, Hans
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.