Simple Scan with Canon LIDE50 - scan results in black page
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
| sane-backends (Debian) |
Fix Released
|
Unknown
|
||
| sane-backends (Ubuntu) |
Undecided
|
Rolf Leggewie | ||
| xsane (Ubuntu) |
Undecided
|
Unassigned | ||
Bug Description
Binary package hint: simple-scan
It makes no difference whether scanning as Photo or Text or whether the scan resolution is 150 or 300 - the output is always a black page. The scanner makes the noises you'd expect of the scanner head moving along.
Version 2.32.0-0ubuntu4 (simple-scan)
Ubuntu 10.10
ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: simple-scan 2.32.0-0ubuntu4
ProcVersionSign
Uname: Linux 2.6.35-
NonfreeKernelMo
Architecture: i386
Date: Wed Nov 24 11:51:54 2010
DriverPackageVe
libsane 1.0.21-2ubuntu2
libsane-extras N/A
hplip 3.10.6-1ubuntu10.1
hpoj N/A
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release Candidate i386 (20100928)
Lsusb:
Bus 002 Device 005: ID 03f0:d404 Hewlett-Packard
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 010: ID 04a9:2213 Canon, Inc. CanoScan LiDE 50/LiDE 35/LiDE 40
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: FOXCONN M61PMV
ProcCmdLine: BOOT_IMAGE=
ProcEnviron:
LANG=en_GB.utf8
SHELL=/bin/bash
SourcePackage: simple-scan
dmi.bios.date: 07/01/2010
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: P09
dmi.board.name: M61PMV
dmi.board.vendor: FOXCONN
dmi.board.version: FAB 1.1
dmi.chassis.
dmi.chassis.type: 3
dmi.chassis.vendor: FOXCONN
dmi.modalias: dmi:bvnPhoenixT
dmi.product.name: M61PMV
dmi.product.
dmi.sys.vendor: FOXCONN
jhoyne (john-hoyne) wrote : | #1 |
Mali (mali2010) wrote : | #2 |
Mali (mali2010) wrote : | #3 |
Same on Debian Lenny, armel. Tested with scanimage (sane-backends) 1.0.21; backend version 1.0.21 ...
Mali (mali2010) wrote : | #4 |
Some more details:
The armel system mentioned above is actually a Debian Squeeze system (not Lenny!) running on a Seagate Dockstar.
The original description mentions the characteristic noise. This noise is produces while the scanner head is supposed to move, but it is not really moving but standing still with the light turned on (green or alternating color, depending on the scanning mode).
The scanner was working fine until some update some weeks ago.
Robert Ancell (robert-ancell) wrote : | #5 |
Reassigned to from simple-scan/xsane to sane-backends - as it affects all programs, it's a driver problem.
affects: | simple-scan (Ubuntu) → sane-backends (Ubuntu) |
Changed in xsane (Ubuntu): | |
status: | New → Invalid |
Mali (mali2010) wrote : | #6 |
Seems to be the same as in this Debian bug report:
Mali (mali2010) wrote : | #7 |
Yet another mentioning of the same behaviour on a Debian Sid system:
http://
Mali (mali2010) wrote : | #8 |
I just tested some older versions of libsane:
1.0.20-13ubuntu2 works fine, 1.0.21-2ubuntu2 shows the behaviour described above ...
jhoyne (john-hoyne) wrote : | #9 |
I confirm Mali's experience here also: forcing Maverick to use libsane 1.0.20-13ubuntu2 works round this bug
Chriss (neuhaus-info) wrote : | #10 |
I confirm Mali's experience here also: forcing Maverick to use libsane
1.0.20-13ubuntu2 works round this bug
Simple-Scan works without a problem
1) removed libsane via apt-get (simple-scan will be removed also)
2) downloaded deb from https:/
3) Installed deb
4) installed simple-scan via apt-get
Mali (mali2010) wrote : | #11 |
Ah, the problem seems to have gone in the most recent package from
https:/
Just installing libsane_
Alkis Georgopoulos (alkisg) wrote : | #12 |
I confirm that the problem exists in Precise and that it is solved by installing the libsane package from Lucid
(with dpkg -i and "echo hold libsane | dpkg --set-selections).
Changed in sane-backends (Debian): | |
importance: | Undecided → Unknown |
status: | New → Unknown |
Rolf Leggewie (r0lf) wrote : | #13 |
So, lucid was good, but maverick and later were not. How about Quantal and in particular raring? Are those affected? They've seen a new upstream release compared to precise and that release seems to have gotten many bug fixes.
Changed in sane-backends (Ubuntu): | |
assignee: | nobody → Rolf Leggewie (r0lf) |
status: | New → Incomplete |
Changed in sane-backends (Debian): | |
status: | Unknown → Fix Released |
Rolf Leggewie (r0lf) wrote : | #14 |
The upstream Debian ticket was marked as fixed for 1.0.22-1 and confirmed fixed for 1.0.22-2 by the reporter. Alkis, I am surprised to hear you might still be affected with version 1.0.22-7ubuntu1 in precise.
Rolf Leggewie (r0lf) wrote : | #15 |
jhoyne did not report back so I will close this ticket now. Please feel free to reopen if you are still affected.
Alkis, I suggest you open a new ticket since your problem might be a different issue after all.
Changed in sane-backends (Ubuntu): | |
status: | Incomplete → Fix Released |
Nino (nino-ketonen) wrote : | #16 |
Argh =) HP scanjet scan results are all black.
I changed resolution and it worked once, but second scan was all black again.
Ubuntu 13.10
Nino (nino-ketonen) wrote : | #17 |
And it is getting more weird.
I tried several different software's with same result and somehow when nerves was almost done, i started xsane from terminal as a root and it worked. Same thing with simple scan.
Same here: Ubuntu 10.10, x86_64, Canon LiDE 50.
Seems to affect all programs accessing the scanner: Simple Scan, xsane, scanimage ...