Bug 149490

Summary: after uploading new pictures, the album isn't displaying new picture, even after refresh, only restart works
Product: [Applications] digikam Reporter: schmirrwurst
Component: Albums-MainViewAssignee: Digikam Developers <digikam-bugs-null>
Status: RESOLVED FIXED    
Severity: normal    
Priority: NOR    
Version: 0.9.2   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed In: 1.0.0

Description schmirrwurst 2007-09-02 19:23:47 UTC 
Version:           0.9.2-final (using KDE 3.5.7, Kubuntu (gutsy) 4:3.5.7-1ubuntu14)
Compiler:          Target: i486-linux-gnu
OS:                Linux (i686) release 2.6.22-10-generic

I've added some pictures from my digital camera, and they don't appear in the album, I've pressed F5 to refresh, but they don't appear.
Only after a restart from the program I was able to see them
Comment 1 caulier.gilles 2007-09-02 19:47:11 UTC 
Not reproductible too...

Gilles Caulier
Comment 2 schmirrwurst 2007-09-02 20:40:07 UTC 
I could reproduce it twice !
Comment 3 caulier.gilles 2007-09-02 20:44:26 UTC 
Are you few messages on the console ?

Gilles Caulier
Comment 4 caulier.gilles 2007-12-04 08:14:56 UTC 
Marcel,

Sometime, i can reproduce this problem on my computers, sometime no. Sound like a race condition somewhere (scanlib ?)

Can you reproduce it ?

Gilles
Comment 5 caulier.gilles 2008-12-05 12:46:23 UTC 
What's news about this file ? it still valid using digiKam 0.9.4 ?

Andi, can you reproduce it ?

Gilles Caulier
Comment 6 Andi Clemens 2008-12-05 12:54:48 UTC 
Well this sometimes happens to me, too. For example when I use the RemoveRedEyes plugin (which creates new subfolders), then the subfolder will not be visible. But "Scan for new images" normally solves the problem.
This is not happening all the time though.

Andi
Comment 7 Andi Clemens 2009-10-20 17:43:02 UTC 
I guess this is not happening anymore in 1.0.0 and KDE4, could never reproduce it again.
Comment 8 Andi Clemens 2009-10-25 16:18:59 UTC 
No feedback since two years, and I'm sure it has been fixed.
I will close this report now as FIXED.