Ettore Pasquini ([EMAIL PROTECTED]) wrote:
> On 3/2/08 8:46 AM, "Sven Neumann" <[EMAIL PROTECTED]> wrote:
> > On Wed, 2008-02-27 at 19:16 -0800, Ettore Pasquini wrote:
> > 
> >> It turned out to be a couple wrong assumptions on my side.  First the linux
> >> device file /dev/input/eventN was for some reason not readable by anyone 
> >> but
> >> root.
> > 
> > I usually fix this by adding a udev rule that changes the device
> > permissions for all usb input devices to allow the group "plugdev" to
> > access the device.
> Yep, that's pretty much what I did.  I added a post to our forum:

For helix I have prepared the following udev rule:

KERNEL=="event[0-9]*", ATTRS{name}=="3Dconnexion Space*", 
SYMLINK+="input/3d-nav", MODE="0666"

This matches the USB device name against "3Dconnexion Space*", which
should cover all 6DOF devices from 3Dconnexion. It also symlinks that
device to a fixed position so that programs can make assumptions about
the device name without probing the linux input layer.

Maybe this is useful for you.

              [EMAIL PROTECTED]    
Gimp-developer mailing list

Reply via email to