Description of problem: Simple Scan ignores attached Canon LiDE 210 scanner although lsusb recognizes this device. Error message is "No scanners detected" lsusb .. Bus 001 Device 006: ID 04a9:190a Canon, Inc. CanoScan LiDE 210 .. The scanner is fully supported on Linux - http://scannerlinux.blogspot.cz/2012/09/canon-scanner-canoscan-lide-210-full.html Version-Release number of selected component (if applicable): simple-scan 3.10.3 Linux 3.14.4-200.fc20.x86_64 How reproducible: Steps to Reproduce: 1. Connect scanner and run Simple scan 2. 3. Actual results: Error message is "No scanners detected" Expected results: working scanner Additional info: Xsane has the same problem.
I use a Canon LiDe 210 with Simple Scan and it is detected successfully. If XSane has the same problem, this is very likely not a problem with Simple Scan, but with your SANE configuration. You can try running "sane-find-scanner" at a terminal to see which scanners SANE can detect on your system. Is the scanner found by sane-find-scanner?
There was not program sane-find-scanner (missing dependencies?). I've installed it by # dnf install sane-backends* Common user has not appropriate rights: $ sane-find-scanner # sane-find-scanner will now attempt to detect your scanner. If the # result is different from what you expected, first make sure your # scanner is powered up and properly connected to your computer. # No SCSI scanners found. If you expected something different, make sure that # you have loaded a kernel SCSI driver for your SCSI adapter. could not open USB device 0x0bda/0x0158 at 001:003: Access denied (insufficient permissions) could not open USB device 0x04a9/0x190a at 001:006: Access denied (insufficient permissions) could not open USB device 0x12d1/0x1001 at 001:005: Access denied (insufficient permissions) could not open USB device 0x04f2/0xb027 at 001:002: Access denied (insufficient permissions) could not open USB device 0x1d6b/0x0002 at 001:001: Access denied (insufficient permissions) could not open USB device 0x1d6b/0x0001 at 006:001: Access denied (insufficient permissions) could not open USB device 0x1d6b/0x0001 at 005:001: Access denied (insufficient permissions) could not open USB device 0x1d6b/0x0001 at 004:001: Access denied (insufficient permissions) could not open USB device 0x1d6b/0x0001 at 003:001: Access denied (insufficient permissions) could not open USB device 0x1d6b/0x0001 at 002:001: Access denied (insufficient permissions) # No USB scanners found. If you expected something different, make sure that # you have loaded a kernel driver for your USB host controller and have setup # the USB system correctly. See man sane-usb for details. # Not checking for parallel port scanners. # Most Scanners connected to the parallel port or other proprietary ports # can't be detected by this program. # You may want to run this program as root to find all devices. Once you # found the scanner devices, be sure to adjust access permissions as # necessary. contrary root: # sane-find-scanner # sane-find-scanner will now attempt to detect your scanner. If the # result is different from what you expected, first make sure your # scanner is powered up and properly connected to your computer. # No SCSI scanners found. If you expected something different, make sure that # you have loaded a kernel SCSI driver for your SCSI adapter. found USB scanner (vendor=0x04a9 [Canon], product=0x190a [CanoScan], chip=GL124) at libusb:001:006 found USB scanner (vendor=0x12d1 [HUAWEI Technology], product=0x1001 [HUAWEI Mobile]) at libusb:001:005 # Your USB scanner was (probably) detected. It may or may not be supported by # SANE. Try scanimage -L and read the backend's manpage. # Not checking for parallel port scanners. # Most Scanners connected to the parallel port or other proprietary ports # can't be detected by this program. I can use Simple Scan as the root but as common user cannot (my webcam is offered as only one device). That's progress, of course :)
Thanks for the information, it seems that there is something wrong with your SANE configuration. I can access the device fine as a normal user here, so maybe the sane-backends packer will know what the problem is. Reassigning to sane-backends.
I have the same problem with Lide 210. My suspect is that it is a kernel-dependent problem. I had the problem with 3.13.10-200 kernel; the problem has disappeared under the kernels 3.14.x-200 (x=2,3,4,5,6). Again, the 3.14.7, 3.14.8, 3.14.9, 3.15.3, 3.15.4 (testing release) kernels are "bad" for the Lide 210 scanner.
To complete the information, the scanner works perfectly under every kernel if you disable the USB3 (xHCI) functionality in BIOS.
Bruno, thanks for the info. Changing component to kernel accordingly.
At first sight, the kernel 3.15.6-200 solves the problem
More systematic tests show that neither kernel 3.15.6-200, nor 3.15.7-200, nor 3.15.8-200 fix the bug
My current 3.15.7-200.fc20.x86_64 has no detection problem with simple-scan 3.10.3. But as I wrote previously there are strange package dependencies. I can install simple-scan without sane-backends-drivers-scanners and these drivers required several development packages.
A little off-topic, but anyway: (In reply to Ladislav Nesnera from comment #9) > My current 3.15.7-200.fc20.x86_64 has no detection problem with simple-scan > 3.10.3. But as I wrote previously there are strange package dependencies. I > can install simple-scan without sane-backends-drivers-scanners and these This is intentional as there are other packages besides sane-backends-drivers-* that provide backend drivers for software using the SANE library. We don't want the scanner libraries that contain the basic functionality to depend on any driver packages (inside sane-backends or external) for these reasons: - It would explode space requirements on e.g. live media. Even without scanning frontend programs like simple-scan, or xsane, there is basic system software like colord (a daemon mapping color devices to color profiles) that needs to be able to access connected scanner hardware. Pulling in the SANE library is necessary for colord to work, pulling in the drivers isn't. - It wouldn't help with 3rd party drivers we don't have control over anyway. I know it's not ideal, and I plan to do something about it (using PK to install drivers for hardware that is detected on the system, or weak RPM dependencies, or a combination). > drivers required several development packages. No it doesn't, I just made a test install of just sane-backends-drivers-scanners and it doesn't pull in a single -devel package.
(In reply to Nils Philippsen from comment #10) Packages structure: I see and It's good idea. Devel dependencies: Interesting. You are right although I'm sure my previous attempt required libraries like sane-backends-devel or libusbx-devel Thank a lot
This is the update of my situation concerning the Canon LiDe 210 scanner My hardware: Notherboard: Asus Z87M-Plus CPU Intel(R) Core(TM) i7-4770S CPU @ 3.10GHz quadcore - Disable USB3 from BIOS: simple-scan works with any kernel (from 3.14.4-200.fc20.x86_64 to 3.16.2-201.fc20.x86_64) - Enable USB3 from BIOS: simple-scan works only with 3.14.4-200.fc20.x86_64 kernel Under the following virtual OS under VirtualBox simple-scan always works: Debian 7.5 Ubuntu 14.4 OpenSuse 13.3 CentOS 6.5 Centos 7.0-1406 Slackware 14.1 Linux mint 17 PCLinuxOS 2014-05 PCLinuxOS 2014-08 Note that VirtualBox does not provide USB3 for guest OS. I hope this can help
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 20 kernel bugs. Fedora 20 has now been rebased to 3.17.2-200.fc20. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 21, and are still experiencing this issue, please change the version to Fedora 21. If you experience different issues, please open a new bug report for those.
I am very sorry to confirm all what I said in my post of 2014-09-22, up to the 3.17.2-200.fc20 kernel. I tried Fedora 21 beta in VirtualBox and I got a working simple-scan, but this does not solve the problem (all OS I tried under VirtualBox give a working simple-scan) For this reason I cannot transfer the bug to Fedora 21 beta.
Hello, Similar problem with CanonScan N1240U. It is fully supported by SANE via the plustek backend: http://www.sane-project.org/sane-mfgs.html#Z-CANON but I'm unable to scan. - sudo sane-find-scanner (complete output as attachment) found USB scanner (vendor=0x04a9 [Canon], product=0x220e [CanoScan]) at libusb:003:004 - Simple Scan: Failed to scane: unable to star scan - scanimage $ scanimage -d plustek --mode Gray --resolution 75 >test.pnm scanimage: open of device plustek failed: Invalid argument
Created attachment 970007 [details] Output of "sudo sane-find-scanner -v -v"
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 20 kernel bugs. Fedora 20 has now been rebased to 3.18.7-100.fc20. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 21, and are still experiencing this issue, please change the version to Fedora 21. If you experience different issues, please open a new bug report for those.
I tried 3.18.7-100.fc20. No success. simple-scan outputs the message: Unable to start scan. xsane freezes
Same problem with Canon LiDE 50. Scanner gets detected with sane-find-scanner but not by a scanner frontend. $ uname -a Linux siegfried.localdomain 3.18.7-100.fc20.x86_64 #1 SMP Wed Feb 11 19:01:50 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux $ sudo sane-find-scanner # sane-find-scanner will now attempt to detect your scanner. If the # result is different from what you expected, first make sure your # scanner is powered up and properly connected to your computer. # No SCSI scanners found. If you expected something different, make sure that # you have loaded a kernel SCSI driver for your SCSI adapter. found USB scanner (vendor=0x04a9 [Canon], product=0x2213 [CanoScan], chip=GL842) at libusb:001:011 # Your USB scanner was (probably) detected. It may or may not be supported by # SANE. Try scanimage -L and read the backend's manpage. # Not checking for parallel port scanners. # Most Scanners connected to the parallel port or other proprietary ports # can't be detected by this program. $ sudo scanimage -L No scanners were identified. If you were expecting something different, check that the scanner is plugged in, turned on and detected by the sane-find-scanner tool (if appropriate). Please read the documentation which came with this software (README, FAQ, manpages).
In my case Lide210 is detected by sane-find-scanner AND scanimage. But Simple Scan outputs: Failed to scan: unable to start scan xsane freezes uname -a Linux mario.lan 3.18.7-100.fc20.x86_64 #1 SMP Wed Feb 11 19:01:50 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux sane-find-scanner # sane-find-scanner will now attempt to detect your scanner. If the # result is different from what you expected, first make sure your # scanner is powered up and properly connected to your computer. # No SCSI scanners found. If you expected something different, make sure that # you have loaded a kernel SCSI driver for your SCSI adapter. could not fetch string descriptor: Pipe error found USB scanner (vendor=0x04a9 [Canon], product=0x190a [CanoScan], chip=GL124) at libusb:001:005 # Your USB scanner was (probably) detected. It may or may not be supported by # SANE. Try scanimage -L and read the backend's manpage. # Not checking for parallel port scanners. # Most Scanners connected to the parallel port or other proprietary ports # can't be detected by this program. scanimage -L device `genesys:libusb:001:005' is a Canon LiDE 210 flatbed scanner
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 20 kernel bugs. Fedora 20 has now been rebased to 3.19.5-100.fc20. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 21, and are still experiencing this issue, please change the version to Fedora 21. If you experience different issues, please open a new bug report for those.
I updated to 3.19.5-100.fc20, but always get the same error message: Failed to scan Unable to connect to scanner lsusb, sane-find-scanner and scanimage -L all detect my CanoScan LiDE 210
Same problem here with Fedora 21 and kernel 3.19.5-200.fc21.x86_64 CanonScan N1240U recognized: [18939.914618] usb 1-3: new full-speed USB device number 3 using xhci_hcd [18940.092317] usb 1-3: New USB device found, idVendor=04a9, idProduct=220e [18940.092320] usb 1-3: New USB device strings: Mfr=64, Product=77, SerialNumber=0 [18940.092322] usb 1-3: Product: CanoScan [18940.092324] usb 1-3: Manufacturer: Canon [18940.120764] WARNING! power/level is deprecated; use power/control instead But unable to scan.
I can confirm this is still an issue in fedora 21. Lenovo carbon x1 gen3. Had to disable USB3 and it worked fine.
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.