Package: libsane
Version: 1.0.22-7.1
Severity: normal

scanimage -L
device `genesys:libusb:002:003' is a Canon LiDE 60 flatbed scanner

scanimage > /tmp/test.tiff

results in a successful scan, but the scanner (scanner unit, sledge?) stays in
the position where the scan was stopped. It does not return back to the start
position/parking position.

If a second scan is started (same command), the scanner *will* return, execute
the scan - and again refuse to return to the parking position. So in short:
once the first scan has been started, it is impossible to make it return for
all time.

Expected behaviour:

After finishing or cancelling a scan, the scanner unit should return to the
parking positon.

Note:

This is with libsane 1.0.22-7.1 which is the current version in testing as of
today.

It looks like this broke somewhere between 1.0.21-9 and 1.0.22-7.1 as
downgrading to version 1.0.21-9 from snapshots *solves the problem*.



-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 3.2.0-2-686-pae (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages libsane depends on:
ii  acl                2.2.51-7
ii  adduser            3.113+nmu2
ii  libavahi-client3   0.6.31-1
ii  libavahi-common3   0.6.31-1
ii  libc6              2.13-32
ii  libexif12          0.6.20-2
ii  libgphoto2-2       2.4.14-2
ii  libgphoto2-port0   2.4.14-2
ii  libieee1284-3      0.2.11-10
ii  libjpeg8           8d-1
ii  libsane-common     1.0.22-7.1
ii  libtiff4           3.9.6-5
ii  libusb-0.1-4       2:0.1.12-20
ii  libv4l-0           0.8.8-1
ii  multiarch-support  2.13-32
ii  udev               175-3.1

Versions of packages libsane recommends:
ii  libsane-extras  1.0.22.2
ii  sane-utils      1.0.22-7.1

Versions of packages libsane suggests:
pn  avahi-daemon  <none>
pn  hplip         3.12.2-1
pn  hpoj          <none>

-- no debconf information



-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to