notfound 523355 1.0.19-23
tag 523355 - patch
close 523355
thanks
Frans Pop elen...@planet.nl wrote:
Hi,
I tried purging and reinstalling libsane a few times. No luck reproducing
the problem.
I'm closing the bug, then. Hopefully it won't reoccur, and if it does
maybe it can be tracked down
On Friday 10 April 2009, Julien BLACHE wrote:
libsane also installs an HAL FDI file; I'm not sure whether HAL
monitors the relevant directories for new files like udev does for its
rules. That'd be worth checking out.
That's not it. hal gets restarted during installation of libsane:
Unpacking
On Thursday 09 April 2009, Julien BLACHE wrote:
udev_device_event: device '/class/usb_device/usbdev5.12' already in
database, cleanup udev_node_add: creating device node
'/dev/bus/usb/005/012', major=189, minor=523, mode=0664, uid=0,
gid=115
The node gets created, presumably with proper
Frans Pop elen...@planet.nl wrote:
Hi,
If either of you has any ideas, please let me know. If not, I guess this
one can be closed.
libsane also installs an HAL FDI file; I'm not sure whether HAL
monitors the relevant directories for new files like udev does for its
rules. That'd be worth
Package: libsane
Version: 1.0.19-23
Severity: important
Tags: patch
I've decided to file a new BR even though I suspect that this will resolve
quite a few open bugs both against libsane and scanning frontends.
My HP Scanjet 3300C worked perfectly before, but when I connected it to
my notebook
On Apr 09, Frans Pop elen...@planet.nl wrote:
Please Cc me.
udev_node_add: creating device node '/dev/bus/usb/005/011',
major=189, minor=523, mode=0664, uid=0, gid=115
So clearly udev is confused.
Is it? here it says gid=115.
So, my theory was that the device gets created with
Maybe the rules file should even get a lower number than 60 as that is
used for the standard udev rules. I see that hplip is at 45 for example.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
On Thursday 09 April 2009, Frans Pop wrote:
Maybe the rules file should even get a lower number than 60 as that is
used for the standard udev rules. I see that hplip is at 45 for
example.
The same goes for z60_libsane-extras.rules obviously.
--
To UNSUBSCRIBE, email to
On Thursday 09 April 2009, Marco d'Itri wrote:
On Apr 09, Frans Pop elen...@planet.nl wrote:
udev_node_add: creating device node '/dev/bus/usb/005/011',
major=189, minor=523, mode=0664, uid=0, gid=115
So clearly udev is confused.
Is it? here it says gid=115.
So, my theory was
Frans Pop elen...@planet.nl wrote:
Hi,
So clearly udev is confused.
confused is not the word I'd use, actually. Though it does start
with a 'c', too.
After all that, the solution!
I noticed that the libsane udev rules are completely at the end:
[...]
80-drivers.rules
85-pcmcia.rules
Frans Pop elen...@planet.nl wrote:
Hi,
match_rule: set ENV 'libsane_matched=yes'
The rule did match, obviously.
udev_device_event: device '/class/usb_device/usbdev5.12' already in database,
cleanup
udev_node_add: creating device node '/dev/bus/usb/005/012', major=189,
minor=523,
On Apr 09, Julien BLACHE jbla...@debian.org wrote:
udev_device_event: device '/class/usb_device/usbdev5.12' already in
database, cleanup
udev_node_add: creating device node '/dev/bus/usb/005/012', major=189,
minor=523, mode=0664, uid=0, gid=115
The node gets created, presumably with
12 matches
Mail list logo
