On Friday 15 November 2002 05:17 am, you wrote: > Hi, > > On Thu, Nov 14, 2002 at 08:13:58PM -0500, Ryan wrote: > > I had xsane/sane working. I think the last time I used it was before= I > > updated to RH8 from 7.3. > > Which version of SANE are you using now (server + client)?
I'm running xsane .89. And this is my output from 'rpm -qa |grep sane' sane-backends-1.0.8-5 sane-frontends-1.0.8-4 sane-backends-devel-1.0.8-5 xsane-0.89-1 It is the same on both PCs. > > I still works on my PC, but I can't get it to work on my second one u= sing > > sane's network capability. > > So on your first PC, the scanner is listed by scanimage -L, even as > normal user? So the permissions are set-up correctly. Yes, when I run scanimage -L as a normal user I get: device `epson:/dev/usb/scanner0' is a Epson Perfection610 flatbed scanner > > But this was all working last time I tried it. > > At first when I fired up xsane on the second PC all I got was somethi= ng > > like 'no devices found'. After I set /usr/sbin/saned to SUID root > > Don't do that. saned wasn't written to support that. It's too risky. > Instead, make sure that the user saned has access to your USB device > (probably /dev/usb/scanner0). I don't have a user named saned. So I should create one, then make that = user=20 own the saned executeable, then make sure xinetd is going to run saned as= =20 that user? > First, make sure that the local net works: On PC 1, add localhost to > net.conf. scanimage -L should list your scanner twice now, once > directly and once over the net (e.g. > net:localhost:epson:/dev/usb/scanner0). If this doesn't work, check > your xinetd settings again. This works. I get: device `epson:/dev/usb/scanner0' is a Epson Perfection610 flatbed scanner device `net:localhost:epson:/dev/usb/scanner0' is a Epson Perfection610=20 flatbed scanner > > I was able to > > get past that. But now every time I hit preview or scan on the seco= nd > > PC I get this error: "Failed to start scanner: Invalid argument". > > > > If I run scanimage I get: "scanimage: sane_start: Invalid argument". > > Any messages in syslog of PC 1? Maybe you can see more details when > running with debugging enabled: > > SANE_DEBUG_NET=3D255 scanimage -d ... >out.pnm This works fine. I end up with a scanned image. > For debugging purposes, you can also use saned stand-alone (without > xinetd). See man saned. If you mean 'saned -d', I get this when I run that: [saned] main: starting debug mode (level 2) [saned] main: bind failed: Address already in use And when I run 'saned' it just sits there waiting for me to do something=20 somehow until I hit Ctrl+C. Thanks for your help. -Ryan
