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).
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
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?
Created attachment 72784 [details] Log of scangui with SANE_DEBUG_EPKOWA=INFO
Created attachment 72785 [details] Log of xsane with SANE_DEBUG_EPKOWA=INFO
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.
Oops accidentally changed resolution
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
% 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.
Created attachment 72792 [details] Log of scangui with SANE_DEBUG_EPKOWA=HEX
Created attachment 72793 [details] Log of scangui with SANE_DEBUG_EPKOWA=HEX
Created attachment 72794 [details] Log of scangui with SANE_DEBUG_EPKOWA=HEX
Created attachment 72795 [details] Log of scangui with SANE_DEBUG_EPKOWA=HEX
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