Bug#359797: libsane: udev rules file broken

2007-04-22 Thread Julien BLACHE
Brad Sawatzky [EMAIL PROTECTED] wrote: Hi, Can you unplug your scanner, run udevmonitor (as root), plug it in and send me the output ? Alright. Now I'm confused... The scanner now works correctly with the original rule: SUBSYSTEM!=usb_device, GOTO=libsane_rules_end and not with the

Bug#359797: libsane: udev rules file broken

2007-04-22 Thread Brad Sawatzky
On Sun, 22 Apr 2007, Julien BLACHE wrote: Brad Sawatzky [EMAIL PROTECTED] wrote: [ ... ] Is it possible for the autoprobed scanner device to be indeterminate? The I'm not sure what you mean here, could you elaborate ? See below. CX6600 is a multifunction printer/scanner unit with

Bug#359797: libsane: udev rules file broken

2007-04-22 Thread Julien BLACHE
Brad Sawatzky [EMAIL PROTECTED] wrote: Hi, There's only one node created under /dev/bus/usb unfortunately, that's a real problem with multifunction devices and the current permissions scheme - it's hard to share the printer between CUPS and SANE. This is what was in the back of my mind.

Bug#359797: libsane: udev rules file broken

2007-04-21 Thread Julien BLACHE
Brad Sawatzky [EMAIL PROTECTED] wrote: Hi, Changing the line to SUBSYSTEM!=usb_endpoint, GOTO=libsane_rules_end allows the rule to match and fixes the problem for me. I assume that this is a change in how kernel 2.6.20.7 reports this device? I've attached a udevinfo dump for the curious.

Bug#359797: libsane: udev rules file broken

2007-04-21 Thread Brad Sawatzky
On Sat, 21 Apr 2007, Julien BLACHE wrote: Brad Sawatzky [EMAIL PROTECTED] wrote: Changing the line to SUBSYSTEM!=usb_endpoint, GOTO=libsane_rules_end allows the rule to match and fixes the problem for me. I assume that this is a change in how kernel 2.6.20.7 reports this device?

Bug#359797: libsane: udev rules file broken

2007-04-15 Thread Brad Sawatzky
Package: libsane Version: 1.0.18-6 Followup-For: Bug #359797 The patch suggested by Henrique causes libsane.rules to fail to match my scanner (an Epson CX6600). The problem is that udev sees a subsystem class of usb_endpoint not usb_device so the following line causes the bulk of libsane.rules

Bug#359797: libsane: udev rules file broken

2006-04-12 Thread Julien BLACHE
Henrique de Moraes Holschuh [EMAIL PROTECTED] wrote: Hi, You need to write it like this: ACTION!=add, GOTO=libsane_rules_end SUBSYSTEM!=usb_device, GOTO=libsane_rules_end Fixed upstream. Thanks, JB. -- Julien BLACHE - Debian GNU/Linux Developer - [EMAIL PROTECTED] Public key

Bug#359797: libsane: udev rules file broken

2006-03-29 Thread Julien BLACHE
Henrique de Moraes Holschuh [EMAIL PROTECTED] wrote: The first line of the udev rules file is incorrect: SUBSYSTEM!=usb_device, ACTION!=add, GOTO=libsane_rules_end You need to write it like this: ACTION!=add, GOTO=libsane_rules_end SUBSYSTEM!=usb_device, GOTO=libsane_rules_end As matches

Bug#359797: libsane: udev rules file broken

2006-03-29 Thread Henrique de Moraes Holschuh
On Wed, 29 Mar 2006, Julien BLACHE wrote: Henrique de Moraes Holschuh [EMAIL PROTECTED] wrote: The first line of the udev rules file is incorrect: SUBSYSTEM!=usb_device, ACTION!=add, GOTO=libsane_rules_end You need to write it like this: ACTION!=add, GOTO=libsane_rules_end

Bug#359797: libsane: udev rules file broken

2006-03-29 Thread Julien BLACHE
Henrique de Moraes Holschuh [EMAIL PROTECTED] wrote: And still, it works. As in it matches a lot many more times than it should, wasting resources. Ah, ok, so it's not b0rken, it's just sub-optimal. Fix queued, thanks. JB. -- Julien BLACHE - Debian GNU/Linux Developer - [EMAIL

Bug#359797: libsane: udev rules file broken

2006-03-28 Thread Henrique de Moraes Holschuh
Package: libsane Version: 1.0.17-1 Severity: normal The first line of the udev rules file is incorrect: SUBSYSTEM!=usb_device, ACTION!=add, GOTO=libsane_rules_end You need to write it like this: ACTION!=add, GOTO=libsane_rules_end SUBSYSTEM!=usb_device, GOTO=libsane_rules_end As matches are