Hi, On Tue, Jun 08, 2004 at 08:31:51AM -0700, Keith Clayton wrote: > On Tue, 2004-06-08 at 10:52 +0200, Henning Meier-Geinitz wrote: > > Hi, > > > > On Sun, Jun 06, 2004 at 10:27:57AM -0700, Keith Clayton wrote: > > > No seg fault on the saned end. Its happily running, waiting to finish > > > up. Xsane itself remains responsive. > > > > Ok. So you sent the logfile when both xsane and saned were still > > running? In this case the log file looks ok. Can you please retry and > > after the scan, close xsane? saned should also closes itsself. Thanks. > > I would expect xsane to close the fd used to access the scanner though.
sane_close() will be called when xsane is closed. Some backends close the device file (or use the equivalent call to libusb) after the scan has finished but not all. > Anyway, generated a log with a scan followed by closing xsane. saned > exited as expected. As you'll see in the log, saned quits however, I > never see any entry regarding the closing of the active fd. Please try again with SANE_DEBUG_PLUSTEK=255. saned doesn't print messages about closing but from your log I expect that the devices are actually closed. The plustek messages should show that. In that case we must have a closer look at the communication. > thanks for all your work . . looks like you've been busy as of late 8^( Fortunately I've two weeks of holidays and a lot of that time is used for SANE :-) Bye, Henning