You are not logged in.
This is a strange problem... I have within use two desktop machines and a laptop.
The laptop is a fresh install of Arch .8 and works wonderful with Digikam and my Canon SD800IS camera.
The two desktops are older 7.2 installs and are constantly kept up to date with pacman. They both auto detect the camera, however, unlike when I have the camera connected to my laptop, they fail on trying to connect to the camera. I'm clueless as to why. All machines with my user name belong to the camera group, and like I said, are up to date with udev, and use the latest kernel26beyond kernel. I'd hate to do a fresh install of .8 on either machines as they are both how I like them.
Does anyone have any idea what this could possibly be? I'm totally stumped, and had not luck with the bug reports, forums, or even google
Thanks in advance for any help if you can,
--
JSkier
Offline
Seems to be a permission problem. The posts on this forum point out that I need to be in the camera group, which my user is. It works fine in root. Any ideas on how to fix the permissions? I found some on the forums for digikam but they aren't very clear and haven't helped.
--
JSkier
Offline
Just a guess: try adding your user to the storage group.
Offline
Just a guess: try adding your user to the storage group.
Already was
As well as audio, scanner~ typically everything except root. I know I can't be the only one with this problem as it is duplicable on another machine.
--
JSkier
Offline
Make sure that the user on the laptop and desktops are in the same groups.
Maybe you have an old udev rule lying around that messes things up. Compare the group ownership/permissions of the device created when you plug in the camera.
Offline
Make sure that the user on the laptop and desktops are in the same groups.
Maybe you have an old udev rule lying around that messes things up. Compare the group ownership/permissions of the device created when you plug in the camera.
Users are identical. I tried adding everything except root and still it doesn't work. I even reinstalled on one desktop and the problem is still there. It's not setting permissions right. I'm not sure where to go with this at this point.
--
JSkier
Offline