Re: pkg/50340: USB scanners stopped working with xsane

[Martin Husemann <martin%duskware.de@localhost>]

The following reply was made to PR pkg/50340; it has been noted by GNATS.

From: Martin Husemann <martin%duskware.de@localhost>
To: gnats-bugs%NetBSD.org@localhost
Cc: 
Subject: Re: pkg/50340: USB scanners stopped working with xsane
Date: Sat, 17 Oct 2015 23:06:24 +0200

 So the issue started with the update to sane-backends.
 
 In their README.netbsd there is this passage:
 
 > If you want to use libusb, disable the uscanner driver.
 > 
 > Problems with uscanner driver:
 > 
 > The uscanner driver also works (tested with the plustek backend). As the
 > uscanner driver can't detect the vendor and product ids automatically, it's
 > necessary to add the name of the device file to the backends's configuration
 > file. Some backends also need the vendor and product id of the scanner.
 
 I have no idea how to enable or disable the usage of libusb, my backend
 configuration had the right magic to make /dev/uscanner0 work.
 
 However, if I remove the kernel uscanner driver, I can use my scanner
 via libusb.
 
 This has a very serious drawback though: I have /dev/uscanner0 chown'd to
 the console user. I really would like to avoid that for /dev/ugen0.00.
 And of course I won't run xsane as root either.
 
 I would very much prefer to get the old state back working, unless anyone
 has a good idea how to make some arbitrary ugen* device chowned to the
 console user when the scanner is pluged in (or similar).
 
 Martin