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 permissions. > > > udevtest: run: 'socket:/org/freedesktop/hal/udev_event' > > And what happens with that? I wouldn't be surprised if HAL or > something else was changing the permissions at that point.
Thanks for the replies. Strangely enough I can no longer reproduce it. The device now gets created reliably with the correct group (with the rules file renamed back to its old name and even after a reboot). The only thing I can think of is that something has some kind of memory, possibly hal. Here's roughly what I did: - plugged in the scanner - noticed I did not yet have kooka or libsane installed - installed the packages - add myself to scanner group; log out and log in again - try kooka which fails (understandable as udev rules missing when scanner was plugged in, so wrong group) - unplugged the scanner and plugged it in again (remember that this creates a new device node with a name and minor one higher than the last) - things still not working - loads of different attempts to find out what's wrong; unplug scanner a number of times - finally notice that group is wrong on device node - chgrp to fix it => kooka works - try the rename of the rules file - unplug scanner and plug it back in again => now I get correct group If either of you has any ideas, please let me know. If not, I guess this one can be closed. Cheers, FJP -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
