[sane-devel] [epson2] leaking file descriptors

Olaf Meeuwissen olaf.meeuwissen at avasys.jp
Thu Aug 29 07:42:13 UTC 2013

Hi all,

I've been chasing a bug where the epson2 backend prevented another
backend from recognizing that backend's supported network scanners.
Turns out that the epson2 backend holds on to file descriptors (and
associated network connections) even if it decides that the device is
one that the epson2 backend doesn't support after all.

Upon closer inspection, not only network connections were affected but
*any* connection that used a file descriptor.  Attached is a patch.

This issue has been around since 1.0.19 and at one point AVASYS even
recommended disabling the epson2 backend if you were using the epkowa
backend with its non-free network support...
A slightly less intrusive workaround would be to disabled the epson2
backend's autodiscovery in epson2.conf.

If someone could commit this for me so it goes into 1.0.24, I would
appreciate it a lot.

Hope this helps,
Olaf Meeuwissen, LPIC-2           FLOSS Engineer -- AVASYS CORPORATION
FSF Associate Member #1962               Help support software freedom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-Close-file-descriptor-leak.patch
Type: text/x-diff
Size: 1405 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20130829/ced8ce7e/attachment-0001.patch>

More information about the sane-devel mailing list