Bug 162592 - Communication error with digital camera
Summary: Communication error with digital camera
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Import-Gphoto2 (show other bugs)
Version: 0.9.3
Platform: FreeBSD Ports FreeBSD
: NOR normal
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-05-25 13:29 UTC by Norbert Koch
Modified: 2017-08-16 06:12 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In: 5.1.0
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Norbert Koch 2008-05-25 13:29:49 UTC
Version:           0.9.3 (using KDE 3.5.8)
Installed from:    FreeBSD Ports
Compiler:          gcc 4.2.1 
OS:                FreeBSD

I see this with a Canon EOS-350D and a Canon EOS-400D:

Both cameras are correctly auto-detected in PTP-mode.
The images on the camera are correctly displayed in
digikam's preview.
I can retrieve all pictures from those cameras with gphoto2
(command line) without any problems.
Only when I use digikam, the transfer stops randomly
and digikam reports, that there is a communication error.
When this happens I see that there is effectively no
communication as the camera's light does not flash.
I usually can solve this by only mark a single picture,
retrieve this and so on. I tried the other Canon camera
protocol and saw the same problem.
It makes no difference if I manually start digikam or
let it be started through hal.

This is the output of "gphoto2 -v":

gphoto2         2.4.1          cc, popt(m), exif, no cdk, aa, jpeg, readline
libgphoto2      2.4.1          cc, no ltdl, EXIF
libgphoto2_port 0.8.0          cc, no ltdl, USB, serial without locking

These additional ports are installed:
kipi-plugins-0.1.5_1,1 KDE Image Plugin Interface plugins
libkipi-0.1.6       KDE Image Plugin Interface

The funny thing is that I remember not having had problems
with older kde and digikam but cannot reproduce what versions
were ok.
It does not have to do with some settings as I completely
rebuilt kde and digikam when upgrading from FreeBSD 6.3
to FreeBSD 7.0. I also deleted all digikam-related settings.
Comment 1 caulier.gilles 2009-05-13 11:48:11 UTC
Can you use digiKam 0.10.0 for KDE4 and check if problem still here ?

Gilles Caulier
Comment 2 caulier.gilles 2015-07-02 05:07:22 UTC
New digiKam 4.11.0 is available.

https://www.digikam.org/node/740

Can you reproduce the problem with this release ?

Gilles Caulier
Comment 3 caulier.gilles 2016-07-15 16:24:30 UTC
With digiKam 5.0.0, this problem is not reproducible.
I close this file now. Don't hesitate to re-open if necessary.
Gilles Caulier