Bug 304131

Summary:	scangui can't connect to scanner
Product:	[Frameworks and Libraries] libksane	Reporter:	Dirk Heinrichs <dirk.heinrichs>
Component:	general	Assignee:	Kåre Särs <kare.sars>
Status:	RESOLVED UPSTREAM
Severity:	normal	CC:	caulier.gilles, kare.sars
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed In:
Attachments:	Log of scangui with SANE_DEBUG_EPKOWA=INFO Log of xsane with SANE_DEBUG_EPKOWA=INFO Log of scangui with SANE_DEBUG_EPKOWA=HEX Log of scangui with SANE_DEBUG_EPKOWA=HEX Log of scangui with SANE_DEBUG_EPKOWA=HEX Log of scangui with SANE_DEBUG_EPKOWA=HEX

Description Dirk Heinrichs 2012-07-27 09:50:53 UTC

When starting up scangui, either from the shell, or via KDE's menu, I only get a message window telling me that it "Cannot open scanner device.". Shortly before, I can see another window where I can read something containing the name of my scanner device, but it disappears too fast to give any more details. This is true for normal users as well as for root.

OTOH, scanning works fine with xsane and "Image Scan! for Linux" (the device is an Epson Stylus Office BX535WD, connected via WLAN).

Comment 1 Kåre Särs 2012-07-27 10:37:37 UTC

Hi,

Can you run scangui with sane debug enabled? 

if you are using epson2 backend:
SANE_DEBUG_EPSON2=16 scangui

or epkowa backend:
SANE_DEBUG_EPKOWA=16 scangui

Comment 2 Dirk Heinrichs 2012-07-27 11:40:49 UTC

OK, I ran

LC_ALL=C SANE_DEBUG_EPKOWA=16 scangui

but it doesn't make a difference. Nothing printed to stdout/stderr. Or should I find a logfile somewhere?

Comment 3 Dirk Heinrichs 2012-07-27 12:04:17 UTC

Created attachment 72784 [details]
Log of scangui with SANE_DEBUG_EPKOWA=INFO

Comment 4 Dirk Heinrichs 2012-07-27 12:04:58 UTC

Created attachment 72785 [details]
Log of xsane with SANE_DEBUG_EPKOWA=INFO

Comment 5 Dirk Heinrichs 2012-07-27 12:07:01 UTC

OK, got it. Debug level is not numerical for epkowa. I've attached log of the non-working scangui command and, for comparison, the one of a working xsane invocation. Both created with SANE_DEBUG_EPKOWA=INFO.

Comment 6 Dirk Heinrichs 2012-07-27 12:07:54 UTC

Oops accidentally changed resolution

Comment 7 Kåre Särs 2012-07-27 12:40:32 UTC

OK thanks,

Can you increase the log level?

Can you try with Skanlite and give the sane device name as parameter?

skanlite -d epkowa:<something...>

I don't know the format epkowa uses for WLAN models. "scanimage -L" should give you the name.

I think this is a backend bug, but it would be good to know what triggers it.

/Kåre

Comment 8 Dirk Heinrichs 2012-07-27 16:04:26 UTC

% scanimage -L
device `epkowa:net:drucker.altum.de' is a Epson Stylus NX635/SX535WD/Stylus Office BX535WD flatbed scanner

skanlite w/o any parameter shows the same behaviour. Using it with "-d epkowa:net:drucker.altum.de" works fine.

I'll attach a log with SANE_DEBUG_EPKOWA=HEX.

Comment 9 Dirk Heinrichs 2012-07-27 16:06:24 UTC

Created attachment 72792 [details]
Log of scangui with SANE_DEBUG_EPKOWA=HEX

Comment 10 Dirk Heinrichs 2012-07-27 16:06:35 UTC

Created attachment 72793 [details]
Log of scangui with SANE_DEBUG_EPKOWA=HEX

Comment 11 Dirk Heinrichs 2012-07-27 16:07:03 UTC

Created attachment 72794 [details]
Log of scangui with SANE_DEBUG_EPKOWA=HEX

Comment 12 Dirk Heinrichs 2012-07-27 16:08:04 UTC

Created attachment 72795 [details]
Log of scangui with SANE_DEBUG_EPKOWA=HEX

Comment 13 Kåre Särs 2012-07-27 21:15:11 UTC

Unfortunately I have no idea what is wrong :( 

My guess is that the backend has some problem with the timing of the probing of devices and the opening of the device...

I have sent a mail about it to the sane mailinglist

/Kåre