And if you'd like to fix it, there is a set of hal fdi files which put scanners into the scanner group for ACL control:
/usr/share/hal/fdi/preprobe/10osvendor/20-libsane.fdi /usr/share/hal/fdi/preprobe/10osvendor/20-libsane-extras.fdi Sometimes the fdi files can miss a supported scanner (like my Epson v500) But hopefully with the additions sent upstream, the next person with your scanner shouldn't suffer the same fate. Be sure you know which driver supports your scanner though, it's important to get it in the right package. (libsane, libsane-extras, iscan-plugins etc etc) Although no idea how this effects DeviceKit, I presume it's going to need some kind of similar list of devices supported. Regards, Martin Owens On Sun, 2009-05-03 at 16:16 +0300, kohe...@gmail.com wrote: > Hello, > In the Brother support page: > http://solutions.brother.com/linux/en_us/instruction_scn1c.html#u9 > They recommend changing the mode for USB devices to 666, which is a > security issue. > I created a usbdev group and added my user to that group, added a > group setting to that line instead of the recommended mode change, > and my scanner works, I think that this group should be added to the > default installation, and the rule modified accordingly. > What do you think? > > Please reply to all, so I'll get the message, I'm not a list member. > David Kohen -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
