Comment 3 for bug 121082

I'm trying hardy heron beta1 and I have this same problem.
(NB, commands below ran after changing permissions, so xsane is not running as root)

when I run lsusb, I can see the device is 004:004:
Bus 004 Device 006: ID 07cc:0501 Carry Computer Eng., Co., Ltd
>>>> Bus 004 Device 004: ID 04b8:011b Seiko Epson Corp. Perfection 2400 Photo
Bus 004 Device 002: ID 03f0:c602 Hewlett-Packard
Bus 004 Device 001: ID 0000:0000
Bus 003 Device 002: ID 046d:c03e Logitech, Inc. Premium Optical Wheel Mouse
Bus 003 Device 001: ID 0000:0000
Bus 002 Device 003: ID 045e:001d Microsoft Corp. Natural Keyboard Pro
Bus 002 Device 002: ID 045e:001c Microsoft Corp.
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 001: ID 0000:0000

"lsof |grep xsane |grep dev" also gives that xsane is using this device at /dev/bus/usb/004/004:
xsane 10068 simon 6r CHR 1,9 1804 /dev/urandom
xsane 10068 simon 8u CHR 189,387 5753 /dev/bus/usb/004/004

So when I changed
chgrp scanner /dev/bus/usb/004/004
and made sure my username (simon) is in the scanner group, I could run xsane as a normal user.

The bug is that my default user wasn't in the scanner group _and_ the device for the scanner wasn't in the scanner group.

I don't know what mechanism is used to set this...

Cheers

Simon