enrico <[EMAIL PROTECTED]> wrote: Hi,
> To run saned in debug mode, I had to remove it from inetd. Indeed, sorry for not telling about this. > So from a command line, I ran saned -d128 on the server > > and it works fine this way, ie. no more bug ... > > here is the output on the client (xsane.out), and on the > server (saned.out) OK, can you send me xsane.out when it fails ? I may have an idea of what's going on, but I need this output to verify that. If the bug still occurs, please test with scanimage instead of xsane, too. > At least, I can scan now, great ! Yep, but it looks like there's a bug to fix nonetheless :) The fact that this code (net and saned) has not been touched in a little less than 3 years really bothers me (and even more so that I know this code very well and rewrote part of it); it's considered stable by now. Either this bug is an heisenbug, or it's specific to your machine ... JB. -- Julien BLACHE - Debian & GNU/Linux Developer - <[EMAIL PROTECTED]> Public key available on <http://www.jblache.org> - KeyID: F5D6 5169 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
