Bug 1212027 - sane-backends: escl not working, exits with Daemon error
Summary: sane-backends: escl not working, exits with Daemon error
Status: RESOLVED NORESPONSE
Alias: None
Product: openSUSE Tumbleweed
Classification: openSUSE
Component: Printing (show other bugs)
Version: Current
Hardware: Other Other
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: Johannes Meixner
QA Contact: Johannes Meixner
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-06-05 13:45 UTC by Tiago Marques
Modified: 2024-01-05 13:06 UTC (History)
1 user (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Tiago Marques 2023-06-05 13:45:13 UTC
Was trying to print to my Epson WF-2800 to no avail, which has been working fine from Leap and Debian.

Configuration was correct with "escl" backend and I think this was working fine a while back. I tried to debug and 'scanimage' outputs:

---
SANE_DEBUG_ESCL=128 scanimage --format=pdf -v 
[14:11:29.196302] [sanei_debug] Setting debug level of escl to 128.
[14:11:29.196377] [escl] escl sane_init
[14:11:29.197196] [escl] escl sane_get_devices
[14:11:29.197222] [escl] New Escl_Device URL [http://XXXYYYZZZ:443].
[14:11:29.197235] [escl] New Escl_Device model [Epson WF-2810].
[14:11:29.197245] [escl] escl_parse_name
[14:11:29.199544] [escl] Failed to create client: Daemon not running
scanimage: no SANE devices found
[14:11:29.199568] [escl] escl sane_exit
---

On Debian scanning works with SSL or without encryption. Don't understand what is this "Daemon" error and this only shows up with DEBUG turned on.
Comment 1 Johannes Meixner 2023-06-13 06:32:41 UTC
There is nothing what I could actually do here
because I neither have an Epson WF-2800
nor another device that uses the "escl" backend
to test the "escl" backend or reproduce issues with it.

Testing scanner drivers requires actual scanner hardware
that is really physically connected to a computer.
What a scanner driver implements is basically
the bidirectional communication with a scanner device via the
particular connection type (mainly via USB and some via network)
to receive a scanned image from the scanner.
It is not possible to test scanner driver functionality
only in software because there is no software that simulates
how actual scanner hardware behaves via a particular connection.

In openSUSE Leap 15.2 there was a sane-backends version upgrade
from sane-backends-1.0.27 to sane-backends-1.0.32 which is
still used up to openSUSE Leap 15.5 - only in recent
openSUSE Leap 16.0 there is sane-backends-1.1.1 and
in openSUSE Tumbleweed there is sane-backends-1.2.1.

My blind guess is that "something changed" with
the "escl" backend in the sane-backends versions
which causes this issue here.

The openSUSE build service development project "graphics"
provides the latest sane-backends version at SUSE, see
https://build.opensuse.org/package/show/graphics/sane-backends

There the sane-backends.changes file lists
several fixes related to the "escl" backend, see
https://build.opensuse.org/package/view_file/graphics/sane-backends/sane-backends.changes?expand=1

In
https://en.opensuse.org/SDB:Configuring_Scanners
see the sections
"RPM packages of the 'sane-backends' scanner drivers"
and
"Version upgrades of scanner driver packages"
how you could try out if this issue here is fixed with
the latest sane-backends version that SUSE provides in the
openSUSE build service development project "graphics".