Bug 250316 - after moving album and pictures, they are displayed like before
Summary: after moving album and pictures, they are displayed like before
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Albums-IconView (show other bugs)
Version: 1.4.0
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-09-05 22:41 UTC by Rainer Lay
Modified: 2017-08-15 12:40 UTC (History)
3 users (show)

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


Attachments
After enabling "scan on startup", the folder ist still empty. (145.66 KB, image/png)
2011-12-15 20:08 UTC, Rainer Lay
Details
Three files are moved (233.66 KB, image/png)
2011-12-15 20:09 UTC, Rainer Lay
Details
the files are still displayed, although they are not there anymore, as you can see in the explorer window (113.67 KB, image/png)
2011-12-15 20:41 UTC, Rainer Lay
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Rainer Lay 2010-09-05 22:41:30 UTC
Version:           1.4.0 (using KDE 4.5.0) 
OS:                Linux

the albums or pictures should be displayed like moved, but they are not.
When trxing to move the items again,a error message pops up like: there is not picture/album. 
This still happens after restarting digikam!

Reproducible: Always

Steps to Reproduce:
move an album into another

Actual Results:  
the album is displayed like it isn't moved

Expected Results:  
album is not only moved, but also displayed as moved

OS: Linux (i686) release 2.6.31.12-0.2-default
Compiler: gcc
Comment 1 Marcel Wiesweg 2010-09-06 09:41:26 UTC
What happens when you press F5?

Can you give console output (enable 50003 in kdebugdialog) while moving files?
Comment 2 Rainer Lay 2010-09-06 14:12:36 UTC
After F5, nothing changed. It looks like F5 is only updating thumbnails, even changed on the file system (new picture, deleted pictures) is not recognized, as expected by me.
I will have a look in the kdebugdialog, as soon as I understood this thing.
Comment 3 Marcel Wiesweg 2010-09-06 17:23:07 UTC
If you are really using digikam 1.4, F5 is definitely rescanning the current directory.
Comment 4 Rainer Lay 2010-09-15 23:53:02 UTC
OK, F5 is rescanning the current directory. But it isn't showing the expected result: after moving a file in the konsole, I expect that the picture is not shown anymore, after pressing F5 - but it still is. The pictures are repainted, but the one moved via konsole ist still available.
After a while, the picture is not shown anymore.
Comment 5 Vincent Tassy 2010-11-07 22:16:22 UTC
I'm experiencing the same problem on 1.5
Was running 1.2 until yesterday and now that I'm on 1.5 here's what happens:
- Move one folder from one collection to another collection
- Folder and content are now visible in the destination collection
- Folder and content thumbnails still visible in the original collection !
- Physically, the files have been moved (they're in the destination collection and no longer in the original one)
- Pressing F5 doesn't fix it
- Rescaning the collections doesn't fix it
- Closing digikam, relaunching it still shows the folder and thumbnails in the original collection
- Rescaning the collections now makes the folder disappear from the original collection at last ...

It's reproductible everytime.
Comment 6 Hendric Stattmann 2011-08-04 11:52:14 UTC
I can confirm this behavior in 2.0.
Also, if a new folder is created using Dolphin (KDE 4.7) inside my collection while Digikam is NOT running, it does NOT appear in the album list when I launch Digikam, even if I wait a while or restert Digikam.
This bug does NOT appear if the folder is created in a console (mkdir...) or with Dolphin while Digikam is running.
Comment 7 Marcel Wiesweg 2011-08-06 13:05:04 UTC
Hendric: Do you have scan at startup disabled?
Comment 8 Hendric Stattmann 2011-08-06 13:18:43 UTC
Marcel.

Scan at startup was disabled. Could this be the cause for the album to remain invisible?
Hendric
Comment 9 Marcel Wiesweg 2011-08-06 13:29:51 UTC
Probably. Digikam wont scan if you disabled scanning ;-)
Comment 10 caulier.gilles 2011-12-14 09:42:46 UTC
Hendric,

Do you see comment #9 from Marcel ?

It still valid using digiKam 2.4 ?

Gilles Caulier
Comment 11 Hendric Stattmann 2011-12-14 09:52:50 UTC
Dear Gilles,

After proceeding according to Marcel's recommendation, I do not run into this problem anymore. From my side, you may mark this bug as closed.
Hendric
Comment 12 Vincent Tassy 2011-12-14 09:57:31 UTC
It was still true in 1.9

It's fixed in 2.3 (I expect it's still fixed in 2.4 ;-)

For me, you can close this one
Comment 13 Rainer Lay 2011-12-15 20:08:51 UTC
Created attachment 66785 [details]
After enabling "scan on startup", the folder ist still empty.
Comment 14 Rainer Lay 2011-12-15 20:09:18 UTC
Created attachment 66786 [details]
Three files are moved
Comment 15 Rainer Lay 2011-12-15 20:41:53 UTC
Created attachment 66787 [details]
the files are still displayed, although they are not there anymore, as you can see in the explorer window
Comment 16 Rainer Lay 2011-12-15 20:43:47 UTC
unfortunatly, the hint from comment #9 is not working, as you can see in the last three screenshots. I am using 2.3 too
Comment 17 Marcel Wiesweg 2011-12-25 11:49:59 UTC
Rainer,

I'm not sure if this is a new problem or an old scenario
- 2.4 brings direct usage of inotify on Linux, so it would be interesting if you can still reproduce a new problem (move while digikam is running.) 
- if this is an old scenario, I might want to have a look into your digikam4.db file, because I have no idea what's happening
Comment 18 Rainer Lay 2011-12-27 10:20:18 UTC
Marcel,

meanwhile I am using windows (version 2.3), so I asume, it is still the old scenario.
I tried to mail the db file.
Comment 19 Rainer Lay 2012-06-27 17:58:38 UTC
Gilles, in my windows 2.5.0 version, the bug was still there.
After the 2.6.0 windows release, I will try this again.