Canoscan 4400F driver - update

View: New views
15 Messages — Rating Filter:   Alert me  

Canoscan 4400F driver - update

by Andreas Robinson :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hi folks,

I've been busy working on a driver for the Canoscan 4400F for a good
while and thought it best to come out with an update in case someone
wonders whether I dropped off the planet.

Yesterday, I received some unexpected help from Wim Brul, (Thanks
again!) and was finally able to get the damned contraption to send
images properly!

The attached image should give you an idea how far along it is. (Or isn't.)

Basically, I have a good grasp of how the scanner works, but there's
still a lot of work to be done on the actual driver.

The curious can visit http://github.com/andr345/gl843driver where I'm
dumping my code at irregular intervals.
(The interesting files are gl843_*.c)

It is a standalone test driver, where I've experimented with accessing
the scanner registers by name, instead of by I/O address and bit
number. It's *very* convenient, but so different from the current
Genesys driver that I'm doubting whether it can ever be merged with
it.

Anyhow, back to work! If you have questions or opinions, I'll be happy
to answer them.

Cheers,
Andreas


--
sane-devel mailing list: sane-devel@...
http://lists.alioth.debian.org/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
             to sane-devel-request@...

hello-world.jpg (26K) Download Attachment

Unknown SANE status code -1081075667

by carterbueford :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hi,

could anybody mention what is the reason for this??

Sane:
scanimage -L
WARNING: Unhandled message: interface=org.freedesktop.DBus.Introspectable,
path=/, member=Introspect
device `net:192.168.1.1:epson2:libusb:003:003' is a Epson generic flatbed
scanner

XSane:
Unknown SANE status code -1081075667

I am using a Epson all-in-one RX520 and the sane-backends optware package.

Regards
Oliver




--
sane-devel mailing list: sane-devel@...
http://lists.alioth.debian.org/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
             to sane-devel-request@...

Re: Unknown SANE status code -1081075667

by m. allan noah-3 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

network endianness mangling? does it happen if you scan with scanimage?

allan

On Sat, Oct 17, 2009 at 3:15 AM,  <carterbueford@...> wrote:

> Hi,
>
> could anybody mention what is the reason for this??
>
> Sane:
> scanimage -L
> WARNING: Unhandled message: interface=org.freedesktop.DBus.Introspectable,
> path=/, member=Introspect
> device `net:192.168.1.1:epson2:libusb:003:003' is a Epson generic flatbed
> scanner
>
> XSane:
> Unknown SANE status code -1081075667
>
> I am using a Epson all-in-one RX520 and the sane-backends optware package.
>
> Regards
> Oliver
>
>
>
>
> --
> sane-devel mailing list: sane-devel@...
> http://lists.alioth.debian.org/mailman/listinfo/sane-devel
> Unsubscribe: Send mail with subject "unsubscribe your_password"
>             to sane-devel-request@...
>



--
"The truth is an offense, but not a sin"

--
sane-devel mailing list: sane-devel@...
http://lists.alioth.debian.org/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
             to sane-devel-request@...

Re: Canoscan 4400F driver - update

by m. allan noah-3 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

sounds good. the first time you get image data is really a rush!

allan

On Fri, Oct 16, 2009 at 6:47 PM, Andreas Robinson <andr345@...> wrote:

> Hi folks,
>
> I've been busy working on a driver for the Canoscan 4400F for a good
> while and thought it best to come out with an update in case someone
> wonders whether I dropped off the planet.
>
> Yesterday, I received some unexpected help from Wim Brul, (Thanks
> again!) and was finally able to get the damned contraption to send
> images properly!
>
> The attached image should give you an idea how far along it is. (Or isn't.)
>
> Basically, I have a good grasp of how the scanner works, but there's
> still a lot of work to be done on the actual driver.
>
> The curious can visit http://github.com/andr345/gl843driver where I'm
> dumping my code at irregular intervals.
> (The interesting files are gl843_*.c)
>
> It is a standalone test driver, where I've experimented with accessing
> the scanner registers by name, instead of by I/O address and bit
> number. It's *very* convenient, but so different from the current
> Genesys driver that I'm doubting whether it can ever be merged with
> it.
>
> Anyhow, back to work! If you have questions or opinions, I'll be happy
> to answer them.
>
> Cheers,
> Andreas
>
> --
> sane-devel mailing list: sane-devel@...
> http://lists.alioth.debian.org/mailman/listinfo/sane-devel
> Unsubscribe: Send mail with subject "unsubscribe your_password"
>             to sane-devel-request@...
>



--
"The truth is an offense, but not a sin"

--
sane-devel mailing list: sane-devel@...
http://lists.alioth.debian.org/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
             to sane-devel-request@...

Re: Unknown SANE status code -1081075667

by Olaf Meeuwissen :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

<carterbueford@...> writes:

> Hi,
>
> could anybody mention what is the reason for this??
>
> Sane:
> scanimage -L
> WARNING: Unhandled message: interface=org.freedesktop.DBus.Introspectable,
> path=/, member=Introspect
> device `net:192.168.1.1:epson2:libusb:003:003' is a Epson generic flatbed
> scanner
>
> XSane:
> Unknown SANE status code -1081075667

Not initialising the status variable before returning it, most likely.
Meaning that this is probably a minor bug in the epson2 backend.

> I am using a Epson all-in-one RX520 and the sane-backends optware package.

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

--
sane-devel mailing list: sane-devel@...
http://lists.alioth.debian.org/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
             to sane-devel-request@...

Re: Unknown SANE status code -1081075667

by carterbueford :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hi,

thanks for the reply.

"Not initialising the status variable before returning it, most likely.
Meaning that this is probably a minor bug in the epson2 backend."

How can I solve this?

Regards
Oliver


-----Ursprüngliche Nachricht-----
Von: Olaf Meeuwissen [mailto:olaf.meeuwissen@...]
Gesendet: Montag, 19. Oktober 2009 01:48
An: carterbueford@...
Cc: sane-devel@...
Betreff: Re: [sane-devel] Unknown SANE status code -1081075667

<carterbueford@...> writes:

> Hi,
>
> could anybody mention what is the reason for this??
>
> Sane:
> scanimage -L
> WARNING: Unhandled message: interface=org.freedesktop.DBus.Introspectable,
> path=/, member=Introspect
> device `net:192.168.1.1:epson2:libusb:003:003' is a Epson generic flatbed
> scanner
>
> XSane:
> Unknown SANE status code -1081075667

Not initialising the status variable before returning it, most likely.
Meaning that this is probably a minor bug in the epson2 backend.

> I am using a Epson all-in-one RX520 and the sane-backends optware package.

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


--
sane-devel mailing list: sane-devel@...
http://lists.alioth.debian.org/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
             to sane-devel-request@...

Re: Unknown SANE status code -1081075667

by m. allan noah-3 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

I had a similar problem with the fujitsu backend when I built 1.0.20
on the slug a few months ago. The cross-compiler does not init vars to
0. Get a log of the problem occurring, so we can track down which
function is being called:

SANE_DEBUG_NET=10 xsane... 2>net.log

Also, does it happen with scanimage too, or does it happen on the slug
if you scan there with scanimage directly?

allan

On Mon, Oct 19, 2009 at 12:52 PM,  <carterbueford@...> wrote:

> Hi,
>
> thanks for the reply.
>
> "Not initialising the status variable before returning it, most likely.
> Meaning that this is probably a minor bug in the epson2 backend."
>
> How can I solve this?
>
> Regards
> Oliver
>
>
> -----Ursprüngliche Nachricht-----
> Von: Olaf Meeuwissen [mailto:olaf.meeuwissen@...]
> Gesendet: Montag, 19. Oktober 2009 01:48
> An: carterbueford@...
> Cc: sane-devel@...
> Betreff: Re: [sane-devel] Unknown SANE status code -1081075667
>
> <carterbueford@...> writes:
>
>> Hi,
>>
>> could anybody mention what is the reason for this??
>>
>> Sane:
>> scanimage -L
>> WARNING: Unhandled message: interface=org.freedesktop.DBus.Introspectable,
>> path=/, member=Introspect
>> device `net:192.168.1.1:epson2:libusb:003:003' is a Epson generic flatbed
>> scanner
>>
>> XSane:
>> Unknown SANE status code -1081075667
>
> Not initialising the status variable before returning it, most likely.
> Meaning that this is probably a minor bug in the epson2 backend.
>
>> I am using a Epson all-in-one RX520 and the sane-backends optware package.
>
> 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
>
>
> --
> sane-devel mailing list: sane-devel@...
> http://lists.alioth.debian.org/mailman/listinfo/sane-devel
> Unsubscribe: Send mail with subject "unsubscribe your_password"
>             to sane-devel-request@...
>



--
"The truth is an offense, but not a sin"

--
sane-devel mailing list: sane-devel@...
http://lists.alioth.debian.org/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
             to sane-devel-request@...

Re: Unknown SANE status code -1081075667

by Olaf Meeuwissen :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

"m. allan noah" <kitno455@...> writes:

> I had a similar problem with the fujitsu backend when I built 1.0.20
> on the slug a few months ago. The cross-compiler does not init vars to
> 0.

Eh, if you don't tell it to do so, yes.  Using variables before
initialisation has been undefined behaviour since as long as I
know.

> Get a log of the problem occurring, so we can track down which
> function is being called:

Compile the backend with gcc -Wall -Werror should give a cluebat.

> SANE_DEBUG_NET=10 xsane... 2>net.log
>
> Also, does it happen with scanimage too, or does it happen on the slug
> if you scan there with scanimage directly?
>
> allan
>
> On Mon, Oct 19, 2009 at 12:52 PM,  <carterbueford@...> wrote:
>> Hi,
>>
>> thanks for the reply.
>>
>> "Not initialising the status variable before returning it, most likely.
>> Meaning that this is probably a minor bug in the epson2 backend."
>>
>> How can I solve this?
>>
>> Regards
>> Oliver
>>
>>
>> -----Ursprüngliche Nachricht-----
>> Von: Olaf Meeuwissen [mailto:olaf.meeuwissen@...]
>> Gesendet: Montag, 19. Oktober 2009 01:48
>> An: carterbueford@...
>> Cc: sane-devel@...
>> Betreff: Re: [sane-devel] Unknown SANE status code -1081075667
>>
>> <carterbueford@...> writes:
>>
>>> Hi,
>>>
>>> could anybody mention what is the reason for this??
>>>
>>> Sane:
>>> scanimage -L
>>> WARNING: Unhandled message: interface=org.freedesktop.DBus.Introspectable,
>>> path=/, member=Introspect
>>> device `net:192.168.1.1:epson2:libusb:003:003' is a Epson generic flatbed
>>> scanner
>>>
>>> XSane:
>>> Unknown SANE status code -1081075667
>>
>> Not initialising the status variable before returning it, most likely.
>> Meaning that this is probably a minor bug in the epson2 backend.
>>
>>> I am using a Epson all-in-one RX520 and the sane-backends optware package.
>>
>> 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
>>
>>
>> --
>> sane-devel mailing list: sane-devel@...
>> http://lists.alioth.debian.org/mailman/listinfo/sane-devel
>> Unsubscribe: Send mail with subject "unsubscribe your_password"
>>             to sane-devel-request@...
>>

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

--
sane-devel mailing list: sane-devel@...
http://lists.alioth.debian.org/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
             to sane-devel-request@...

Re: Unknown SANE status code -1081075667

by carterbueford :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hi,

@allan: I do not run xsane on the same mashine like the sane-server, so I do not understand how to write the log you want me to.
"xsane... 2>net.log"
sanimage on the mashine where the sane-server runs, works fine.

@Olaf:"Compile the backend with gcc -Wall -Werror should give a cluebat." What is meant by that?
I'm using the optware package, so it is not compiled on my router. I am maintainer of the package, so I can patch it to be compiled in a different way, but how?

Regards
Oliver



-----Ursprüngliche Nachricht-----
Von: Olaf Meeuwissen [mailto:olaf.meeuwissen@...]
Gesendet: Dienstag, 20. Oktober 2009 01:05
An: m. allan noah
Cc: carterbueford@...; sane-devel@...
Betreff: Re: [sane-devel] Unknown SANE status code -1081075667

"m. allan noah" <kitno455@...> writes:

> I had a similar problem with the fujitsu backend when I built 1.0.20
> on the slug a few months ago. The cross-compiler does not init vars to
> 0.

Eh, if you don't tell it to do so, yes.  Using variables before
initialisation has been undefined behaviour since as long as I
know.

> Get a log of the problem occurring, so we can track down which
> function is being called:

Compile the backend with gcc -Wall -Werror should give a cluebat.

> SANE_DEBUG_NET=10 xsane... 2>net.log
>
> Also, does it happen with scanimage too, or does it happen on the slug
> if you scan there with scanimage directly?
>
> allan
>
> On Mon, Oct 19, 2009 at 12:52 PM,  <carterbueford@...> wrote:
>> Hi,
>>
>> thanks for the reply.
>>
>> "Not initialising the status variable before returning it, most likely.
>> Meaning that this is probably a minor bug in the epson2 backend."
>>
>> How can I solve this?
>>
>> Regards
>> Oliver
>>
>>
>> -----Ursprüngliche Nachricht-----
>> Von: Olaf Meeuwissen [mailto:olaf.meeuwissen@...]
>> Gesendet: Montag, 19. Oktober 2009 01:48
>> An: carterbueford@...
>> Cc: sane-devel@...
>> Betreff: Re: [sane-devel] Unknown SANE status code -1081075667
>>
>> <carterbueford@...> writes:
>>
>>> Hi,
>>>
>>> could anybody mention what is the reason for this??
>>>
>>> Sane:
>>> scanimage -L
>>> WARNING: Unhandled message: interface=org.freedesktop.DBus.Introspectable,
>>> path=/, member=Introspect
>>> device `net:192.168.1.1:epson2:libusb:003:003' is a Epson generic flatbed
>>> scanner
>>>
>>> XSane:
>>> Unknown SANE status code -1081075667
>>
>> Not initialising the status variable before returning it, most likely.
>> Meaning that this is probably a minor bug in the epson2 backend.
>>
>>> I am using a Epson all-in-one RX520 and the sane-backends optware package.
>>
>> 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
>>
>>
>> --
>> sane-devel mailing list: sane-devel@...
>> http://lists.alioth.debian.org/mailman/listinfo/sane-devel
>> Unsubscribe: Send mail with subject "unsubscribe your_password"
>>             to sane-devel-request@...
>>

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


--
sane-devel mailing list: sane-devel@...
http://lists.alioth.debian.org/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
             to sane-devel-request@...

Re: Unknown SANE status code -1081075667

by m. allan noah-3 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

On Tue, Oct 20, 2009 at 2:49 AM,  <carterbueford@...> wrote:
> Hi,
>
> @allan: I do not run xsane on the same mashine like the sane-server, so I do not understand how to write the log you want me to.
> "xsane... 2>net.log"

easy, open a terminal window on the scanning client, and run the
command i gave you.

> sanimage on the mashine where the sane-server runs, works fine.

what about scanimage on the client machine?

Tthere are three likely sources for this error:

1. xsane makes different API calls than scanimage, and triggers a bug in epson2
2. net backend munges the data
3. saned munges the data

> @Olaf:"Compile the backend with gcc -Wall -Werror should give a cluebat." What is meant by that?
> I'm using the optware package, so it is not compiled on my router. I am maintainer of the package, so I can patch it to be compiled in a different way, but how?

if you maintain the package, you should know how to modify the .bb
file to add arguments to the gcc call. Something like CFLAGS="-Wall
-Werror"

bitbake puts its compilation output someplace funny, you'll have to
look for the log...

allan
--
"The truth is an offense, but not a sin"

--
sane-devel mailing list: sane-devel@...
http://lists.alioth.debian.org/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
             to sane-devel-request@...

Re: Unknown SANE status code -1081075667

by carterbueford :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hi,

"easy, open a terminal window on the scanning client, and run the
command i gave you."

Does not work. I am using Windows XP and after executing the command, the
log is empty.
Command I used:
C:\sane\bin>xsane 2>net.log

"SANE_DEBUG_NET=10" Where do I have to execute this command? It only works
on my router.

"what about scanimage on the client machine?"
Works!

"if you maintain the package, you should know how to modify the .bb
file to add arguments to the gcc call. Something like CFLAGS="-Wall
-Werror"
Yes, no problem to set the flags, but I did not understand what effect it
will have. Is this option for debugging or to solve the problem after
compiling?

Regards
Oliver




-----Ursprüngliche Nachricht-----
Von: m. allan noah [mailto:kitno455@...]
Gesendet: Dienstag, 20. Oktober 2009 14:41
An: carterbueford@...
Cc: Olaf Meeuwissen; sane-devel@...
Betreff: Re: [sane-devel] Unknown SANE status code -1081075667

On Tue, Oct 20, 2009 at 2:49 AM,  <carterbueford@...> wrote:
> Hi,
>
> @allan: I do not run xsane on the same mashine like the sane-server, so I
do not understand how to write the log you want me to.
> "xsane... 2>net.log"

easy, open a terminal window on the scanning client, and run the
command i gave you.

> sanimage on the mashine where the sane-server runs, works fine.

what about scanimage on the client machine?

Tthere are three likely sources for this error:

1. xsane makes different API calls than scanimage, and triggers a bug in
epson2
2. net backend munges the data
3. saned munges the data

> @Olaf:"Compile the backend with gcc -Wall -Werror should give a cluebat."
What is meant by that?
> I'm using the optware package, so it is not compiled on my router. I am
maintainer of the package, so I can patch it to be compiled in a different
way, but how?

if you maintain the package, you should know how to modify the .bb
file to add arguments to the gcc call. Something like CFLAGS="-Wall
-Werror"

bitbake puts its compilation output someplace funny, you'll have to
look for the log...

allan
--
"The truth is an offense, but not a sin"


--
sane-devel mailing list: sane-devel@...
http://lists.alioth.debian.org/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
             to sane-devel-request@...

Re: Unknown SANE status code -1081075667

by m. allan noah-3 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

On Thu, Oct 22, 2009 at 1:17 AM,  <carterbueford@...> wrote:
> Hi,
>
> "easy, open a terminal window on the scanning client, and run the
> command i gave you."
>
> Does not work. I am using Windows XP and after executing the command, the
> log is empty.
> Command I used:
> C:\sane\bin>xsane 2>net.log

ahh- somewhere along the way you should have mentioned that windows
was involved. You might try asking the author of xsane...

> "SANE_DEBUG_NET=10" Where do I have to execute this command? It only works
> on my router.

this sets an enviroment variable in unix, you put it on the same
command line right before you call the program, just like i typed it
before.

> "what about scanimage on the client machine?"
> Works!
>
> "if you maintain the package, you should know how to modify the .bb
> file to add arguments to the gcc call. Something like CFLAGS="-Wall
> -Werror"
> Yes, no problem to set the flags, but I did not understand what effect it
> will have. Is this option for debugging or to solve the problem after
> compiling?

the -W options to gcc make it give more warnings at compile time. you
will have to find the bitbake logfile to see the noise.

but frankly, I am now thinking the windows compile of xsane might be
part of the problem. The easiest way to know would be for you to
install a real OS on your machine (i.e. Linux, perhaps in a VM), and
make sure that you can scan over the network.

allan

>
> Regards
> Oliver
>
>
>
>
> -----Ursprüngliche Nachricht-----
> Von: m. allan noah [mailto:kitno455@...]
> Gesendet: Dienstag, 20. Oktober 2009 14:41
> An: carterbueford@...
> Cc: Olaf Meeuwissen; sane-devel@...
> Betreff: Re: [sane-devel] Unknown SANE status code -1081075667
>
> On Tue, Oct 20, 2009 at 2:49 AM,  <carterbueford@...> wrote:
>> Hi,
>>
>> @allan: I do not run xsane on the same mashine like the sane-server, so I
> do not understand how to write the log you want me to.
>> "xsane... 2>net.log"
>
> easy, open a terminal window on the scanning client, and run the
> command i gave you.
>
>> sanimage on the mashine where the sane-server runs, works fine.
>
> what about scanimage on the client machine?
>
> Tthere are three likely sources for this error:
>
> 1. xsane makes different API calls than scanimage, and triggers a bug in
> epson2
> 2. net backend munges the data
> 3. saned munges the data
>
>> @Olaf:"Compile the backend with gcc -Wall -Werror should give a cluebat."
> What is meant by that?
>> I'm using the optware package, so it is not compiled on my router. I am
> maintainer of the package, so I can patch it to be compiled in a different
> way, but how?
>
> if you maintain the package, you should know how to modify the .bb
> file to add arguments to the gcc call. Something like CFLAGS="-Wall
> -Werror"
>
> bitbake puts its compilation output someplace funny, you'll have to
> look for the log...
>
> allan
> --
> "The truth is an offense, but not a sin"
>
>



--
"The truth is an offense, but not a sin"

--
sane-devel mailing list: sane-devel@...
http://lists.alioth.debian.org/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
             to sane-devel-request@...

Parent Message unknown Re: Unknown SANE status code -1081075667

by carterbueford :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hi at all,

I've got the following error trying to scan with my Epson Stylus Photo RX640
over XSane.

>> >> [sanei_debug] Setting debug level of epson2 to 128.
>> >> [epson2] sane_epson2_init: sane-backends 1.0.19
>> >> [epson2] sane_epson2_init: reading config file, epson2.conf
>> >> [epson2]  scsi EPSON
>> >> [epson2]  usb
>> >> [epson2] attach_one_usb: dev =
>> >> [epson2] SANE Epson 2 Backend v0.1.16 - 2007-12-30
>> >> [epson2] attach: devname = , type = 3
>> >> [epson2] attach: opening , type = 3
>> >> [epson2]  net autodiscovery
>> >> [epson2] attach_one_net: dev = autodiscovery
>> >> [epson2] SANE Epson 2 Backend v0.1.16 - 2007-12-30
>> >> [epson2] attach: devname = autodiscovery, type = 4
>> >> [epson2] attach: opening autodiscovery, type = 4
>> >> [epson2] e2_network_discovery, sent discovery packet
>> >> [epson2] e2_network_discovery, end
>> >> [epson2] close_scanner: fd = -1
>> >> [epson2] sane_epson2_get_devices

Simple scanimage from server mashine and client PC works.

Any ideas.

Regards
Oliver
 

-----Ursprüngliche Nachricht-----
Von: m. allan noah [mailto:kitno455@...]
Gesendet: Montag, 26. Oktober 2009 13:27
An: Oliver Polch
Betreff: Re: [sane-devel] Unknown SANE status code -1081075667

xsane cannot speak over the network. it has some portion of sane
(perhaps just the net backend) installed inside it.

I am not sure what you can do to fix this- how about this: can you get
the scanner setup via USB in your linux VM? then share it with the
windows host via saned, and see if the same problem occurs. That will
tell us if the compile on the router is part of the problem...

allan

On Mon, Oct 26, 2009 at 6:31 AM, Oliver Polch <CarterBueford@...> wrote:

> Hi,
>
> on the client there is no sane, only XSane 0,996.
> On the server there is sane-backends, the latest git.
>
> Regards
> Oliver
>
> -------- Original-Nachricht --------
>> Datum: Sun, 25 Oct 2009 16:15:10 -0400
>> Von: "m. allan noah" <kitno455@...>
>> An: carterbueford@...
>> Betreff: Re: [sane-devel] Unknown SANE status code -1081075667
>
>> hmm- notice that there are no messages from epson2 prior to the
>> segfault. strange. what version of sane is in use on the client
>> machine?
>>
>> allan
>>
>> On Sun, Oct 25, 2009 at 10:18 AM,  <carterbueford@...> wrote:
>> > Hi Allan,
>> >
>> > see the attached logfile.
>> >
>> > Regards
>> > Oliver
>> >
>> >
>> > -----Ursprüngliche Nachricht-----
>> > Von: m. allan noah [mailto:kitno455@...]
>> > Gesendet: Sonntag, 25. Oktober 2009 12:43
>> > An: Oliver Polch
>> > Betreff: Re: [sane-devel] Unknown SANE status code -1081075667
>> >
>> > ahh, yes- this won't work on the client machine. we instead need to
>> > set it somehow in the xinetd config, and send the output into a file
>> > that the user can write to. I've never done that before, you'll have
>> > to figure it out.
>> >
>> > allan
>> >
>> > On Sun, Oct 25, 2009 at 5:25 AM, Oliver Polch <CarterBueford@...>
>> wrote:
>> >> Hi,
>> >>
>> >> here is the log:
>> >>
>> >> [sanei_debug] Setting debug level of epson2 to 128.
>> >> [epson2] sane_epson2_init: sane-backends 1.0.19
>> >> [epson2] sane_epson2_init: reading config file, epson2.conf
>> >> [epson2]  scsi EPSON
>> >> [epson2]  usb
>> >> [epson2] attach_one_usb: dev =
>> >> [epson2] SANE Epson 2 Backend v0.1.16 - 2007-12-30
>> >> [epson2] attach: devname = , type = 3
>> >> [epson2] attach: opening , type = 3
>> >> [epson2]  net autodiscovery
>> >> [epson2] attach_one_net: dev = autodiscovery
>> >> [epson2] SANE Epson 2 Backend v0.1.16 - 2007-12-30
>> >> [epson2] attach: devname = autodiscovery, type = 4
>> >> [epson2] attach: opening autodiscovery, type = 4
>> >> [epson2] e2_network_discovery, sent discovery packet
>> >> [epson2] e2_network_discovery, end
>> >> [epson2] close_scanner: fd = -1
>> >> [epson2] sane_epson2_get_devices
>> >>
>> >> Regards
>> >> Oliver
>> >>
>> >>
>> >> -------- Original-Nachricht --------
>> >>> Datum: Sat, 24 Oct 2009 16:05:37 -0400
>> >>> Von: "m. allan noah" <kitno455@...>
>> >>> An: Oliver Polch <CarterBueford@...>
>> >>> Betreff: Re: [sane-devel] Unknown SANE status code -1081075667
>> >>
>> >>> try with epson2 debug instead:
>> >>>
>> >>> SANE_DEBUG_EPSON2=128 xsane 2>ep2.log
>> >>>
>> >>> allan
>> >>>
>> >>> On Sat, Oct 24, 2009 at 3:52 PM, Oliver Polch <CarterBueford@...>
>> >>> wrote:
>> >>> > Hi,
>> >>> >
>> >>> > here is the logfile:
>> >>> >
>> >>> > [sanei_debug] Setting debug level of net to 10.
>> >>> > [net] sane_init: authorize = 0x413a70, version_code =
0x7fff8a519aa4

>> >>> > [net] sane_init: SANE net backend version 1.0.14 (AF-indep+IPv6)
>> from
>> >>> sane-backends 1.0.19
>> >>> > [net] sane_init: Client has little endian byte order
>> >>> > [net] sane_init: searching for config file
>> >>> > [net] net_avahi_browse_callback: CACHE_EXHAUSTED
>> >>> > [net] sane_init: trying to add 192.168.1.1
>> >>> > [net] add_device: adding backend 192.168.1.1
>> >>> > [net] add_device: backend 192.168.1.1 added
>> >>> > [net] sane_init: done reading config
>> >>> > [net] sane_init: evaluating environment variable SANE_NET_HOSTS
>> >>> > [net] sane_init: evaluating environment variable SANE_NET_TIMEOUT
>> >>> > [net] sane_init: done
>> >>> > [net] sane_get_devices: local_only = 0
>> >>> > [net] connect_dev: trying to connect to 192.168.1.1
>> >>> > [net] connect_dev: [0] connection succeeded (IPv4)
>> >>> > [net] connect_dev: sanei_w_init
>> >>> > [net] connect_dev: net_init (user=ram32, local version=1.0.3)
>> >>> > [net] connect_dev: freeing init reply (status=Success, remote
>> >>> version=1.0.3)
>> >>> > [net] connect_dev: done
>> >>> > [net] net_avahi_browse_callback: ALL_FOR_NOW
>> >>> > [net] sane_get_devices: got 192.168.1.1:epson2:libusb:002:004
>> >>> > [net] sane_get_devices: finished (1 devices)
>> >>> > [net] sane_open("192.168.1.1:epson2:libusb:002:004")
>> >>> > [net] sane_open: host = 192.168.1.1, device = epson2:libusb:002:004
>> >>> > [net] sane_open: device found in list
>> >>> > [net] sane_open: net_open
>> >>> > [net] sane_open: getting option descriptors
>> >>> > [net] fetch_options: 0x2782510
>> >>> > [net] fetch_options: get_option_descriptors
>> >>> > [net] fetch_options: creating 45 local option descriptors
>> >>> > [net] fetch_options: copying 45 option descriptors
>> >>> > [net] fetch_options: 45 options fetched
>> >>> > [net] sane_open: success
>> >>> > [net] sane_control_option: option 0, action 0
>> >>> > [net] sane_control_option: remote control option
>> >>> > [net] sane_control_option: remote done (Success, info 0)
>> >>> > [net] sane_control_option: done (Success, info 0)
>> >>> > [net] sane_get_option_descriptor: option 1
>> >>> > [net] sane_get_option_descriptor: option 2
>> >>> > [net] sane_get_option_descriptor: option 2
>> >>> > [net] sane_control_option: option 2, action 0
>> >>> > [net] sane_control_option: remote control option
>> >>> > [net] sane_control_option: remote done (Success, info 0)
>> >>> > [net] sane_control_option: done (Success, info 0)
>> >>> > [net] sane_get_option_descriptor: option 3
>> >>> > [net] sane_get_option_descriptor: option 4
>> >>> > [net] sane_get_option_descriptor: option 5
>> >>> > [net] sane_get_option_descriptor: option 5
>> >>> > [net] sane_control_option: option 5, action 0
>> >>> > [net] sane_control_option: remote control option
>> >>> > [net] sane_control_option: remote done (Success, info 0)
>> >>> > [net] sane_control_option: done (Success, info 0)
>> >>> > [net] sane_get_option_descriptor: option 6
>> >>> > [net] sane_get_option_descriptor: option 7
>> >>> > [net] sane_get_option_descriptor: option 8
>> >>> > [net] sane_get_option_descriptor: option 8
>> >>> > [net] sane_control_option: option 8, action 0
>> >>> > [net] sane_control_option: remote control option
>> >>> > [net] sane_control_option: remote done (Success, info 0)
>> >>> > [net] sane_control_option: done (Success, info 0)
>> >>> > [net] sane_get_option_descriptor: option 9
>> >>> > [net] sane_get_option_descriptor: option 10
>> >>> > [net] sane_get_option_descriptor: option 10
>> >>> > [net] sane_control_option: option 10, action 0
>> >>> > [net] sane_control_option: remote control option
>> >>> > [net] sane_control_option: remote done (Success, info 0)
>> >>> > [net] sane_control_option: done (Success, info 0)
>> >>> > [net] sane_get_option_descriptor: option 11
>> >>> > [net] sane_get_option_descriptor: option 12
>> >>> > [net] sane_get_option_descriptor: option 13
>> >>> > [net] sane_get_option_descriptor: option 14
>> >>> > [net] sane_get_option_descriptor: option 15
>> >>> > [net] sane_get_option_descriptor: option 15
>> >>> > [net] sane_control_option: option 15, action 0
>> >>> > [net] sane_control_option: remote control option
>> >>> > [net] sane_control_option: remote done (Success, info 0)
>> >>> > [net] sane_control_option: done (Success, info 0)
>> >>> > [net] sane_get_option_descriptor: option 16
>> >>> > [net] sane_get_option_descriptor: option 17
>> >>> > [net] sane_get_option_descriptor: option 18
>> >>> > [net] sane_get_option_descriptor: option 19
>> >>> > [net] sane_get_option_descriptor: option 19
>> >>> > [net] sane_control_option: option 19, action 0
>> >>> > [net] sane_control_option: remote control option
>> >>> > [net] sane_control_option: remote done (Success, info 0)
>> >>> > [net] sane_control_option: done (Success, info 0)
>> >>> > [net] sane_get_option_descriptor: option 20
>> >>> > [net] sane_get_option_descriptor: option 21
>> >>> > [net] sane_get_option_descriptor: option 22
>> >>> > [net] sane_get_option_descriptor: option 23
>> >>> > [net] sane_get_option_descriptor: option 24
>> >>> > [net] sane_get_option_descriptor: option 25
>> >>> > [net] sane_get_option_descriptor: option 26
>> >>> > [net] sane_get_option_descriptor: option 27
>> >>> > [net] sane_get_option_descriptor: option 28
>> >>> > [net] sane_get_option_descriptor: option 29
>> >>> > [net] sane_get_option_descriptor: option 30
>> >>> > [net] sane_get_option_descriptor: option 31
>> >>> > [net] sane_get_option_descriptor: option 32
>> >>> > [net] sane_get_option_descriptor: option 33
>> >>> > [net] sane_get_option_descriptor: option 33
>> >>> > [net] sane_control_option: option 33, action 0
>> >>> > [net] sane_control_option: remote control option
>> >>> > [net] sane_control_option: remote done (Success, info 0)
>> >>> > [net] sane_control_option: done (Success, info 0)
>> >>> > [net] sane_get_option_descriptor: option 34
>> >>> > [net] sane_get_option_descriptor: option 34
>> >>> > [net] sane_control_option: option 34, action 0
>> >>> > [net] sane_control_option: remote control option
>> >>> > [net] sane_control_option: remote done (Success, info 0)
>> >>> > [net] sane_control_option: done (Success, info 0)
>> >>> > [net] sane_get_option_descriptor: option 35
>> >>> > [net] sane_get_option_descriptor: option 35
>> >>> > [net] sane_control_option: option 35, action 0
>> >>> > [net] sane_control_option: remote control option
>> >>> > [net] sane_control_option: remote done (Success, info 0)
>> >>> > [net] sane_control_option: done (Success, info 0)
>> >>> > [net] sane_get_option_descriptor: option 36
>> >>> > [net] sane_get_option_descriptor: option 36
>> >>> > [net] sane_control_option: option 36, action 0
>> >>> > [net] sane_control_option: remote control option
>> >>> > [net] sane_control_option: remote done (Success, info 0)
>> >>> > [net] sane_control_option: done (Success, info 0)
>> >>> > [net] sane_get_option_descriptor: option 37
>> >>> > [net] sane_get_option_descriptor: option 38
>> >>> > [net] sane_get_option_descriptor: option 38
>> >>> > [net] sane_control_option: option 38, action 0
>> >>> > [net] sane_control_option: remote control option
>> >>> > [net] sane_control_option: remote done (Success, info 0)
>> >>> > [net] sane_control_option: done (Success, info 0)
>> >>> > [net] sane_get_option_descriptor: option 39
>> >>> > [net] sane_get_option_descriptor: option 40
>> >>> > [net] sane_get_option_descriptor: option 41
>> >>> > [net] sane_get_option_descriptor: option 42
>> >>> > [net] sane_get_option_descriptor: option 43
>> >>> > [net] sane_get_option_descriptor: option 44
>> >>> > [net] sane_get_option_descriptor: option 38
>> >>> > [net] sane_get_option_descriptor: option 38
>> >>> > [net] sane_control_option: option 38, action 0
>> >>> > [net] sane_control_option: remote control option
>> >>> > [net] sane_control_option: remote done (Success, info 0)
>> >>> > [net] sane_control_option: done (Success, info 0)
>> >>> > [net] sane_get_option_descriptor: option 2
>> >>> > [net] sane_get_option_descriptor: option 2
>> >>> > [net] sane_control_option: option 2, action 0
>> >>> > [net] sane_control_option: remote control option
>> >>> > [net] sane_control_option: auth required
>> >>> > [net]
>> >>> >
>> >>> >
>> >>> > Regards
>> >>> > Oliver
>> >>> >
>> >>> >
>> >>> > -------- Original-Nachricht --------
>> >>> >> Datum: Sat, 24 Oct 2009 08:44:23 -0400
>> >>> >> Von: "m. allan noah" <kitno455@...>
>> >>> >> An: carterbueford@...
>> >>> >> Betreff: Re: [sane-devel] Unknown SANE status code -1081075667
>> >>> >
>> >>> >> now get the xsane debug log i asked for on your ubuntu vm...
>> >>> >>
>> >>> >> allan
>> >>> >>
>> >>> >> On Sat, Oct 24, 2009 at 8:36 AM,  <carterbueford@...> wrote:
>> >>> >> > Hi,
>> >>> >> >
>> >>> >> > I have Ubuntu running in a VM, XSane still doesn't work,
>> scanimage
>> >>> does.
>> >>> >> > Might be a problem with XSane and epson2?
>> >>> >> >
>> >>> >> > Seems not to be a problem with the windows-version of XSane.
>> >>> >> >
>> >>> >> > I'm going to crosscompile a new version of sane-backends with
the

>> >>> flags
>> >>> >> and
>> >>> >> > take a look at the logs.
>> >>> >> >
>> >>> >> > Regards
>> >>> >> > Oliver
>> >>> >> >
>> >>> >> > -----Ursprüngliche Nachricht-----
>> >>> >> > Von: m. allan noah [mailto:kitno455@...]
>> >>> >> > Gesendet: Donnerstag, 22. Oktober 2009 14:46
>> >>> >> > An: carterbueford@...
>> >>> >> > Cc: sane-devel@...
>> >>> >> > Betreff: Re: [sane-devel] Unknown SANE status code -1081075667
>> >>> >> >
>> >>> >> > On Thu, Oct 22, 2009 at 1:17 AM,  <carterbueford@...> wrote:
>> >>> >> >> Hi,
>> >>> >> >>
>> >>> >> >> "easy, open a terminal window on the scanning client, and run
>> the
>> >>> >> >> command i gave you."
>> >>> >> >>
>> >>> >> >> Does not work. I am using Windows XP and after executing the
>> >>> command,
>> >>> >> the
>> >>> >> >> log is empty.
>> >>> >> >> Command I used:
>> >>> >> >> C:\sane\bin>xsane 2>net.log
>> >>> >> >
>> >>> >> > ahh- somewhere along the way you should have mentioned that
>> windows
>> >>> >> > was involved. You might try asking the author of xsane...
>> >>> >> >
>> >>> >> >> "SANE_DEBUG_NET=10" Where do I have to execute this command? It
>> > only
>> >>> >> works
>> >>> >> >> on my router.
>> >>> >> >
>> >>> >> > this sets an enviroment variable in unix, you put it on the same
>> >>> >> > command line right before you call the program, just like i
typed

>> it
>> >>> >> > before.
>> >>> >> >
>> >>> >> >> "what about scanimage on the client machine?"
>> >>> >> >> Works!
>> >>> >> >>
>> >>> >> >> "if you maintain the package, you should know how to modify the
>> .bb
>> >>> >> >> file to add arguments to the gcc call. Something like
>> CFLAGS="-Wall
>> >>> >> >> -Werror"
>> >>> >> >> Yes, no problem to set the flags, but I did not understand what
>> >>> effect
>> >>> >> it
>> >>> >> >> will have. Is this option for debugging or to solve the problem
>> >>> after
>> >>> >> >> compiling?
>> >>> >> >
>> >>> >> > the -W options to gcc make it give more warnings at compile
time.
>> > you
>> >>> >> > will have to find the bitbake logfile to see the noise.
>> >>> >> >
>> >>> >> > but frankly, I am now thinking the windows compile of xsane
might

>> be
>> >>> >> > part of the problem. The easiest way to know would be for you to
>> >>> >> > install a real OS on your machine (i.e. Linux, perhaps in a VM),
>> and
>> >>> >> > make sure that you can scan over the network.
>> >>> >> >
>> >>> >> > allan
>> >>> >> >
>> >>> >> >>
>> >>> >> >> Regards
>> >>> >> >> Oliver
>> >>> >> >>
>> >>> >> >>
>> >>> >> >>
>> >>> >> >>
>> >>> >> >> -----Ursprüngliche Nachricht-----
>> >>> >> >> Von: m. allan noah [mailto:kitno455@...]
>> >>> >> >> Gesendet: Dienstag, 20. Oktober 2009 14:41
>> >>> >> >> An: carterbueford@...
>> >>> >> >> Cc: Olaf Meeuwissen; sane-devel@...
>> >>> >> >> Betreff: Re: [sane-devel] Unknown SANE status code -1081075667
>> >>> >> >>
>> >>> >> >> On Tue, Oct 20, 2009 at 2:49 AM,  <carterbueford@...>
>> wrote:
>> >>> >> >>> Hi,
>> >>> >> >>>
>> >>> >> >>> @allan: I do not run xsane on the same mashine like the
>> >>> sane-server,
>> >>> >> so I
>> >>> >> >> do not understand how to write the log you want me to.
>> >>> >> >>> "xsane... 2>net.log"
>> >>> >> >>
>> >>> >> >> easy, open a terminal window on the scanning client, and run
the
>> >>> >> >> command i gave you.
>> >>> >> >>
>> >>> >> >>> sanimage on the mashine where the sane-server runs, works
fine.

>> >>> >> >>
>> >>> >> >> what about scanimage on the client machine?
>> >>> >> >>
>> >>> >> >> Tthere are three likely sources for this error:
>> >>> >> >>
>> >>> >> >> 1. xsane makes different API calls than scanimage, and triggers
>> a
>> >>> bug
>> >>> >> in
>> >>> >> >> epson2
>> >>> >> >> 2. net backend munges the data
>> >>> >> >> 3. saned munges the data
>> >>> >> >>
>> >>> >> >>> @Olaf:"Compile the backend with gcc -Wall -Werror should give
a
>> >>> >> cluebat."
>> >>> >> >> What is meant by that?
>> >>> >> >>> I'm using the optware package, so it is not compiled on my
>> router.
>> >>> I
>> >>> >> am
>> >>> >> >> maintainer of the package, so I can patch it to be compiled in
a

>> >>> >> different
>> >>> >> >> way, but how?
>> >>> >> >>
>> >>> >> >> if you maintain the package, you should know how to modify the
>> .bb
>> >>> >> >> file to add arguments to the gcc call. Something like
>> CFLAGS="-Wall
>> >>> >> >> -Werror"
>> >>> >> >>
>> >>> >> >> bitbake puts its compilation output someplace funny, you'll
have

>> to
>> >>> >> >> look for the log...
>> >>> >> >>
>> >>> >> >> allan
>> >>> >> >> --
>> >>> >> >> "The truth is an offense, but not a sin"
>> >>> >> >>
>> >>> >> >>
>> >>> >> >
>> >>> >> >
>> >>> >> >
>> >>> >> > --
>> >>> >> > "The truth is an offense, but not a sin"
>> >>> >> >
>> >>> >> >
>> >>> >>
>> >>> >>
>> >>> >>
>> >>> >> --
>> >>> >> "The truth is an offense, but not a sin"
>> >>> >
>> >>> > --
>> >>> > Jetzt kostenlos herunterladen: Internet Explorer 8 und Mozilla
>> Firefox
>> >>> 3.5 -
>> >>> > sicherer, schneller und einfacher!
>> > http://portal.gmx.net/de/go/chbrowser
>> >>> >
>> >>>
>> >>>
>> >>>
>> >>> --
>> >>> "The truth is an offense, but not a sin"
>> >>
>> >> --
>> >> Neu: GMX DSL bis 50.000 kBit/s und 200,- Euro Startguthaben!
>> >> http://portal.gmx.net/de/go/dsl02
>> >>
>> >
>> >
>> >
>> > --
>> > "The truth is an offense, but not a sin"
>> >
>>
>>
>>
>> --
>> "The truth is an offense, but not a sin"
>
> --
> Jetzt kostenlos herunterladen: Internet Explorer 8 und Mozilla Firefox 3.5
-
> sicherer, schneller und einfacher! http://portal.gmx.net/de/go/atbrowser
>



--
"The truth is an offense, but not a sin"


--
sane-devel mailing list: sane-devel@...
http://lists.alioth.debian.org/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
             to sane-devel-request@...

Re: Unknown SANE status code -1081075667

by m. allan noah-3 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

On Mon, Oct 26, 2009 at 1:12 PM,  <carterbueford@...> wrote:

> Hi at all,
>
> I've got the following error trying to scan with my Epson Stylus Photo RX640
> over XSane.
>
>>> >> [sanei_debug] Setting debug level of epson2 to 128.
>>> >> [epson2] sane_epson2_init: sane-backends 1.0.19
>>> >> [epson2] sane_epson2_init: reading config file, epson2.conf
>>> >> [epson2]  scsi EPSON
>>> >> [epson2]  usb
>>> >> [epson2] attach_one_usb: dev =
>>> >> [epson2] SANE Epson 2 Backend v0.1.16 - 2007-12-30
>>> >> [epson2] attach: devname = , type = 3
>>> >> [epson2] attach: opening , type = 3
>>> >> [epson2]  net autodiscovery
>>> >> [epson2] attach_one_net: dev = autodiscovery
>>> >> [epson2] SANE Epson 2 Backend v0.1.16 - 2007-12-30
>>> >> [epson2] attach: devname = autodiscovery, type = 4
>>> >> [epson2] attach: opening autodiscovery, type = 4
>>> >> [epson2] e2_network_discovery, sent discovery packet
>>> >> [epson2] e2_network_discovery, end
>>> >> [epson2] close_scanner: fd = -1
>>> >> [epson2] sane_epson2_get_devices
>
> Simple scanimage from server mashine and client PC works.

There is no error in that log section...

allan
--
"The truth is an offense, but not a sin"

--
sane-devel mailing list: sane-devel@...
http://lists.alioth.debian.org/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
             to sane-devel-request@...

Parent Message unknown Re: Unknown SANE status code -1081075667

by carterbueford :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hi at all,

I've got the following (see the attached logfile) error trying to scan with
my Epson Stylus Photo RX640 over XSane.

Simple scanimage from server mashine and client PC works.

Any ideas.

Regards
Oliver

-----Ursprüngliche Nachricht-----
Von: carterbueford@... [mailto:carterbueford@...]
Gesendet: Montag, 26. Oktober 2009 18:13
An: 'm. allan noah'; 'sane-devel@...'
Betreff: AW: [sane-devel] Unknown SANE status code -1081075667

Hi at all,

I've got the following error trying to scan with my Epson Stylus Photo RX640
over XSane.

>> >> [sanei_debug] Setting debug level of epson2 to 128.
>> >> [epson2] sane_epson2_init: sane-backends 1.0.19
>> >> [epson2] sane_epson2_init: reading config file, epson2.conf
>> >> [epson2]  scsi EPSON
>> >> [epson2]  usb
>> >> [epson2] attach_one_usb: dev =
>> >> [epson2] SANE Epson 2 Backend v0.1.16 - 2007-12-30
>> >> [epson2] attach: devname = , type = 3
>> >> [epson2] attach: opening , type = 3
>> >> [epson2]  net autodiscovery
>> >> [epson2] attach_one_net: dev = autodiscovery
>> >> [epson2] SANE Epson 2 Backend v0.1.16 - 2007-12-30
>> >> [epson2] attach: devname = autodiscovery, type = 4
>> >> [epson2] attach: opening autodiscovery, type = 4
>> >> [epson2] e2_network_discovery, sent discovery packet
>> >> [epson2] e2_network_discovery, end
>> >> [epson2] close_scanner: fd = -1
>> >> [epson2] sane_epson2_get_devices
Simple scanimage from server mashine and client PC works.

Any ideas.

Regards
Oliver
 

-----Ursprüngliche Nachricht-----
Von: m. allan noah [mailto:kitno455@...]
Gesendet: Montag, 26. Oktober 2009 13:27
An: Oliver Polch
Betreff: Re: [sane-devel] Unknown SANE status code -1081075667

xsane cannot speak over the network. it has some portion of sane
(perhaps just the net backend) installed inside it.

I am not sure what you can do to fix this- how about this: can you get
the scanner setup via USB in your linux VM? then share it with the
windows host via saned, and see if the same problem occurs. That will
tell us if the compile on the router is part of the problem...

allan

On Mon, Oct 26, 2009 at 6:31 AM, Oliver Polch <CarterBueford@...> wrote:

> Hi,
>
> on the client there is no sane, only XSane 0,996.
> On the server there is sane-backends, the latest git.
>
> Regards
> Oliver
>
> -------- Original-Nachricht --------
>> Datum: Sun, 25 Oct 2009 16:15:10 -0400
>> Von: "m. allan noah" <kitno455@...>
>> An: carterbueford@...
>> Betreff: Re: [sane-devel] Unknown SANE status code -1081075667
>
>> hmm- notice that there are no messages from epson2 prior to the
>> segfault. strange. what version of sane is in use on the client
>> machine?
>>
>> allan
>>
>> On Sun, Oct 25, 2009 at 10:18 AM,  <carterbueford@...> wrote:
>> > Hi Allan,
>> >
>> > see the attached logfile.
>> >
>> > Regards
>> > Oliver
>> >
>> >
>> > -----Ursprüngliche Nachricht-----
>> > Von: m. allan noah [mailto:kitno455@...]
>> > Gesendet: Sonntag, 25. Oktober 2009 12:43
>> > An: Oliver Polch
>> > Betreff: Re: [sane-devel] Unknown SANE status code -1081075667
>> >
>> > ahh, yes- this won't work on the client machine. we instead need to
>> > set it somehow in the xinetd config, and send the output into a file
>> > that the user can write to. I've never done that before, you'll have
>> > to figure it out.
>> >
>> > allan
>> >
>> > On Sun, Oct 25, 2009 at 5:25 AM, Oliver Polch <CarterBueford@...>
>> wrote:
>> >> Hi,
>> >>
>> >> here is the log:
>> >>
>> >> [sanei_debug] Setting debug level of epson2 to 128.
>> >> [epson2] sane_epson2_init: sane-backends 1.0.19
>> >> [epson2] sane_epson2_init: reading config file, epson2.conf
>> >> [epson2]  scsi EPSON
>> >> [epson2]  usb
>> >> [epson2] attach_one_usb: dev =
>> >> [epson2] SANE Epson 2 Backend v0.1.16 - 2007-12-30
>> >> [epson2] attach: devname = , type = 3
>> >> [epson2] attach: opening , type = 3
>> >> [epson2]  net autodiscovery
>> >> [epson2] attach_one_net: dev = autodiscovery
>> >> [epson2] SANE Epson 2 Backend v0.1.16 - 2007-12-30
>> >> [epson2] attach: devname = autodiscovery, type = 4
>> >> [epson2] attach: opening autodiscovery, type = 4
>> >> [epson2] e2_network_discovery, sent discovery packet
>> >> [epson2] e2_network_discovery, end
>> >> [epson2] close_scanner: fd = -1
>> >> [epson2] sane_epson2_get_devices
>> >>
>> >> Regards
>> >> Oliver
>> >>
>> >>
>> >> -------- Original-Nachricht --------
>> >>> Datum: Sat, 24 Oct 2009 16:05:37 -0400
>> >>> Von: "m. allan noah" <kitno455@...>
>> >>> An: Oliver Polch <CarterBueford@...>
>> >>> Betreff: Re: [sane-devel] Unknown SANE status code -1081075667
>> >>
>> >>> try with epson2 debug instead:
>> >>>
>> >>> SANE_DEBUG_EPSON2=128 xsane 2>ep2.log
>> >>>
>> >>> allan
>> >>>
>> >>> On Sat, Oct 24, 2009 at 3:52 PM, Oliver Polch <CarterBueford@...>
>> >>> wrote:
>> >>> > Hi,
>> >>> >
>> >>> > here is the logfile:
>> >>> >
>> >>> > [sanei_debug] Setting debug level of net to 10.
>> >>> > [net] sane_init: authorize = 0x413a70, version_code =
0x7fff8a519aa4

>> >>> > [net] sane_init: SANE net backend version 1.0.14 (AF-indep+IPv6)
>> from
>> >>> sane-backends 1.0.19
>> >>> > [net] sane_init: Client has little endian byte order
>> >>> > [net] sane_init: searching for config file
>> >>> > [net] net_avahi_browse_callback: CACHE_EXHAUSTED
>> >>> > [net] sane_init: trying to add 192.168.1.1
>> >>> > [net] add_device: adding backend 192.168.1.1
>> >>> > [net] add_device: backend 192.168.1.1 added
>> >>> > [net] sane_init: done reading config
>> >>> > [net] sane_init: evaluating environment variable SANE_NET_HOSTS
>> >>> > [net] sane_init: evaluating environment variable SANE_NET_TIMEOUT
>> >>> > [net] sane_init: done
>> >>> > [net] sane_get_devices: local_only = 0
>> >>> > [net] connect_dev: trying to connect to 192.168.1.1
>> >>> > [net] connect_dev: [0] connection succeeded (IPv4)
>> >>> > [net] connect_dev: sanei_w_init
>> >>> > [net] connect_dev: net_init (user=ram32, local version=1.0.3)
>> >>> > [net] connect_dev: freeing init reply (status=Success, remote
>> >>> version=1.0.3)
>> >>> > [net] connect_dev: done
>> >>> > [net] net_avahi_browse_callback: ALL_FOR_NOW
>> >>> > [net] sane_get_devices: got 192.168.1.1:epson2:libusb:002:004
>> >>> > [net] sane_get_devices: finished (1 devices)
>> >>> > [net] sane_open("192.168.1.1:epson2:libusb:002:004")
>> >>> > [net] sane_open: host = 192.168.1.1, device = epson2:libusb:002:004
>> >>> > [net] sane_open: device found in list
>> >>> > [net] sane_open: net_open
>> >>> > [net] sane_open: getting option descriptors
>> >>> > [net] fetch_options: 0x2782510
>> >>> > [net] fetch_options: get_option_descriptors
>> >>> > [net] fetch_options: creating 45 local option descriptors
>> >>> > [net] fetch_options: copying 45 option descriptors
>> >>> > [net] fetch_options: 45 options fetched
>> >>> > [net] sane_open: success
>> >>> > [net] sane_control_option: option 0, action 0
>> >>> > [net] sane_control_option: remote control option
>> >>> > [net] sane_control_option: remote done (Success, info 0)
>> >>> > [net] sane_control_option: done (Success, info 0)
>> >>> > [net] sane_get_option_descriptor: option 1
>> >>> > [net] sane_get_option_descriptor: option 2
>> >>> > [net] sane_get_option_descriptor: option 2
>> >>> > [net] sane_control_option: option 2, action 0
>> >>> > [net] sane_control_option: remote control option
>> >>> > [net] sane_control_option: remote done (Success, info 0)
>> >>> > [net] sane_control_option: done (Success, info 0)
>> >>> > [net] sane_get_option_descriptor: option 3
>> >>> > [net] sane_get_option_descriptor: option 4
>> >>> > [net] sane_get_option_descriptor: option 5
>> >>> > [net] sane_get_option_descriptor: option 5
>> >>> > [net] sane_control_option: option 5, action 0
>> >>> > [net] sane_control_option: remote control option
>> >>> > [net] sane_control_option: remote done (Success, info 0)
>> >>> > [net] sane_control_option: done (Success, info 0)
>> >>> > [net] sane_get_option_descriptor: option 6
>> >>> > [net] sane_get_option_descriptor: option 7
>> >>> > [net] sane_get_option_descriptor: option 8
>> >>> > [net] sane_get_option_descriptor: option 8
>> >>> > [net] sane_control_option: option 8, action 0
>> >>> > [net] sane_control_option: remote control option
>> >>> > [net] sane_control_option: remote done (Success, info 0)
>> >>> > [net] sane_control_option: done (Success, info 0)
>> >>> > [net] sane_get_option_descriptor: option 9
>> >>> > [net] sane_get_option_descriptor: option 10
>> >>> > [net] sane_get_option_descriptor: option 10
>> >>> > [net] sane_control_option: option 10, action 0
>> >>> > [net] sane_control_option: remote control option
>> >>> > [net] sane_control_option: remote done (Success, info 0)
>> >>> > [net] sane_control_option: done (Success, info 0)
>> >>> > [net] sane_get_option_descriptor: option 11
>> >>> > [net] sane_get_option_descriptor: option 12
>> >>> > [net] sane_get_option_descriptor: option 13
>> >>> > [net] sane_get_option_descriptor: option 14
>> >>> > [net] sane_get_option_descriptor: option 15
>> >>> > [net] sane_get_option_descriptor: option 15
>> >>> > [net] sane_control_option: option 15, action 0
>> >>> > [net] sane_control_option: remote control option
>> >>> > [net] sane_control_option: remote done (Success, info 0)
>> >>> > [net] sane_control_option: done (Success, info 0)
>> >>> > [net] sane_get_option_descriptor: option 16
>> >>> > [net] sane_get_option_descriptor: option 17
>> >>> > [net] sane_get_option_descriptor: option 18
>> >>> > [net] sane_get_option_descriptor: option 19
>> >>> > [net] sane_get_option_descriptor: option 19
>> >>> > [net] sane_control_option: option 19, action 0
>> >>> > [net] sane_control_option: remote control option
>> >>> > [net] sane_control_option: remote done (Success, info 0)
>> >>> > [net] sane_control_option: done (Success, info 0)
>> >>> > [net] sane_get_option_descriptor: option 20
>> >>> > [net] sane_get_option_descriptor: option 21
>> >>> > [net] sane_get_option_descriptor: option 22
>> >>> > [net] sane_get_option_descriptor: option 23
>> >>> > [net] sane_get_option_descriptor: option 24
>> >>> > [net] sane_get_option_descriptor: option 25
>> >>> > [net] sane_get_option_descriptor: option 26
>> >>> > [net] sane_get_option_descriptor: option 27
>> >>> > [net] sane_get_option_descriptor: option 28
>> >>> > [net] sane_get_option_descriptor: option 29
>> >>> > [net] sane_get_option_descriptor: option 30
>> >>> > [net] sane_get_option_descriptor: option 31
>> >>> > [net] sane_get_option_descriptor: option 32
>> >>> > [net] sane_get_option_descriptor: option 33
>> >>> > [net] sane_get_option_descriptor: option 33
>> >>> > [net] sane_control_option: option 33, action 0
>> >>> > [net] sane_control_option: remote control option
>> >>> > [net] sane_control_option: remote done (Success, info 0)
>> >>> > [net] sane_control_option: done (Success, info 0)
>> >>> > [net] sane_get_option_descriptor: option 34
>> >>> > [net] sane_get_option_descriptor: option 34
>> >>> > [net] sane_control_option: option 34, action 0
>> >>> > [net] sane_control_option: remote control option
>> >>> > [net] sane_control_option: remote done (Success, info 0)
>> >>> > [net] sane_control_option: done (Success, info 0)
>> >>> > [net] sane_get_option_descriptor: option 35
>> >>> > [net] sane_get_option_descriptor: option 35
>> >>> > [net] sane_control_option: option 35, action 0
>> >>> > [net] sane_control_option: remote control option
>> >>> > [net] sane_control_option: remote done (Success, info 0)
>> >>> > [net] sane_control_option: done (Success, info 0)
>> >>> > [net] sane_get_option_descriptor: option 36
>> >>> > [net] sane_get_option_descriptor: option 36
>> >>> > [net] sane_control_option: option 36, action 0
>> >>> > [net] sane_control_option: remote control option
>> >>> > [net] sane_control_option: remote done (Success, info 0)
>> >>> > [net] sane_control_option: done (Success, info 0)
>> >>> > [net] sane_get_option_descriptor: option 37
>> >>> > [net] sane_get_option_descriptor: option 38
>> >>> > [net] sane_get_option_descriptor: option 38
>> >>> > [net] sane_control_option: option 38, action 0
>> >>> > [net] sane_control_option: remote control option
>> >>> > [net] sane_control_option: remote done (Success, info 0)
>> >>> > [net] sane_control_option: done (Success, info 0)
>> >>> > [net] sane_get_option_descriptor: option 39
>> >>> > [net] sane_get_option_descriptor: option 40
>> >>> > [net] sane_get_option_descriptor: option 41
>> >>> > [net] sane_get_option_descriptor: option 42
>> >>> > [net] sane_get_option_descriptor: option 43
>> >>> > [net] sane_get_option_descriptor: option 44
>> >>> > [net] sane_get_option_descriptor: option 38
>> >>> > [net] sane_get_option_descriptor: option 38
>> >>> > [net] sane_control_option: option 38, action 0
>> >>> > [net] sane_control_option: remote control option
>> >>> > [net] sane_control_option: remote done (Success, info 0)
>> >>> > [net] sane_control_option: done (Success, info 0)
>> >>> > [net] sane_get_option_descriptor: option 2
>> >>> > [net] sane_get_option_descriptor: option 2
>> >>> > [net] sane_control_option: option 2, action 0
>> >>> > [net] sane_control_option: remote control option
>> >>> > [net] sane_control_option: auth required
>> >>> > [net]
>> >>> >
>> >>> >
>> >>> > Regards
>> >>> > Oliver
>> >>> >
>> >>> >
>> >>> > -------- Original-Nachricht --------
>> >>> >> Datum: Sat, 24 Oct 2009 08:44:23 -0400
>> >>> >> Von: "m. allan noah" <kitno455@...>
>> >>> >> An: carterbueford@...
>> >>> >> Betreff: Re: [sane-devel] Unknown SANE status code -1081075667
>> >>> >
>> >>> >> now get the xsane debug log i asked for on your ubuntu vm...
>> >>> >>
>> >>> >> allan
>> >>> >>
>> >>> >> On Sat, Oct 24, 2009 at 8:36 AM,  <carterbueford@...> wrote:
>> >>> >> > Hi,
>> >>> >> >
>> >>> >> > I have Ubuntu running in a VM, XSane still doesn't work,
>> scanimage
>> >>> does.
>> >>> >> > Might be a problem with XSane and epson2?
>> >>> >> >
>> >>> >> > Seems not to be a problem with the windows-version of XSane.
>> >>> >> >
>> >>> >> > I'm going to crosscompile a new version of sane-backends with
the

>> >>> flags
>> >>> >> and
>> >>> >> > take a look at the logs.
>> >>> >> >
>> >>> >> > Regards
>> >>> >> > Oliver
>> >>> >> >
>> >>> >> > -----Ursprüngliche Nachricht-----
>> >>> >> > Von: m. allan noah [mailto:kitno455@...]
>> >>> >> > Gesendet: Donnerstag, 22. Oktober 2009 14:46
>> >>> >> > An: carterbueford@...
>> >>> >> > Cc: sane-devel@...
>> >>> >> > Betreff: Re: [sane-devel] Unknown SANE status code -1081075667
>> >>> >> >
>> >>> >> > On Thu, Oct 22, 2009 at 1:17 AM,  <carterbueford@...> wrote:
>> >>> >> >> Hi,
>> >>> >> >>
>> >>> >> >> "easy, open a terminal window on the scanning client, and run
>> the
>> >>> >> >> command i gave you."
>> >>> >> >>
>> >>> >> >> Does not work. I am using Windows XP and after executing the
>> >>> command,
>> >>> >> the
>> >>> >> >> log is empty.
>> >>> >> >> Command I used:
>> >>> >> >> C:\sane\bin>xsane 2>net.log
>> >>> >> >
>> >>> >> > ahh- somewhere along the way you should have mentioned that
>> windows
>> >>> >> > was involved. You might try asking the author of xsane...
>> >>> >> >
>> >>> >> >> "SANE_DEBUG_NET=10" Where do I have to execute this command? It
>> > only
>> >>> >> works
>> >>> >> >> on my router.
>> >>> >> >
>> >>> >> > this sets an enviroment variable in unix, you put it on the same
>> >>> >> > command line right before you call the program, just like i
typed

>> it
>> >>> >> > before.
>> >>> >> >
>> >>> >> >> "what about scanimage on the client machine?"
>> >>> >> >> Works!
>> >>> >> >>
>> >>> >> >> "if you maintain the package, you should know how to modify the
>> .bb
>> >>> >> >> file to add arguments to the gcc call. Something like
>> CFLAGS="-Wall
>> >>> >> >> -Werror"
>> >>> >> >> Yes, no problem to set the flags, but I did not understand what
>> >>> effect
>> >>> >> it
>> >>> >> >> will have. Is this option for debugging or to solve the problem
>> >>> after
>> >>> >> >> compiling?
>> >>> >> >
>> >>> >> > the -W options to gcc make it give more warnings at compile
time.
>> > you
>> >>> >> > will have to find the bitbake logfile to see the noise.
>> >>> >> >
>> >>> >> > but frankly, I am now thinking the windows compile of xsane
might

>> be
>> >>> >> > part of the problem. The easiest way to know would be for you to
>> >>> >> > install a real OS on your machine (i.e. Linux, perhaps in a VM),
>> and
>> >>> >> > make sure that you can scan over the network.
>> >>> >> >
>> >>> >> > allan
>> >>> >> >
>> >>> >> >>
>> >>> >> >> Regards
>> >>> >> >> Oliver
>> >>> >> >>
>> >>> >> >>
>> >>> >> >>
>> >>> >> >>
>> >>> >> >> -----Ursprüngliche Nachricht-----
>> >>> >> >> Von: m. allan noah [mailto:kitno455@...]
>> >>> >> >> Gesendet: Dienstag, 20. Oktober 2009 14:41
>> >>> >> >> An: carterbueford@...
>> >>> >> >> Cc: Olaf Meeuwissen; sane-devel@...
>> >>> >> >> Betreff: Re: [sane-devel] Unknown SANE status code -1081075667
>> >>> >> >>
>> >>> >> >> On Tue, Oct 20, 2009 at 2:49 AM,  <carterbueford@...>
>> wrote:
>> >>> >> >>> Hi,
>> >>> >> >>>
>> >>> >> >>> @allan: I do not run xsane on the same mashine like the
>> >>> sane-server,
>> >>> >> so I
>> >>> >> >> do not understand how to write the log you want me to.
>> >>> >> >>> "xsane... 2>net.log"
>> >>> >> >>
>> >>> >> >> easy, open a terminal window on the scanning client, and run
the
>> >>> >> >> command i gave you.
>> >>> >> >>
>> >>> >> >>> sanimage on the mashine where the sane-server runs, works
fine.

>> >>> >> >>
>> >>> >> >> what about scanimage on the client machine?
>> >>> >> >>
>> >>> >> >> Tthere are three likely sources for this error:
>> >>> >> >>
>> >>> >> >> 1. xsane makes different API calls than scanimage, and triggers
>> a
>> >>> bug
>> >>> >> in
>> >>> >> >> epson2
>> >>> >> >> 2. net backend munges the data
>> >>> >> >> 3. saned munges the data
>> >>> >> >>
>> >>> >> >>> @Olaf:"Compile the backend with gcc -Wall -Werror should give
a
>> >>> >> cluebat."
>> >>> >> >> What is meant by that?
>> >>> >> >>> I'm using the optware package, so it is not compiled on my
>> router.
>> >>> I
>> >>> >> am
>> >>> >> >> maintainer of the package, so I can patch it to be compiled in
a

>> >>> >> different
>> >>> >> >> way, but how?
>> >>> >> >>
>> >>> >> >> if you maintain the package, you should know how to modify the
>> .bb
>> >>> >> >> file to add arguments to the gcc call. Something like
>> CFLAGS="-Wall
>> >>> >> >> -Werror"
>> >>> >> >>
>> >>> >> >> bitbake puts its compilation output someplace funny, you'll
have

>> to
>> >>> >> >> look for the log...
>> >>> >> >>
>> >>> >> >> allan
>> >>> >> >> --
>> >>> >> >> "The truth is an offense, but not a sin"
>> >>> >> >>
>> >>> >> >>
>> >>> >> >
>> >>> >> >
>> >>> >> >
>> >>> >> > --
>> >>> >> > "The truth is an offense, but not a sin"
>> >>> >> >
>> >>> >> >
>> >>> >>
>> >>> >>
>> >>> >>
>> >>> >> --
>> >>> >> "The truth is an offense, but not a sin"
>> >>> >
>> >>> > --
>> >>> > Jetzt kostenlos herunterladen: Internet Explorer 8 und Mozilla
>> Firefox
>> >>> 3.5 -
>> >>> > sicherer, schneller und einfacher!
>> > http://portal.gmx.net/de/go/chbrowser
>> >>> >
>> >>>
>> >>>
>> >>>
>> >>> --
>> >>> "The truth is an offense, but not a sin"
>> >>
>> >> --
>> >> Neu: GMX DSL bis 50.000 kBit/s und 200,- Euro Startguthaben!
>> >> http://portal.gmx.net/de/go/dsl02
>> >>
>> >
>> >
>> >
>> > --
>> > "The truth is an offense, but not a sin"
>> >
>>
>>
>>
>> --
>> "The truth is an offense, but not a sin"
>
> --
> Jetzt kostenlos herunterladen: Internet Explorer 8 und Mozilla Firefox 3.5
-
> sicherer, schneller und einfacher! http://portal.gmx.net/de/go/atbrowser
>



--
"The truth is an offense, but not a sin"

[saned] main: starting debug mode (level 128)
[saned] read_config: searching for config file
[saned] read_config: done reading config
[saned] saned (AF-indep+IPv6) from sane-backends 1.0.20 starting up
[saned] do_bindings: trying to get port for service "sane-port" (getaddrinfo)
[saned] do_bindings: " sane-port " service unknown on your host; you should add
[saned] do_bindings:      sane-port 6566/tcp saned # SANE network scanner daemon
[saned] do_bindings: to your /etc/services file (or equivalent). Proceeding anyway.
[saned] do_bindings: [0] socket () using IPv6
[saned] do_bindings: [0] socket failed: Address family not supported by protocol
[saned] do_bindings: [1] socket () using IPv4
[saned] do_bindings: [1] setsockopt ()
[saned] do_bindings: [1] bind () to port 6566
[saned] do_bindings: [1] listen ()
[saned] run_standalone: waiting for control connection
[saned] handle_connection: processing client connection
[saned] check_host: access by remote host: 192.168.1.2
[saned] check_host: remote host is not IN_LOOPBACK nor IN6_LOOPBACK
[saned] check_host: local hostname: WL-001FC642402C
[saned] check_host: local hostname(s) (from DNS): c0a8:101:1062:ff7f::
[saned] check_host: local hostname(s) (from DNS): c0a8:101:1062:ff7f::
[saned] check_host: local hostname(s) (from DNS): c0a8:101:1062:ff7f::
[saned] check_host: local hostname(s) (from DNS): WL-001FC642402C
[saned] check_host: local hostname(s) (from DNS): WL-001FC642402C
[saned] check_host: local hostname(s) (from DNS): WL-001FC642402C
[saned] check_host: remote host doesn't have same addr as local
[saned] check_host: opening config file: /etc/hosts.equiv
[saned] check_host: can't open config file: /etc/hosts.equiv (No such file or directory)
[saned] check_host: opening config file: saned.conf
[saned] check_host: config file line: `# saned.conf'
[saned] check_host: config file line: `# Configuration for the saned daemon'
[saned] check_host: config file line: `'
[saned] check_host: config file line: `## Daemon options'
[saned] check_host: config file line: `# Port range for the data connection. Choose a range inside [1024 - 65535].'
[saned] check_host: config file line: `# Avoid specifying too large a range, for performance reasons.'
[saned] check_host: config file line: `#'
[saned] check_host: config file line: `# ONLY use this if your saned server is sitting behind a firewall. If your'
[saned] check_host: config file line: `# firewall is a Linux machine, we strongly recommend using the'
[saned] check_host: config file line: `# Netfilter nf_conntrack_sane connection tracking module instead.'
[saned] check_host: config file line: `#'
[saned] check_host: config file line: `# data_portrange = 10000 - 10100'
[saned] check_host: config file line: `'
[saned] check_host: config file line: `'
[saned] check_host: config file line: `## Access list'
[saned] check_host: config file line: `# A list of host names, IP addresses or IP subnets (CIDR notation) that'
[saned] check_host: config file line: `# are permitted to use local SANE devices. IPv6 addresses must be enclosed'
[saned] check_host: config file line: `# in brackets, and should always be specified in their compressed form.'
[saned] check_host: config file line: `#'
[saned] check_host: config file line: `# The hostname matching is not case-sensitive.'
[saned] check_host: config file line: `'
[saned] check_host: config file line: `#scan-client.somedomain.firm'
[saned] check_host: config file line: `#192.168.0.1'
[saned] check_host: config file line: `#192.168.0.1/29'
[saned] check_host: config file line: `#[2001:7a8:185e::42:12]'
[saned] check_host: config file line: `#[2001:7a8:185e::42:12]/64'
[saned] check_host: config file line: `'
[saned] check_host: config file line: `# NOTE: /etc/inetd.conf (or /etc/xinetd.conf) and'
[saned] check_host: config file line: `# /etc/services must also be properly configured to start'
[saned] check_host: config file line: `# the saned daemon as documented in saned(8), services(4)'
[saned] check_host: config file line: `# and inetd.conf(4) (or xinetd.conf(5)).'
[saned] check_host: config file line: `'
[saned] check_host: config file line: `192.168.1.0/24 #grant access to scanner from network 192.168.1.x'
[saned] check_host: subnet with base IP = 192.168.1.0, CIDR netmask = 24 #grant access to scanner from network 192.168.1.x
[saned] check_host: access granted from IP address 192.168.1.2 (in subnet 192.168.1.0/24 #grant access to scanner from network 192.168.1.x)
[saned] init: access granted
[saned] init: access granted to ram32@...
[saned] process_request: waiting for request
[saned] process_request: got request 1
[sanei_debug] Setting debug level of epson2 to 128.
[epson2] sane_epson2_init: sane-backends 1.0.20
[epson2] sane_epson2_init: reading config file, epson2.conf
[epson2]  scsi EPSON
[epson2]  usb
[epson2] attach_one_usb: dev =
[epson2] epson2 backend, version 1.0.117
[epson2] attach: devname = , type = 3
[epson2] attach: opening , type = 3
[epson2]  usb 0x04b8 0x081c
[epson2] attach_one_usb: dev = libusb:002:004
[epson2] epson2 backend, version 1.0.117
[epson2] attach: devname = libusb:002:004, type = 3
[epson2] attach: opening libusb:002:004, type = 3
[epson2] found valid EPSON scanner: 0x4b8/0x81c (vendorID/productID)
[epson2] e2_set_model: model is 'generic'
[epson2] esci_reset
[epson2] e2_cmd_simple: size = 2
[epson2] e2_send: size = 2, reply = 1
[epson2] e2_send: ESC @
[epson2] buf[0] 1b .
[epson2] buf[1] 40 @
[epson2] e2_send: cmd count, r = 0, w = 1
[epson2] e2_recv: size = 1, buf = 0x7fff3110
[epson2] e2_recv: cmd count, r = 1, w = 1
[epson2] buf[0] 06 .
[epson2] e2_discover_capabilities
[epson2] esci_request_identity
[epson2] e2_cmd_info_block, params len = 2, reply len = 0, buf = 0x7fff3184
[epson2] e2_send: size = 2, reply = 0
[epson2] e2_send: ESC I
[epson2] buf[0] 1b .
[epson2] buf[1] 49 I
[epson2] e2_send: cmd count, r = 1, w = 2
[epson2] e2_recv: size = 4, buf = 0x7fff30a4
[epson2] e2_recv: cmd count, r = 2, w = 2
[epson2] buf[0] 02 .
[epson2] buf[1] 12 .
[epson2] buf[2] 13 .
[epson2] buf[3] 00 .
[epson2] e2_recv_info_block: payload length: 19
[epson2] e2_recv: size = 19, buf = 0x4229b0
[epson2] e2_recv: cmd count, r = 3, w = 2
[epson2] buf[0] 44 D
[epson2] buf[1] 38 8
[epson2] buf[2] 52 R
[epson2] buf[3] 64 d
[epson2] buf[4] 00 .
[epson2] buf[5] 52 R
[epson2] buf[6] 90 .
[epson2] buf[7] 01 .
[epson2] buf[8] 52 R
[epson2] buf[9] 40 @
[epson2] buf[10] 06 .
[epson2] buf[11] 52 R
[epson2] buf[12] 80 .
[epson2] buf[13] 0c .
[epson2] buf[14] 41 A
[epson2] buf[15] 40 @
[epson2] buf[16] 6a j
[epson2] buf[17] 40 @
[epson2] buf[18] 92 .
[epson2] e2_set_cmd_level: D8
[epson2] e2_add_resolution: add (dpi): 100
[epson2] e2_add_resolution: add (dpi): 400
[epson2] e2_add_resolution: add (dpi): 1600
[epson2] e2_add_resolution: add (dpi): 3200
[epson2] maximum scan area: 27200x37440
[epson2] e2_set_fbf_area: 0.000000,0.000000 215.899994,297.179993 3200 [mm]
[epson2] esci_request_status
[epson2] e2_send: size = 2, reply = 4
[epson2] e2_send: ESC F
[epson2] buf[0] 1b .
[epson2] buf[1] 46 F
[epson2] e2_send: cmd count, r = 3, w = 3
[epson2] e2_recv: size = 4, buf = 0x7fff30f4
[epson2] e2_recv: cmd count, r = 4, w = 3
[epson2] buf[0] 02 .
[epson2] buf[1] 12 .
[epson2] buf[2] 00 .
[epson2] buf[3] 00 .
[epson2] status: 12
[epson2]  ready
[epson2]  option equipment is installed
[epson2]  support extended commands
[epson2] esci_request_identity2
[epson2] e2_cmd_info_block, params len = 2, reply len = 0, buf = 0x7fff3184
[epson2] e2_send: size = 2, reply = 0
[epson2] e2_send: ESC i
[epson2] buf[0] 1b .
[epson2] buf[1] 69 i
[epson2] e2_send: cmd count, r = 4, w = 4
[epson2] e2_recv: size = 4, buf = 0x7fff30a4
[epson2] e2_recv: cmd count, r = 5, w = 4
[epson2] buf[0] 02 .
[epson2] buf[1] 12 .
[epson2] buf[2] 3c <
[epson2] buf[3] 00 .
[epson2] e2_recv_info_block: payload length: 60
[epson2] e2_recv: size = 60, buf = 0x422c60
[epson2] e2_recv: cmd count, r = 6, w = 4
[epson2] buf[0] 80 .
[epson2] buf[1] 0c .
[epson2] buf[2] d5 .
[epson2] buf[3] 00 .
[epson2] buf[4] 00 .
[epson2] buf[5] 00 .
[epson2] buf[6] 00 .
[epson2] buf[7] 00 .
[epson2] buf[8] 00 .
[epson2] buf[9] 00 .
[epson2] buf[10] 00 .
[epson2] buf[11] 00 .
[epson2] buf[12] 00 .
[epson2] buf[13] 00 .
[epson2] buf[14] 64 d
[epson2] buf[15] 00 .
[epson2] buf[16] c8 .
[epson2] buf[17] 00 .
[epson2] buf[18] 2c ,
[epson2] buf[19] 01 .
[epson2] buf[20] 90 .
[epson2] buf[21] 01 .
[epson2] buf[22] 58 X
[epson2] buf[23] 02 .
[epson2] buf[24] 20  
[epson2] buf[25] 03 .
[epson2] buf[26] b0 .
[epson2] buf[27] 04 .
[epson2] buf[28] 40 @
[epson2] buf[29] 06 .
[epson2] buf[30] 80 .
[epson2] buf[31] 0c .
[epson2] buf[32] 00 .
[epson2] buf[33] 00 .
[epson2] buf[34] 64 d
[epson2] buf[35] 00 .
[epson2] buf[36] c8 .
[epson2] buf[37] 00 .
[epson2] buf[38] 2c ,
[epson2] buf[39] 01 .
[epson2] buf[40] 90 .
[epson2] buf[41] 01 .
[epson2] buf[42] 58 X
[epson2] buf[43] 02 .
[epson2] buf[44] 20  
[epson2] buf[45] 03 .
[epson2] buf[46] b0 .
[epson2] buf[47] 04 .
[epson2] buf[48] 40 @
[epson2] buf[49] 06 .
[epson2] buf[50] 60 `
[epson2] buf[51] 09 .
[epson2] buf[52] 80 .
[epson2] buf[53] 0c .
[epson2] buf[54] c0 .
[epson2] buf[55] 12 .
[epson2] buf[56] 00 .
[epson2] buf[57] 19 .
[epson2] buf[58] 00 .
[epson2] buf[59] 00 .
[epson2] discovering max depth, NAKs are expected
[epson2] e2_esc_cmd: cmd = 0x44, val = 16
[epson2] e2_cmd_simple: size = 2
[epson2] e2_send: size = 2, reply = 1
[epson2] e2_send: ESC D
[epson2] buf[0] 1b .
[epson2] buf[1] 44 D
[epson2] e2_send: cmd count, r = 6, w = 5
[epson2] e2_recv: size = 1, buf = 0x7fff30f8
[epson2] e2_recv: cmd count, r = 7, w = 5
[epson2] buf[0] 06 .
[epson2] e2_cmd_simple: size = 1
[epson2] e2_send: size = 1, reply = 1
[epson2] buf[0] 10 .
[epson2] e2_send: cmd count, r = 7, w = 6
[epson2] e2_recv: size = 1, buf = 0x7fff30f8
[epson2] e2_recv: cmd count, r = 8, w = 6
[epson2] buf[0] 06 .
[epson2] e2_esc_cmd: cmd = 0x44, val = 14
[epson2] e2_cmd_simple: size = 2
[epson2] e2_send: size = 2, reply = 1
[epson2] e2_send: ESC D
[epson2] buf[0] 1b .
[epson2] buf[1] 44 D
[epson2] e2_send: cmd count, r = 8, w = 7
[epson2] e2_recv: size = 1, buf = 0x7fff30f8
[epson2] e2_recv: cmd count, r = 9, w = 7
[epson2] buf[0] 06 .
[epson2] e2_cmd_simple: size = 1
[epson2] e2_send: size = 1, reply = 1
[epson2] buf[0] 0e .
[epson2] e2_send: cmd count, r = 9, w = 8
[epson2] e2_recv: size = 1, buf = 0x7fff30f8
[epson2] e2_recv: cmd count, r = 10, w = 8
[epson2] buf[0] 15 .
[epson2] e2_cmd_simple: NAK
[epson2] e2_esc_cmd: cmd = 0x44, val = 12
[epson2] e2_cmd_simple: size = 2
[epson2] e2_send: size = 2, reply = 1
[epson2] e2_send: ESC D
[epson2] buf[0] 1b .
[epson2] buf[1] 44 D
[epson2] e2_send: cmd count, r = 10, w = 9
[epson2] e2_recv: size = 1, buf = 0x7fff30f8
[epson2] e2_recv: cmd count, r = 11, w = 9
[epson2] buf[0] 06 .
[epson2] e2_cmd_simple: size = 1
[epson2] e2_send: size = 1, reply = 1
[epson2] buf[0] 0c .
[epson2] e2_send: cmd count, r = 11, w = 10
[epson2] e2_recv: size = 1, buf = 0x7fff30f8
[epson2] e2_recv: cmd count, r = 12, w = 10
[epson2] buf[0] 15 .
[epson2] e2_cmd_simple: NAK
[epson2] maximum supported color depth: 16
[epson2] esci_request_focus_position
[epson2] setting focus is not supported
[epson2] esci_request_scanner_status
[epson2] e2_send: size = 2, reply = 16
[epson2] e2_send: FS F
[epson2] buf[0] 1c .
[epson2] buf[1] 46 F
[epson2] e2_send: cmd count, r = 12, w = 11
[epson2] e2_recv: size = 16, buf = 0x7fff318d
[epson2] e2_recv: cmd count, r = 13, w = 11
[epson2] buf[0] 01 .
[epson2] buf[1] 00 .
[epson2] buf[2] 80 .
[epson2] buf[3] c0 .
[epson2] buf[4] 00 .
[epson2] buf[5] 00 .
[epson2] buf[6] 00 .
[epson2] buf[7] 00 .
[epson2] buf[8] 00 .
[epson2] buf[9] 00 .
[epson2] buf[10] 00 .
[epson2] buf[11] 00 .
[epson2] buf[12] 00 .
[epson2] buf[13] 00 .
[epson2] buf[14] 00 .
[epson2] buf[15] 00 .
[epson2] global status   : 0x01
[epson2] adf status      : 0x00
[epson2]  not installed
[epson2]  not enabled
[epson2] tpu status      : 0x80
[epson2]  installed
[epson2]  not enabled
[epson2] device type     : 0xc0
[epson2] main body status: 0x00
[epson2] esci_reset
[epson2] e2_cmd_simple: size = 2
[epson2] e2_send: size = 2, reply = 1
[epson2] e2_send: ESC @
[epson2] buf[0] 1b .
[epson2] buf[1] 40 @
[epson2] e2_send: cmd count, r = 13, w = 12
[epson2] e2_recv: size = 1, buf = 0x7fff3110
[epson2] e2_recv: cmd count, r = 14, w = 12
[epson2] buf[0] 06 .
[epson2] scanner model: generic
[epson2] close_scanner: fd = 0
[epson2]  net autodiscovery
[epson2] attach_one_net: dev = autodiscovery
[epson2] epson2 backend, version 1.0.117
[epson2] attach: devname = autodiscovery, type = 4
[epson2] attach: opening autodiscovery, type = 4
[epson2] e2_network_discovery, sent discovery packet
[epson2] e2_network_discovery, end
[epson2] close_scanner: fd = -1
[epson2] sane_epson2_get_devices
[epson2]  0: generic
[saned] process_request: waiting for request
[saned] process_request: got request 2
[saned] process_request: access to resource `epson2' granted
[epson2] sane_epson2_open: name = libusb:002:004
[epson2] init_options
[epson2] open_scanner
[epson2] esci_reset
[epson2] e2_cmd_simple: size = 2
[epson2] e2_send: size = 2, reply = 1
[epson2] e2_send: ESC @
[epson2] buf[0] 1b .
[epson2] buf[1] 40 @
[epson2] e2_send: cmd count, r = 14, w = 13
[epson2] e2_recv: size = 1, buf = 0x7fff4288
[epson2] e2_recv: cmd count, r = 15, w = 13
[epson2] buf[0] 06 .
[saned] process_request: sane_open returned: Success
[saned] process_request: waiting for request
[saned] process_request: got request 4
[saned] process_request: waiting for request
[saned] process_request: got request 5
[saned] process_request: waiting for request
[saned] process_request: got request 5
[saned] process_request: waiting for request
[saned] process_request: got request 5
[saned] process_request: waiting for request
[saned] process_request: got request 5
[saned] process_request: waiting for request
[saned] process_request: got request 5
[saned] process_request: waiting for request
[saned] process_request: got request 5
[saned] process_request: waiting for request
[saned] process_request: got request 5
[saned] process_request: waiting for request
[saned] process_request: got request 5
[saned] process_request: waiting for request
[saned] process_request: got request 5
[saned] process_request: waiting for request
[saned] process_request: got request 5
[saned] process_request: waiting for request
[saned] process_request: got request 5
[saned] process_request: waiting for request
[saned] process_request: got request 5
Segmentation fault

--
sane-devel mailing list: sane-devel@...
http://lists.alioth.debian.org/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
             to sane-devel-request@...