Scanner 04a9:220e used works in Dapper and Edgy not Feisty

[Jonah]

first my printers wouldn't work and then i tried my scanner and that's not working either since updating to feisty on amd64, was fine on same system in edgy... seems to be some major detection problems going down. can anyone fix this please? if you need any more info let me know what i can provide...

[Jonah (jonah)]

tried scanning on my 32bit box and that won't work either. although it will give me a preview in xsane, it doesn't scan....

[Nathan Murray (yotux)]

I have attempted to recreate this problem on my system. The first time I scanned an image I used xsane version 0.991 setting of line art. The image was poor quality. The second scan I did was in color and appears to be good.

The system that I used to test against the above issue was Kubuntu 7.04 fiesty. As of Sun, 7 Jan 2007 07:56:00 -0600 I believe all updates have been applied.

I have enclosed the id of my scanner below.

Bus 003 Device 002: ID 03f0:0201 Hewlett-Packard ScanJet 6200c

Hope this helps someone.

Unable to confirm at this point in time.

Nathan Murray

[Jonah (jonah)]

my printers are now working from last gnome updates, however scanner still has the same problem...

[Brian Murray (brian-murray)]

Thanks for your bug report. Could you provide us with the output of 'lsusb' so we can better troubleshot this issue? Additionally, what happens when you run 'sane-find-scanner' in a terminal?

[Jonah (jonah)]

jonah@jonah-desktop:~$ sane-find-scanner
bash: sane-find-scanner: command not found
jonah@jonah-desktop:~$

[Jonah (jonah)]

jonah@jonah-desktop:~$ lsusb
Bus 006 Device 001: ID 0000:0000
Bus 003 Device 001: ID 0000:0000
Bus 005 Device 001: ID 0000:0000
Bus 001 Device 002: ID 046d:c512 Logitech, Inc.
Bus 001 Device 003: ID 04a9:220e Canon, Inc. CanoScan N1240U/LiDE 30
Bus 001 Device 001: ID 0000:0000
Bus 002 Device 002: ID 058f:6362 Alcor Micro Corp.
Bus 002 Device 001: ID 0000:0000
Bus 004 Device 001: ID 0000:0000
jonah@jonah-desktop:~$

[Brian Murray (brian-murray)]

The utility sane-find-scanner is part of the sane-utils package.

[Jonah (jonah)]

ok thanks.. i've installed sane-utils, ran the command and got this:

jonah@jonah-desktop:~$ 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=0x220e [CanoScan], chip=LM9832/3) at libusb:001:003
  # 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.

  # 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.
jonah@jonah-desktop:~$

[Brian Murray (brian-murray)]

It doesn't seem that there is support for your scanner in the sane backend. I looked at this url, http://www.buzzard.me.uk/jonathan/scanners-usb.html , and read:
"These are National Semiconductor LM9833 USB scanner chip based. While not currently supported, they are likely to be supported by the Plustek backend in the near future. Check the SANE Plustek backend for more upto date details."

However from your first comment I am under the impression that your scanner worked in Edgy. Is that correct?

[Jonah (jonah)]

that's correct the scanner worked fantastic in dapper and edgy... in fact i seem to remember that it was detected with some kind of plustek driver automatically...

[Clay Weber (claydoh)]

May be related, my Canon Lide25 (plustek backend) scanner which worked in Edgy, does not scan using kooka or xsane/xscanimage. It "pretends" to scan, the scanner bar does not move or light up in the preview/final scan, and it produces a black scan.

I only have found a few other very recent instances of this problem in other distros, but no useful information
https://alioth.debian.org/tracker/?group_id=30186&atid=410366&func=detail&aid=304367
http://www.nabble.com/canon-lide25---impossible-to-scan-via-a-graphical-frontend-t3129854.html

[Clay Weber (claydoh)]

Also I should note that scanning via command line does produce a normal image.

[Garbor (garbor)]

I can confirm this, i have the same scanner (N1240U/LIDE 30).
It was working fine on dapper and edgy but on feisty it will be detected but not accessed.

Bus 005 Device 005: ID 046d:08c5 Logitech, Inc.
Bus 005 Device 001: ID 0000:0000
Bus 004 Device 001: ID 0000:0000
Bus 003 Device 002: ID 04a9:220e Canon, Inc. CanoScan N1240U/LiDE 30
Bus 003 Device 001: ID 0000:0000
Bus 002 Device 003: ID 045e:0040 Microsoft Corp. Wheel Mouse Optical
Bus 002 Device 002: ID 046d:c21a Logitech, Inc.
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 001: ID 0000:0000

[Clay Weber (claydoh)]

Similar reports on Arch's bug tracker:
http://bugs.archlinux.org/task/6182

[Clay Weber (claydoh)]

marked as duplicate of bug # 85488
https://bugs.beta.launchpad.net/ubuntu/+source/sane-backends/+bug/78205