FS#10341 - [gphoto2] Usb-camera permissions problem related to udev

Attached to Project: Arch Linux
Opened by Ivan N. Veselov (dying_sphynx) - Friday, 02 May 2008, 20:32 GMT
Last edited by Greg (dolby) - Saturday, 26 July 2008, 07:20 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Jason Chu (jason)
Architecture i686
Severity Medium
Priority Normal
Reported Version 2007.08-2
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 3
Private No

Details

Description:

I'd like to be able to work with my Canon EOS 350D camera.
I've installed gphoto2, added my user to 'camera' group, found my vendor-id and product-id in 54-gphoto.rules.
gphoto2 works good for root, but returns the following error for regular user (added to camera group):

sphynx@behexen:~$ gphoto2 --summary

*** Error ***
An error occurred in the io-library ('Bad parameters'): Could not find USB device (vendor 0x4a9, product 0x30ef). Make sure this device is connected to the computer.
*** Error (-2: 'Bad parameters') ***

Also I've noticed I can see my camera only with 'sudo lsusb', not with 'lsusb'.

The problem can be solved by running /etc/start_udev and seems to be similar to one mentioned here:
http://bugs.archlinux.org/task/9935

Additional info:
* package version(s)
gphoto2 2.4.0-1
udev 119-1
2.6.24.4 kernel

Steps to reproduce:
1. install gphoto2
2. attach Canon EOS 350D to usb :)
2. run 'gphoto2 --auto-detect'
This task depends upon

Closed by  Greg (dolby)
Saturday, 26 July 2008, 07:20 GMT
Reason for closing:  Fixed
Comment by Jick Nan (jicknan) - Wednesday, 07 May 2008, 09:18 GMT
I encounter the problem too, and play with it for a while.

Then I find out that to solve this problem, it's just need to run:

/etc/start_udev uevents

and this call '/sbin/udevtrigger' and '/sbin/udevsettle'.

But the up two commands are not called in the /etc/rc.sysinit where processing the udev-related things.
Comment by Greg (dolby) - Monday, 14 July 2008, 20:07 GMT
Please update to libgphoto2 2.4.2-1 and report back
Comment by Eduardo Romero (kensai) - Friday, 25 July 2008, 02:24 GMT
OK, this has been sitting here for some time. If the problem is similar to http://bugs.archlinux.org/task/9935, and that one got fixed, I believe this one is fixed as well.

Loading...