Permissions difficulties with USB camera

krazykit · Tux's lil' helper Joined: 28 Aug 2004 Posts: 91

I'm trying to use my Canon Powershot a400 (a PTP device, NOT usb-mass storage) with digikam. I had it working out the other day, and now it doesn't (computer pixies, I bet :wink:

). The reason I think it's a permissions problem is that my camera will work when I run digikam as root, but not as user.
doing cat /proc/bus/usb/devices gives me (irrelevant stuff snipped)

krazykit · Tux's lil' helper Joined: 28 Aug 2004 Posts: 91

I suppose I could just always run the program in root, but that's really a cruddy solution.

krazykit · Tux's lil' helper Joined: 28 Aug 2004 Posts: 91

Well, perhaps it's time for a bump... it really is a shoddy solution to have to chmod after transferring pictures...

fredgt · Posted: Mon Apr 11, 2005 12:07 am Post subject:

I've got the same camera and i had that problems to. It's a hotplug problems, it doesn't set the correct device file properties.
You can edit the hotplug script ( /etc/hotplug/usb/usbcam ) so the device file property of the you're normal user (for me 'arne'). I also added a few lines, because it still didn't work but now it does.
It's probably not completely by the book but you can give it a try. Don't forget to backup the script before you edit it, and don't forget to change the username.

rizzo · Posted: Mon May 02, 2005 2:18 pm Post subject:

I think I'm having the same problem. I don't have either /var/run/console.lock or /var/lock/console.lock on my box. Has anyone filed a bug on this?

Kern3lP4nic · Posted: Mon May 02, 2005 5:04 pm Post subject:

those files are created by pam

pesche · Posted: Wed May 18, 2005 2:08 pm Post subject:

Hi there

Try to find the file usbcam.group on your disk. If you have digicam / gphoto2 and the right libs installed, the file should be located in

iniTeX · n00b Joined: 23 Jul 2003 Posts: 15 Location: Germany

hi there,

i had problems with my ixus400 yesterday.

i figured out that "usbcam" wants to set the owner according to /var/run/console.lock.

unless you don't have the use-flag "pam_console" set and pam compiled with it you don't have something like /var/{lock,run}/console.lock.

so i compiled pam with pam_console. then i saw that there was not /var/run/console.lock but /var/run/console/console.lock.
i fixed usbcam with another elif-loop and i could download pictures from my camera again.

i don't now if this (use-variable and hacking a usbcam) was the right way to do it so i don't want to send in a bug report.

perhaps someone can enlighten me.

greets, iniTeX
_________________
dashi delegs

pesche · Posted: Thu Jun 02, 2005 11:50 am Post subject:

Hi Initex

As i have already written in my previous post, there's no need for any console.lock file or any other hacks. You just have to use the proper hotplug script (e.g. the one indicated in my post which works with groups...)

Greetings,
Pesche.
_________________
"The significant problems we have cannot be solved at the same level of thinking with which we created them."

Albert Einstein (1879 - 1955)

digitalboi · n00b Joined: 03 May 2005 Posts: 15

I have a similiar problem. I have got the camera to detect after I modified the permissions of usbcam.group like pesche said. However I have a wierd problem going on. Let me give the scenario.

User A logs into kde. Then User B logs into KDE. User A activates his session and view the pictures on the camera through digikam. Then User A leaves and User B activates her session to view the pictures however it says the camera is not hooked up, but User A has no problem viewing the pictures. As soon as User A logs completely out then User B can view the pictures on the camera. Also if user B logs in only, they have no problem viewing. I can't figure out what the problem is.

BTW when user B activates their session. User A does close out digikam completely and the process is no longer running when user B tries to view pictures on the camera.

Don't know if this has to anything to do with it, but when I try to view the camera thru konqueror using media://HP_M305 it gives an error saying it doesnt exist. This happens with both users but not with root. If someone can point me to the right file I would be grateful. If anyone needs any configs posted let me know and I'll be glad to do it. In the mean time I have to log out of my session everytime so the second person who logged in can view and import pictures off the camera. Please help. Thanks in advance.

yfh2 · Apprentice Joined: 20 May 2004 Posts: 242

ok, now, what if I don't use hotplug ?

I found that the camera is created under /proc/bus/usb/003/xyz where xyz is incremented each time the camera is plugged.

It is initialised with root only permissions.

Can I change this in any way ???

Pol · Tux's lil' helper Joined: 01 May 2003 Posts: 113

seppelrockt · Guru Joined: 14 May 2004 Posts: 423

The usbcam script solution works fine here - I even had the file at the right place allready - all I had to change was the group. No PAM and no hotplug needed.

pkturner · Posted: Sat Sep 17, 2005 11:48 am Post subject: bug

There's a more thorough discussion of this problem in bug 84628.

Tarch · n00b Joined: 27 Apr 2005 Posts: 42

Hi all, i've tried with the usbcam script solution but I have a problem, I add the group camera and I add my user to the group camera, I substitute the script, but gphoto says me that I don't have the permissions to access the device. I think it's related to the user and group from which I executing the program but I don't know how to resolve it (a temporary workaround is to set the permission rw to other but I don't like it).

Bye and thank you!

P.S. Happy New Year.

pkturner · Posted: Sat Dec 31, 2005 6:54 pm Post subject: bugfix

When I looked at this topic 3 months ago I didn't like any of the suggested solutions, since they didn't appear to be headed toward a permanent fix.

Happily, there's now a fix in libgphoto2-2.1.6-r1. The ebuild is still listed as unstable, so if you want that fix right away you'll need to add it to /etc/package.keywords.