| View previous topic :: View next topic |
| Author |
Message |
doitux
n00b
Joined: 19 Sep 2006
Posts: 8
|
 Posted: Tue Oct 10, 2006 12:01 am Post subject: wrong permission on camera-device |
 |
|
Hi
Since a few weeks, may be after an update i cannot longer access my usb-camera "ixus 400" as normal user. the user is in "plugdev" group, and "gphoto2 --get-all-files" works as root, but not as normal user.
So i checked permisson on usb-device after plug in:
| Code: | hammer Desktop # lsusb
Bus 002 Device 017: ID 04a9:3075 Canon, Inc. IXUS 400 Camera
hammer Desktop # ls -l /proc/bus/usb/002/017
-rw-rw---- 1 root plugdev 57 10. Okt 01:51 /proc/bus/usb/002/017
hammer Desktop # ls -l /dev/bus/usb/002/017
crw-r--r-- 1 root root 189, 144 10. Okt 01:51 /dev/bus/usb/002/017 |
The /proc permission are ok. But in /dev there are wrong permissions. What can i do here? |
|
| Back to top |
|
 |
shazam75
Guru
Joined: 18 Mar 2006
Posts: 563
Location: Brisbane, Australia
|
| Posted: Tue Oct 10, 2006 9:25 am Post subject: |
|
|
| can u change the permissions on the /dev/ directory using chmod ? |
|
| Back to top |
|
|
doitux
n00b
Joined: 19 Sep 2006
Posts: 8
|
| Posted: Tue Oct 10, 2006 12:30 pm Post subject: |
|
|
Yes this works:
| Code: | hammer doitux # lsusb
Bus 002 Device 019: ID 04a9:3075 Canon, Inc. IXUS 400 Camera
hammer doitux # ls -l /dev/bus/usb/002/019
crw-r--r-- 1 root root 189, 146 10. Okt 14:25 /dev/bus/usb/002/019
hammer doitux # chmod ugo+rwx /dev/bus/usb/002/019
hammer doitux # ls -l /dev/bus/usb/002/019
crwxrwxrwx 1 root root 189, 146 10. Okt 14:25 /dev/bus/usb/002/019
|
But i think permissions should be set correctly by hotplug/udev.  |
|
| Back to top |
|
|
didl
Retired Dev
Joined: 09 Sep 2003
Posts: 1106
Location: Pittsburgh, PA
|
| Posted: Tue Oct 10, 2006 12:44 pm Post subject: |
|
|
Just write a simple udev rule for your camera and you will be in
business. |
|
| Back to top |
|
|
doitux
n00b
Joined: 19 Sep 2006
Posts: 8
|
| Posted: Tue Oct 10, 2006 5:18 pm Post subject: |
|
|
| Yes i can do. But i try to find the reason of the problem. i think an update have destroyed an working rule, because it works as i expected before last update. |
|
| Back to top |
|
|
|
Kernel & Hardware
