[Digikam-users] DigiKam fails to connect with my camera - dmesg

[rivenought]

Message: 3
Date: Thu, 29 Nov 2007 00:12:38 +0100 (CET)
From: Arnd Baecker <arnd.baecker at web.de>
Subject: Re: [Digikam-users] DigiKam fails to connect with my camera
To: digiKam - Digital Photo Management for the masses
    <digikam-users at kde.org>
Message-ID:
    <Pine.LNX.4.51.0711290010400.19433 at ptpcp8.phy.tu-dresden.de>
Content-Type: TEXT/PLAIN; charset=US-ASCII

Hi

On Wed, 28 Nov 2007, rivenought wrote:


> > OK, a few weeks ago was the last time I used DigiKam. I have a Kodak
> > EasyShare C533 which is detected and listed in the DigiKam program. I
> > know the camera works because it has worked numerous times previously. I
> > also plugged it into a Windows XP machine today, and it worked fine.
> >
> > Now, the camera is detected, and the USB Imaging Device icon pops up on
> > the desktop as usual. The error message I then get is: "Failed to
> > connect to the camera. Please make sure it is connected properly and
> > turned on. Would you like to try again?" Something is just not right here...
> >
> > I have the current version of DigiKam and pretty much everything else on
> > here is updated to the current versions, too.  I have libgphoto2,
> > libgphoto2-devel, digikam, digikamimageplugins,
> > digicamimageplugins-superimpose - all of these are updated against the
> > openSUSE 10.3 x86_64 repositories.
> >
> >  Do you guys think it is possible that an update over the past few weeks
> > may have broken something somewhere? If so, what are my options to get
> > this issue fixed really easily? Anyone else have this same issue or have
> > any suggestions?
> >
> > My system: openSUSE 10.3 (64-bit) / KDE 3.5.8 running on an MSI K9VGM-V
> > (integrated VIA Chrome9 K8M890 graphics) with an AMD AM2 Sempron64 3000+
> > CPU and 2 GB of Kingston KVR667D2N5 RAM.
> >
> > This is not an absolute emergency, but I sure would like DigiKam to work
> > like it did before.  I would appreciate any help you guys can give.
>   

There have been a couple of issues with Suse 10.3, see
http://bugs.kde.org/show_bug.cgi?id=152417
http://bugs.kde.org/show_bug.cgi?id=152382
which might be related.
Could you try the steps given in bug 152382 under comment #2
and report the ouput here?

Best, Arnd

New Message Begins:

Thanks, Arnd.  This is what I have done thus far:

------- Additional Comment #2 From Arnd Baecker 2007-11-15 20:45 -------
This is most likely a problem with the setup for gphoto2 which is used
to communicate with the camera.

Could you try the following commands and report their output:
a) connect camera, what is the output of dmesg
(only the camera related part)
b) gphoto2 --list ports
c) gphoto2 --auto-detect -L
d) gphoto2 --abilities
e) gphoto2 --list-folders

I was able to get this dmesg from Konsole:

URGP=0 OPT (0101080A00C24AF1045329CC)
usb 4-2: new full speed USB device using uhci_hcd and address 5
usb 4-2: new device found, idVendor=040a, idProduct=05a2
usb 4-2: new device strings: Mfr=1, Product=2, SerialNumber=3
usb 4-2: Product: KODAK EasyShare C533 Zoom Digital Camera
usb 4-2: Manufacturer: Eastman Kodak Company
usb 4-2: SerialNumber: KCFFR64822253
usb 4-2: configuration #1 chosen from 1 choice
usb 4-2: usbfs: USBDEVFS_CONTROL failed cmd kio_kamera rqt 33 rq 102 len
0 ret -71
usb 4-2: usbfs: USBDEVFS_CONTROL failed cmd kio_kamera rqt 33 rq 102 len
0 ret -71
usb 4-2: usbfs: USBDEVFS_CONTROL failed cmd kio_kamera rqt 33 rq 102 len
0 ret -71
usb 4-2: usbfs: USBDEVFS_CONTROL failed cmd digikam rqt 33 rq 102 len 0
ret -71
usb 4-2: usbfs: USBDEVFS_CONTROL failed cmd digikam rqt 33 rq 102 len 0
ret -71
usb 4-2: usbfs: USBDEVFS_CONTROL failed cmd digikam rqt 33 rq 102 len 0
ret -71

As for the other commands, I got "bash: gphoto2: command not found." I
am scratching my head now.  I have those packages installed.  Am I not
running the commands correctly or something?

Anyone able to point the finger at gphoto2 or a permissions issue? I am
open for suggestion. It seems that I am not the only one with this
problem. Sure, we can wait for the openSUSE team to issue a fix, but
there must be some kind of workaround in the meantime.