canoscan lide 50 worked under jaunty but not under karmic

[elekis]

hi,

canoscan lide 50 witch is worked properly under jaunty but since I upgraded my system, the scanner is not recognized by xsane.

lsusb say
         Bus 001 Device 006: ID 04a9:2213 Canon, Inc. CanoScan LiDE 50/LiDE 35/LiDE 40

and genesys.conf has
         # Canon LiDE 35/40/50
         usb 0x04a9 0x2213

xane-find-scanner
         found USB scanner (vendor=0x04a9, product=0x2213, chip=GL841?) at libusb:001:006

this is the problem, there is a ? after a chip and there is no name in the vendor attribute (technicly, vendor must be 0X04a9[canon]

imagescan -L doesn't found anything, xsane has a beautiful "no device found".

[jhoyne (john-hoyne)]

Canonscan LIDE 50 worked under Jaunty but will not work in Karmic.

lsusb output
Bus 001 Device 006: ID 04a9:2213 Canon, Inc. CanoScan LiDE 50/LiDE 35/LiDE 40

sane-find-scanner output
found USB scanner (vendor=0x04a9 [Canon], product=0x2213 [CanoScan], chip=GL841) at libusb:001:006

scanimage -L output
device `genesys:libusb:001:006' is a Canon LiDE 35/40/50 flatbed scanner

Scanner works okay in MS Windows -so the hardware is okay.
Xsane finds the scanner but freezes when scan button is pressed - eventually it sometimes comes up with
"Failed to start scanner: Error during device I/O"

[Mike Keal (mike-thekeals)]

I'm new to Ubuntu, so haven't tried using my LIDE50 with any release prior to Karmic. I have similar results to jhoyne, with additional error text:

sane-find-scanner output:
found USB scanner (vendor=0x04a9 [Canon], product=0x2213 [CanoScan], chip=GL841) at libusb:001:007

scanimage -L output:
WARNING: Unhandled message: interface=org.freedesktop.DBus.Introspectable, path=/, member=Introspect
device `genesys:libusb:001:007' is a Canon LiDE 35/40/50 flatbed scanner

A couple of things I've tried without success:

1) I read that there may be a problem with Karmic suspending USB to save power; the suggested fix was to install scanbuttond to provide regular 'keep alive' activity and prevent the USB from being suspended. Installed and run, no difference.

2) I've seen several suggestions relating to the mode assigned to the device in config files; the common theme seems to be to replace mode=664 with mode=0666 to allow the device to be run by non-root users. The file most often suggested is
/etc/udev/rules.d/45-libsane.rules
which doesn't (or didn't) exist. I found a link to a copy of this file at
http://forums.linuxmint.com/viewtopic.php?f=49&t=5945
Installed it, edited the entry for the LIDE 50 to show mode=0666, and rebooted. No change.
I also found a similar reference to another config file
/lib/udev/rules.d/50-udev-default.rules
where I changed the mode of the USB subsystem to '0666' at point # libusb device nodes. No change.
I also tried running xsane as root just to rule out any permissions problems. Failed with the same error.

Finally, I found a hint at how to get a debug file from Xsane and ran the following:

SANE_DEBUG_GENESYS=255 xsane 2>lide50.log

which generated the following error info at a point within the log file:

[genesys] sanei_genesys_read_data_from_scanner: timeout, buffer does not get filled
[genesys] genesys_flatbed_calibration: offset calibration failed: Error during device I/O
[genesys] genesys_start_scan: failed to do flatbed calibration: Error during device I/O

I guess that it just doesn't want to work! Any ideas?

Mike

[Droop7 (droop7)]

I have the same problem.

I tried to use Sane, gnomescan and gscan2pdf.

The scanner don't start scanning.

X-sane open properly, find my webcam and my scanner.

I select the scanner and try to scan a document. Nothing appens. The screen change to grey.

Every time, i force the closing of X-sane.

Thats's big problem for me to. I use my scanner every day for my work.

lsusb gives:
Bus 002 Device 004: ID 04a9:2213 Canon, Inc. CanoScan LiDE 50/LiDE 35/LiDE 40

sane-find-scanner:
found USB scanner (vendor=0x04a9 [Canon], product=0x2213 [CanoScan], chip=GL841) at libusb:002:004

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.