| Summary: | after moving album and pictures, they are displayed like before | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | Rainer Lay <rainer.lay> |
| Component: | Albums-IconView | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | caulier.gilles, jimi, timetre |
| Priority: | NOR | ||
| Version: | 1.4.0 | ||
| Target Milestone: | --- | ||
| Platform: | openSUSE | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | 2.5.0 | |
| Sentry Crash Report: | |||
| Attachments: |
After enabling "scan on startup", the folder ist still empty.
Three files are moved the files are still displayed, although they are not there anymore, as you can see in the explorer window |
||
|
Description
Rainer Lay
2010-09-05 22:41:30 UTC
What happens when you press F5? Can you give console output (enable 50003 in kdebugdialog) while moving files? 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. If you are really using digikam 1.4, F5 is definitely rescanning the current directory. 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. 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. 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. Hendric: Do you have scan at startup disabled? Marcel. Scan at startup was disabled. Could this be the cause for the album to remain invisible? Hendric Probably. Digikam wont scan if you disabled scanning ;-) Hendric, Do you see comment #9 from Marcel ? It still valid using digiKam 2.4 ? Gilles Caulier 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 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 Created attachment 66785 [details]
After enabling "scan on startup", the folder ist still empty.
Created attachment 66786 [details]
Three files are moved
Created attachment 66787 [details]
the files are still displayed, although they are not there anymore, as you can see in the explorer window
unfortunatly, the hint from comment #9 is not working, as you can see in the last three screenshots. I am using 2.3 too 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 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. 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. |