This makes grinding noises while stationary on the 2nd or 3rd scan in Dapper, not in Breezy, relieved by unplugging USB cable. I confirmed this by using a chroot Breezy to running xsane in the same box.
Dapper config:
$ uname -a
Linux beanz 2.6.15-28-386 #1 PREEMPT Thu Feb 1 15:51:56 UTC 2007 i686 GNU/Linux
$ apt-show-versions | grep sane
xsane-common/dapper uptodate 0.97-4ubuntu6
libsane/dapper uptodate 1.0.17-1ubuntu4
python2.4-imaging-sane/dapper uptodate 1.1.5-4ubuntu1
sane-utils/dapper uptodate 1.0.17-1ubuntu4
xsane/dapper uptodate 0.97-4ubuntu6
python-imaging-sane/dapper uptodate 1.1.5-4ubuntu1
$ scanimage -L
device `plustek:libusb:003:007' is a Canon N650U/N656U USB flatbed scanner
$ sane-find-scanner
found USB scanner (vendor=0x04a9 [Canon], product=0x2206 [CanoScan], chip=LM9832/3) at libusb:003:007
and output caught before scanner grinds while stationary. Full transcript is attached at the end of this report.
$ export SANE_DEBUG_PLUSTEK=20 ; xsane $2 >> /tmp/xsane-error.txt 2>&1
Scanner stalls on line 1064:
[plustek] MCLK_FFW = 6 --> 0x0a
Breezy config:
$ uname -a
Linux beanz 2.6.15-28-386 #1 PREEMPT Thu Feb 1 15:51:56 UTC 2007 i686 GNU/Linux
$ apt-show-versions | grep sane
python-imaging-sane/unknown uptodate 1.1.5-4
xsane-common/unknown uptodate 0.97-3ubuntu2
libsane/unknown uptodate 1.0.15-9ubuntu6
python2.4-imaging-sane/unknown uptodate 1.1.5-4
sane-utils/unknown uptodate 1.0.15-9ubuntu6
xsane/unknown uptodate 0.97-3ubuntu2
sane/unknown uptodate 1.0.13-2
$ sane-find-scanner
found USB scanner (vendor=0x04a9, product=0x2206, chip=LM983x?) at libusb:003:012
$ sudo scanimage -L
(snip)
[plustek] Scanner information:
[plustek] Vendor : Canon
[plustek] Model : N650U/N656U
the result of the catching output from xsane in Dapper is attached.
Dapper: xsane-dapper-