[sane-devel] Meldung: Operation abgebrochen

[Olaf Meeuwissen]

Please keep this on the mailing list.  That way it will get archived and
be searchable for everyone.

gilada at web.de writes:

> Am Tuesday 07 June 2011 02:19:37 schrieben Sie:
>> "Wolfram Heider" <wolframheider at web.de> writes:
>> > On Mon, 06 Jun 2011 23:20:57 +0200, Jeffrey Ratcliffe
>> > 
>> > <jeffrey.ratcliffe at gmail.com> wrote:
>> >> 2011/6/6  <gilada at web.de>:
>> >>> [snip original German, mine's to crufty by now]
>> > 
>> > Jeffrey is right, but there are pretty a lot German speakers here.
>> > Unfortunately you gave us little information. For example which
>> > SANE-version do you have in use? What does scanimage -L in debug mode
>> > say?  Did you change the USB-port?
>> > For this just as a quick shot in the dark: the packages from Debian
>> > tend to be a bit faulty from time to time. An installation of the
>> > source  packages from the SANE server might help.
>> > As a quick workaround comment out in /etc/sane.d/dll.conf 'epson2' and
>> > uncomment 'epson'. That will exchange the backend/driver.
>> > 
>> >> Gilbert is saying that he installed first sane, then xsane on Debian 6
>> >> with KDE4.x, but that his Epson Perfection 1650 doesn't scan.
>> 
>> Debian 6, that implies sane-backends-1.0.21-9 and xsane-0.997-2+b1.
>> There were a few fixes to the epson2 backend in sane-backends-1.0.22
>> that affected the Perfection 1650.  For what it's worth, the deprecated
>> epson backend ought to work fine.  You may also try the epkowa backend
>> that comes with Image Scan! for Linux available here:
>> 
>>   http://avasys.jp/eng/linux_driver/download/
>> 
>> >> It starts to position the scan head, but a short time later he gets
>> >> the warning "Operation cancelled".
>> 
>> If the problem persists, please provide a debug log with
>> 
>>   SANE_DEBUG_EPKOWA=HEX scanimage > /dev/null 2> debug.log
>> 
>> if using the epkowa backend or
>> 
>>   SANE_DEBUG_EPSON2=127 scanimage > /dev/null 2> debug.log
>> 
>> when using the epson2 backend.
>> 
>> Hope this helps,
>
> Hi,
>
> thank you. Did the two debug.log files created in both read: "scanimage: no 
> SANE devices found".

Check that the epson2 (or epson) backend is enabled (not commented out)
in /etc/sane.d/dll.conf.  Then check, as root, that the device is found
with

  scanimage -L

That ought to list the device.  Repeat that check as a normal user.  If
it does not list the device, you need to add yourself to the scanner
group and log out and back in again.  You can add yourself to the group
from the command line (as root) with

  adduser your-user-name scanner

After that scanimage -L should list the device.

> I will be times on the Sane-page look for new versions of current
> issues of sane 1.0.14-9 and I use xsane 0999-1.

WRT sane-1.014, that only contains SANE frontends.  For the device
"drivers" you need to look at sane-backends.
WRT xsane, that version is newer than the one in Debian's sid.  Sounds
like you compiled something from source.

> But possibly true for me also something wrong with the hardware
> detection Epson Perfection 1650th In the status bar to read xsane
> GT-8200 ...

That the name the Perfection 1650 is marketed as in Japan.  This is the
name that the device advertises so there is no problem with that.

However!  You say scanimage doesn't find the device but apperently your
xsane does.  That's usually a sign that you have two SANE installations
on your machine: one from the distributions libsane packages (under
/usr/lib/sane) and one compiled from source (typically under
/usr/local/lib/sane).  If that's the case get rid of one and try again.

Hope this helps,
-- 
Olaf Meeuwissen, LPIC-2           FLOSS Engineer -- AVASYS CORPORATION
FSF Associate Member #1962               Help support software freedom
                 http://www.fsf.org/jf?referrer=1962