I'm using 6.10, with no backports enabled that I know of.
Like, it appears, several other people, gthumb pops something up, but the.n complains about not being able to access the device. Running "sudo gphoto" works swimmingly well.
I too tried the 'SUBSYSTEM!="usb_device", GOTO="libgphoto2_rules_end"' hack, but that didn't help.
I am in the "plugdev" group; however, the device is created as owned by root, as shown by ls -l in /proc/bus/usb/003
After I "chgrp plugdev 004", it reads:
...
crw-rw-r-- 1 root plugdev 189, 259 2007-05-13 19:46 004
and I can run gphoto from the menu and it works fine.
The workaround of running sudo gphoto / photo-app-of-choice is slightly painful, but not a showstopper. It would be nice to know why it's being created as the wrong group, though. (That seems to be the issue, and not users accidentally being left out of the "plugdev" group.)
I'm using 6.10, with no backports enabled that I know of.
Like, it appears, several other people, gthumb pops something up, but the.n complains about not being able to access the device. Running "sudo gphoto" works swimmingly well.
I too tried the 'SUBSYSTEM! ="usb_device" , GOTO="libgphoto 2_rules_ end"' hack, but that didn't help.
I am in the "plugdev" group; however, the device is created as owned by root, as shown by ls -l in /proc/bus/usb/003
total 0
crw-rw-r-- 1 root root 189, 256 2007-05-12 18:48 001
crw-rw-r-- 1 root root 189, 259 2007-05-13 19:43 004
After I "chgrp plugdev 004", it reads:
...
crw-rw-r-- 1 root plugdev 189, 259 2007-05-13 19:46 004
and I can run gphoto from the menu and it works fine.
The workaround of running sudo gphoto / photo-app-of-choice is slightly painful, but not a showstopper. It would be nice to know why it's being created as the wrong group, though. (That seems to be the issue, and not users accidentally being left out of the "plugdev" group.)