Bug 248494

Summary:	Deleted pictures still shown: Have to rescan collection always
Product:	[Applications] digikam	Reporter:	Bruno Léon <bruno.leon>
Component:	Database-Scan	Assignee:	Digikam Developers <digikam-bugs-null>
Status:	RESOLVED WORKSFORME
Severity:	normal	CC:	caulier.gilles, kde, roger.larsson
Priority:	NOR
Version:	1.3.0
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed In:	2.0.0
Sentry Crash Report:

Description Bruno Léon 2010-08-20 12:14:38 UTC

Version:           1.3.0 (using KDE 4.5.0) 
OS:                Linux

Whenever I delete a picture or a set of pictures, it is actually deleted but Digikam still shows it in the interface.
I have to rescan the collection to have them actually not shown.


Reproducible: Always

Steps to Reproduce:
Delete some pics.


Actual Results:  
They are deleted but still shown.

Expected Results:  
Deleted pictures should be immediately not shown?

Comment 1 caulier.gilles 2010-08-20 12:19:04 UTC

This is relevant of KDE4::KDirWatch event which look if something change on your dir.

I cannot reproduce the problem here with KDE 4.4.3

Something has changed (again) about KDirWatch with KDE 4.5 ?

Gilles Caulier

Comment 2 Bruno Léon 2010-08-22 17:33:24 UTC

I don't know if there has been any change to KdirWatch and did not find any information about it.

However to complete the issue, it also happens if I copy a set of pictures in an album. I have to rescan collection for them to appear.

Comment 3 Nicolas L. 2010-11-25 09:00:43 UTC

i can't reproduce with kde 4.5 and 4.6beta1


Do you reproduce with updates of your distribution ?

Comment 4 Bruno Léon 2011-05-05 04:26:10 UTC

Log time after sorry.
The problem is still the same with KDE 4.6.2 and os Kubuntu (maverick still)

I reproduce it on multiple computers.
Does it really disappear instantaneously on yours ?

Comment 5 Roger Larsson 2011-05-05 08:28:29 UTC

Do you delete the pictures using digikam or in some other way?
If in some other way - did you have digikam running?
Please describe exactly what you do - step by step.

Comment 6 Bruno Léon 2011-05-27 21:06:07 UTC

Hello,

actually the latest version of Digikam (2.0 b5) seems to have fixed it.
You can close this bug AFAIK.

Thanks.