Bug 116904

Summary:	Connection to camera lost after download + delete of pictures
Product:	[Applications] digikam	Reporter:	Dieter Jurzitza <dieter.jurzitza>
Component:	Import-Gphoto2	Assignee:	Digikam Developers <digikam-bugs-null>
Status:	RESOLVED FIXED
Severity:	normal	CC:	caulier.gilles, kde
Priority:	NOR
Version:	0.8.0
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed In:	5.1.0
Sentry Crash Report:

Description Dieter Jurzitza 2005-11-22 21:17:35 UTC

Version:           0.8 (using KDE KDE 3.4.0)
Installed from:    SuSE RPMs
Compiler:          gcc (GCC) 3.3.5 20050117 (prerelease) (SUSE Linux) 
OS:                Linux

Camera: CASIO Exilim EZ 40 (PTP)
Select a set of pictures on the camera. Download them into some folder within digicam. Delete those files from the camera after download. Try to download the next picture -> impossible, camera is said to be inaccessible.
When closing the camera window and reopening it, one can download and delete one set once again. However, the next set is not accessible any more.
Seems to me as if the camera does not realize that the pictures on the camera have changed and those pictures that used to be at a certain position in the picture list do not exist any more.
If I can help by testing something - please let me know.

Comment 1 Tom Albers 2006-02-04 21:10:51 UTC

Could you verify with the libgphoto2 makers if this is a bug on their side?

Comment 2 caulier.gilles 2007-09-12 05:11:37 UTC


*** This bug has been marked as a duplicate of 149786 ***

Comment 3 David John Mills 2007-10-09 04:50:34 UTC

I don't believe that this is a duplicate of 149786.  I get the same behavior with all my cameras.  You can download a single image, delete it and immediately attempt to get the next image - which fails.

It is the delete step that sets up the issue.  If you download one selection of image(s), then not delete, you can immediately download a second set.  But if you attempt to delete any in between the 2 downloads, that is when the error occurs.

Comment 4 Arnd Baecker 2007-10-09 09:14:51 UTC

Reopening this bug in view of the last comment 
(so that it does not fall through the cracks ...)

Comment 5 caulier.gilles 2008-12-05 13:07:01 UTC

What's news about this file. It still valid using digiKam 0.9.4 and a recent libgphoto2 ?

Gilles Caulier

Comment 6 Nicolas L. 2009-04-19 01:40:22 UTC

is this bug still valid for digikam 0.10  ?

Comment 7 Nicolas L. 2009-07-21 00:14:40 UTC

is this bug still valid with digikam 1.0.0 beta2 ?

Comment 8 caulier.gilles 2015-07-03 06:00:43 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 9 caulier.gilles 2016-07-15 16:23:50 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