Description of problem: Canon CanoScan LiDE 110 scanner will respond to any scanning front end in one of 3 ways: 1. The scanner will simply not respond. Reseating the USB cable resolves this issue. 2. The scanner throws an error: Failed to start scanner: invalid argument and nothing else happens 3. The scanner initializes and runs the scanner strip to the bottom of the bed, jams against the bottom and keeps trying to move it further until I unplug the usb cable. I have noticed that 2 and 3 can occur together - scanner throws an error and the scanner strip proceeds to pin itself against the end of the bed and grind away. Version-Release number of selected component (if applicable): xsane 0.999 lib64sane1-1.0.24-10.mga5 sane-backends-1.0.24-10.mga5 sane-frontends-1.0.14-19.mga5 sane-backends-iscan-1.0.24-10.mga5 saned-1.0.24-10.mga5 xsane-gimp-0.999-5.mga5 ksaneplugin-4.14.3-1.mga5 lib64sane-hpaio1-3.15.11-1.mga5 lib64ksane0-4.14.3-1.mga5 libksane-4.14.3-1.mga5 xsane-0.999-5.mga5 How reproducible: Happens every time. Steps to Reproduce: 1. Install task-scanning and possibly other components 2. Open Xsane and attempt to scan or acquire preview 3. Listen as scanner either fails to respond, throws an error, pins the scanner bar against the bottom of the chassis or some combination of those things. This is happening on a new mga5 installation. Scanner has worked without trouble on previous mga5 installation. I've swapped out scanner and cables with known, working hardware. Did not resolve.
Can you try whether updating your sane packages to the following version lib64sane1-1.0.24-10.2.mga5 sane-backends-1.0.24-10.2.mga5 sane-backends-iscan-1.0.24-10.2.mga5 saned-1.0.24-10.2.mga5 (currently available in 5/core/updates_testing, soon available as regular updates) fixes the problem?
Keywords: (none) => NEEDINFOAssignee: bugsquad => lists.jjorgeCC: (none) => marja11
I configured my media sources for updates_testing and tried to install lib64san1. I got an error that aria2 failed to install and now I can't get drakrpm to open, mcc is missing and I can no longer configure my system. Advice?
I managed to get enough of my system back together that I can open drakrpm and download stuff, but there are big holes showing up in this system. Also notable, I can't get any version of sane-backends-iscan to download. Aria2 exits with 3 or wget exits with 8, curl exits with (I think) 22. I'm seeing all kinds of weird here. When I tried to install lib64sane it uninstalled a bunch of software - drakconf Firefox, Thunderbird and who knows what else. I'm going to give this about 30 more minutes, but it's looking like I'm going to have to reinstall this desktop.
Okay, it's almost 6:30 here and my system is well and truly broken. I'm reinstalling. I don't expect that to fix the scanner issue, so I'll be watching for this bug.
It is 8:30 local time and my desktop is back together. The new installation did not resolve the issue; behavior is exactly as before. Any idea when a working update will hit the repos? Thanks.
>Scanner has worked without trouble on previous mga5 installation. Was the previous installation on the same physical machine ? Do you have an alternate USB port on this machine you can try ? If not, do you have another USB device of any kind you can try with this port ? >I've swapped out scanner and cables with known, working hardware. Did not resolve. Do you mean you actually have two identical scanners and both show the error ? Or was it a different model scanner that also showed the error ?
CC: (none) => ftg
Yes, previous installation was on the same physical machine. Tried an alternate usb port when I swapped out the scanner and cable. And yes, identical Canoscan LiDE 110 scanner. I really don't have anything on a par with the scanner that I can test that usb port with. I did, however, just plug a thumb drive into it and that drive was detected and read as expected.
Is what you're installing vanilla MGA5 as released or MGA5 with all of the released updates ? If the latter, can you try installing the former (like from a classical iso) and see if it reproduces ? If it works on original MGA5, then the problem is a subsequent update. If it originally worked on original MGA5 on this machine and doesn't now, then it's a hardware problem of some kind.
I'm installing from the downloaded DVD image on a thumb drive. I installed and immediately configured the scanner with the applet in the Control center. Scanner did not work - same trouble described above. I then updated the system and tried to scan - failed again, same trouble. So, it isn't working on a virgin install or an updated system. I just don't know. I don't see how it can be hardware as it behaves the same way with brand new hardware. And it worked fine under this same OS since it was installed. I see the logic in faulting hardware, but the other scanner is brand new. Stymied.
(In reply to Mark Adams from comment #9) > ...And it worked fine under this same OS since it was installed. I think in a USB speed problem, can you attach the dmesg when the scanner fails? And maybe a USB hub could prevent this bug to trigger?
CC: (none) => lists.jjorge
(In reply to Mark Adams from comment #9) I see the logic in faulting hardware, but the other scanner is brand new. > > Stymied. No, my hardware comment pertained not to the scanner (which you swapped out) but the system machine itself, which has been the single constant point in the testing. Do you have another system where you can install MGA5 and attach the scanner and test ? Because right not, the finger points to something on the system you're using right now.
Ah, so yes I do have such a system. My file server is sitting directly under the scanner. I plugged the scanner in, configured the printer via the applet in the Hardware section of the Control Center and performed a scan with no trouble. It worked like a charm in the the file server. Still not working in my desktop.
Jose Jorge First entry is me reseating the usb cable to get the desktop to recognize the scanner. The second entry is attempting to scan a preview image in Xsane. [155289.670231] usb 3-1: new high-speed USB device number 69 using xhci_hcd [155289.835557] usb 3-1: New USB device found, idVendor=04a9, idProduct=1909 [155289.835560] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [155289.835562] usb 3-1: Product: CanoScan [155289.835563] usb 3-1: Manufacturer: Canon [root@spike mnt]# dmesg [155289.670231] usb 3-1: new high-speed USB device number 69 using xhci_hcd [155289.835557] usb 3-1: New USB device found, idVendor=04a9, idProduct=1909 [155289.835560] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [155289.835562] usb 3-1: Product: CanoScan [155289.835563] usb 3-1: Manufacturer: Canon [155433.054966] usb 3-1: USB disconnect, device number 69 [155435.708092] usb 3-1: new high-speed USB device number 70 using xhci_hcd [155435.874347] usb 3-1: New USB device found, idVendor=04a9, idProduct=1909 [155435.874350] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [155435.874351] usb 3-1: Product: CanoScan [155435.874352] usb 3-1: Manufacturer: Canon I'm staring at that and trying to figure out what to search Google for. I appreciate the attention Jose.
Let me post that info again with time stamps. Sorry for the oversight. At 14:55 I reseated the cable. At 14:58 I opened Xsane and attempted to scan a preview: # dmesg -dT [Sun Jul 16 14:55:51 2017 < 0.000000>] usb 3-1: new high-speed USB device number 69 using xhci_hcd [Sun Jul 16 14:55:51 2017 < 0.165326>] usb 3-1: New USB device found, idVendor=04a9, idProduct=1909 [Sun Jul 16 14:55:51 2017 < 0.000003>] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [Sun Jul 16 14:55:51 2017 < 0.000002>] usb 3-1: Product: CanoScan [Sun Jul 16 14:55:51 2017 < 0.000001>] usb 3-1: Manufacturer: Canon [Sun Jul 16 14:58:15 2017 < 143.219403>] usb 3-1: USB disconnect, device number 69 [Sun Jul 16 14:58:17 2017 < 2.653126>] usb 3-1: new high-speed USB device number 70 using xhci_hcd [Sun Jul 16 14:58:17 2017 < 0.166255>] usb 3-1: New USB device found, idVendor=04a9, idProduct=1909 [Sun Jul 16 14:58:17 2017 < 0.000003>] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [Sun Jul 16 14:58:17 2017 < 0.000001>] usb 3-1: Product: CanoScan [Sun Jul 16 14:58:17 2017 < 0.000001>] usb 3-1: Manufacturer: Canon Again, I appreciate the attention.
I plugged the usb cable from the scanner into a usb hub. The hub works with other devices. I then tried to scan a preview. It immediately threw an error: Failed to open device `genesys:libusb:003036: invalid argument. The dmesg output produced this: # dmesg -dT [Sun Jul 16 15:11:17 2017 < 0.000000>] usb 3-2.2: USB disconnect, device number 35 [Sun Jul 16 15:11:17 2017 < 0.000004>] usb 3-2.2.2: USB disconnect, device number 36 [Sun Jul 16 15:11:17 2017 < 0.000967>] usb 3-2.2.3: USB disconnect, device number 37 [Sun Jul 16 15:11:17 2017 < 0.000019>] usb 3-2.2.3.1: USB disconnect, device number 38 [Sun Jul 16 15:11:17 2017 < 0.172567>] usb 3-2.2: new high-speed USB device number 39 using xhci_hcd [Sun Jul 16 15:11:17 2017 < 0.073165>] usb 3-2.2: New USB device found, idVendor=1a40, idProduct=0101 [Sun Jul 16 15:11:17 2017 < 0.000003>] usb 3-2.2: New USB device strings: Mfr=0, Product=1, SerialNumber=0 [Sun Jul 16 15:11:17 2017 < 0.000001>] usb 3-2.2: Product: USB 2.0 Hub [Sun Jul 16 15:11:17 2017 < 0.000512>] hub 3-2.2:1.0: USB hub found [Sun Jul 16 15:11:17 2017 < 0.000054>] hub 3-2.2:1.0: 4 ports detected [Sun Jul 16 15:11:18 2017 < 0.273231>] usb 3-2.2.2: new high-speed USB device number 40 using xhci_hcd [Sun Jul 16 15:11:18 2017 < 0.085300>] usb 3-2.2.2: New USB device found, idVendor=04a9, idProduct=1909 [Sun Jul 16 15:11:18 2017 < 0.000004>] usb 3-2.2.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [Sun Jul 16 15:11:18 2017 < 0.000001>] usb 3-2.2.2: Product: CanoScan [Sun Jul 16 15:11:18 2017 < 0.000001>] usb 3-2.2.2: Manufacturer: Canon [Sun Jul 16 15:11:18 2017 < 0.073687>] usb 3-2.2.3: new full-speed USB device number 41 using xhci_hcd [Sun Jul 16 15:11:18 2017 < 0.085275>] usb 3-2.2.3: New USB device found, idVendor=0a5c, idProduct=4500 [Sun Jul 16 15:11:18 2017 < 0.000004>] usb 3-2.2.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [Sun Jul 16 15:11:18 2017 < 0.000001>] usb 3-2.2.3: Product: BCM2045B2 [Sun Jul 16 15:11:18 2017 < 0.000001>] usb 3-2.2.3: Manufacturer: Broadcom [Sun Jul 16 15:11:18 2017 < 0.000095>] usb 3-2.2.3: ep 0x81 - rounding interval to 1024 microframes, ep desc says 2040 microframes [Sun Jul 16 15:11:18 2017 < 0.000468>] hub 3-2.2.3:1.0: USB hub found [Sun Jul 16 15:11:18 2017 < 0.000130>] hub 3-2.2.3:1.0: 3 ports detected [Sun Jul 16 15:11:18 2017 < 0.262047>] usb 3-2.2.3.1: new full-speed USB device number 42 using xhci_hcd [Sun Jul 16 15:11:18 2017 < 0.077102>] usb 3-2.2.3.1: New USB device found, idVendor=0a5c, idProduct=2100 [Sun Jul 16 15:11:18 2017 < 0.000003>] usb 3-2.2.3.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [Sun Jul 16 15:11:18 2017 < 0.000001>] usb 3-2.2.3.1: Product: BCM92045B3 ROM [Sun Jul 16 15:11:18 2017 < 0.000001>] usb 3-2.2.3.1: Manufacturer: Broadcom Corp
When I plugged the scanner into the hub, dmesg spit out a long string of information. I captured it and mounted it in pastebin. It may be nothing, but here is the link if you want to look at it. https://pastebin.com/QkFvH9ZN
I think your USB controller on the mainboard is damaged. You shouldn't be seeing all of this disconnecting and reconnecting of USB devices. You should also not have to reseat the cable and have it make a difference.
I'd like to disagree with you Frank Griffin, but I can't. USB is working just fine with everything else, but the scanner doesn't. The scanner works just fine with my file server, so it has to be my desktop. I'm still not able to completely let go of the idea that it's software, but that's is in part because replacing this motherboard is pretty much out of the question at this time. That's a sad statement since the Asus H81M-A is only about $52 at Pricewatch. Being broke sucks. :) At any rate, I'm trying to find a way to make the scanner available as a network device, but I'm coming up with no scanner on my lan despite the several hours invested in it. At any rate, thanks all and I suppose we can close this one as hardware.
(In reply to Mark Adams from comment #13) > I appreciate the attention Jose. I think your file server only has USB2 ports, while desktop has USB3. And I have had problems with old USB2 hardware plugged in USB3 ports. So I think here it is the same problem. Still, I have no clue on how to force USB2 mode in USB3 ports... but I think it is the way to go!
xsane supposedly supports accessing the scanner through the network, tough I've never done it.
So, I got an update this evening: lib64tiff5 sane-backends-iscan sane-backends useradd: user 'saned' already exists saned lib64sane1 microcode lib64gcrypt11 ib64gnutls28 And guess what? My scanner is scanning just fine from my desktop. Just wanted to get that on the record.
Yeah, spoke too soon. It's scanning, but the result is a solid black page. Hmm.
CC: (none) => doktor5000
See also bug 15413 where some patches for USB3 seem to be missing ...
Depends on: (none) => 15413
Hi Mark, Thank you for having taken the needed time to report this issue! This bug was filed against Mageia 5. Did it get fixed? If so, please change its status to RESOLVED - FIXED. If it didn't, then we regret that we weren't able to fix it in Mageia 5. Mageia 5 has officially reached its End of Life on December 31st, 2017 https://blog.mageia.org/en/2017/11/07/mageia-5-eol-postponed/ It continued to get limited extended support since then, but that support has now ended, too. As a result we are closing this bug report as OLD. If you still see this issue in a newer Mageia version, then please reopen this report and say so. Note that we are a community distribution, which means that we, the Mageia users, make Mageia together in our free time. If you'd like to help maintain our packages, then please consider becoming a Mageia packager https://wiki.mageia.org/en/Becoming_a_Mageia_Packager
Resolution: (none) => OLDStatus: NEW => RESOLVED