Digikam and My Digital Cam
Jeffrey F. Bloss
jbloss at tampabay.rr.com
Fri Mar 16 17:12:34 UTC 2007
Amichai Rotman wrote:
> Hi All,
>
> My Ubuntu Edgy box was running slow, so I re-formated and re
> installed from scratch.
>
> Before the re-formating I used my Canon A520 (A.K.A. IXUS 50
> (connected to USB) with Digikam - no problem.
>
> Since the fresh installation I get two problems:
>
> When I connect the camera I hear a beep from the computer's internal
> speaker and Digikam claims the camera isn't connected.
A quick 'apt-cache showpkg' says Digikam depends on libgphoto2, so this
*may* be your problem:
Connect the camera as you would to import pictures from it... turned
on, in "preview" mode, etc.
Open a terminal and invoke...
lsusb
You should see a line that looks something like this...
Bus 002 Device 002: ID 04a9:30ba Canon, Inc. [....]
The important part is the '04a9:30ba'. The vendor:product code of your
camera as your libgphoto2 sees them. Yours will be different.
Now check to see if your camera is one that libgphoto2 is aware of. In
the same terminal type...
grep -n 04a9 /etc/udev/riles.d/45-libgphoto2.rules | grep 30ba
You'll have to replace the '04a9' and '30ba' with your vendor and
product codes of course, but you should see one or more lines that look
something like this...
33:SYSFS{idVendor}=="04a9", SYSFS{idProduct}=="30ba", MODE= [....]
The '33:' is the line number, and of course the '04a9' and '30ba' will
be your own vendor/product codes.
Whether or not you get any results from the grep command above, you'll
want to...
sudo gedit /etc/udev/rules.d/45-libgphoto2.rules
If a line or lines for your camera does *not* exist (grep returns
nothing), you have to add one. Use one of the existing lines as a
template, copy it, and change the idVendor and idProduct codes
accordingly. Save the file, exit gedit, and reboot or restart udev like
this...
sudo /etc/init.d/udev restart
Try the camera again. If it works, JOY!
If that doesn't work, or if entries for your camera vendor and model
already exist, (re)open the libgphoto2.rules file...
sudo gedit /etc/udev/rules.d/45-libgphoto2.rules
If the top of that file looks like this:
# udev rules file for libgphoto2 devices (udev < 0.98)
#
BUS!="usb*", GOTO="libgphoto2_rules_end"
ACTION!="add", GOTO="libgphoto2_rules_end"
Change it to this:
# udev rules file for libgphoto2 devices (udev < 0.98)
#
#BUS!="usb*", GOTO="libgphoto2_rules_end"
SUBSYSTEM!="usb_device", GOTO="libgphoto2_rules_end"
ACTION!="add", GOTO="libgphoto2_rules_end"
Again, save the file, exit gedit, and reboot or restart udev with the
'sudo /etc/init.d/udev restart' invocation. Reboot if you're paranoid
about changes taking effect. ;-)
In short, this is a bug whereby the test BUS!="usb*" will always be
true, and as a result all the following camera "definitions" are
ignored.
> What's wrong? Do I have to install something that isn't installed?
Actually, the problem boils down to permissions if this *is* your
problem. You'll notice the MODE= part of all the libgphoto2.rules
entries. That sets permissions to access the camera. If the rules aren't
read they default to something like 600 I'd imagine. It's a pretty sure
bet that if you log in as root and try to access the camera it will work
even before the above changes. Or start digikam from a terminal as root
with 'sudo digikam' or whatever the executable name for digikam is. It
should "just work" if you're root.
Either one of the two above problems will effectively make your camera
"unknown" to libgphoto2, result in a device that you're not allowed to
access as a lowly user, and they both seem to have both popped up
recently as a side effect of a libgphoto2 update. My s410 quit working
on me this week out of the blue... no reinstall needed. ;-)
--
_?_ Outside of a dog, a book is a man's best friend.
(o o) Inside of a dog, it's too dark to read.
-oOO-(_)--OOo------------------------------[ Groucho Marx ]---
http://wrench.homelinux.net/~jeff/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 892 bytes
Desc: not available
URL: <https://lists.ubuntu.com/archives/ubuntu-users/attachments/20070316/f4203237/attachment.sig>
More information about the ubuntu-users
mailing list