Hello, I have noticed that dk6.2-git does not show some images in the folder. That is not the old versioning problem, the option "always show original images" is activated. Here is what happens when I right click on the album and press "refresh": --- [376328] digikam.general: scan mode: ScheduleCollectionScan :: ("C:/Users/wca0272/Desktop/San Antonio 2018/2019-04 Easter photosession/") [376328] digikam.general: Action Thread run 4 new jobs [376328] digikam.general: Event is dispatched through a passive pop-up [376328] QLayout: Attempting to add QLayout "" to QWidget "", which already has a layout [376328] digikam.dimg: "C:/Users/wca0272/Desktop/San Antonio 2018/2019-04 Easter photosession/IMG_5321.JPG" : JPEG file identified [376328] digikam.dimg: "C:/Users/wca0272/Desktop/San Antonio 2018/2019-04 Easter photosession/IMG_5326.JPG" : JPEG file identified [376328] digikam.dimg: "C:/Users/wca0272/Desktop/San Antonio 2018/2019-04 Easter photosession/IMG_5332.JPG" : JPEG file identified [376328] digikam.dimg: "C:/Users/wca0272/Desktop/San Antonio 2018/2019-04 Easter photosession/IMG_5335.JPG" : JPEG file identified [376328] digikam.dimg: "C:/Users/wca0272/Desktop/San Antonio 2018/2019-04 Easter photosession/IMG_5339.JPG" : JPEG file identified [376328] digikam.dimg: "C:/Users/wca0272/Desktop/San Antonio 2018/2019-04 Easter photosession/IMG_5340.JPG" : JPEG file identified [376328] digikam.dimg: "C:/Users/wca0272/Desktop/San Antonio 2018/2019-04 Easter photosession/IMG_5354.JPG" : JPEG file identified [376328] digikam.dimg: "C:/Users/wca0272/Desktop/San Antonio 2018/2019-04 Easter photosession/IMG_5355.JPG" : JPEG file identified [376328] digikam.dimg: "C:/Users/wca0272/Desktop/San Antonio 2018/2019-04 Easter photosession/IMG_5361.JPG" : JPEG file identified [376328] digikam.dimg: "C:/Users/wca0272/Desktop/San Antonio 2018/2019-04 Easter photosession/IMG_5375.JPG" : JPEG file identified [376328] digikam.dimg: "C:/Users/wca0272/Desktop/San Antonio 2018/2019-04 Easter photosession/IMG_5379.JPG" : JPEG file identified [376328] digikam.dimg: "C:/Users/wca0272/Desktop/San Antonio 2018/2019-04 Easter photosession/IMG_5381.JPG" : JPEG file identified [376328] digikam.dimg: "C:/Users/wca0272/Desktop/San Antonio 2018/2019-04 Easter photosession/IMG_5383.JPG" : JPEG file identified [376328] digikam.dimg: "C:/Users/wca0272/Desktop/San Antonio 2018/2019-04 Easter photosession/IMG_5394.JPG" : JPEG file identified [376328] digikam.dimg: "C:/Users/wca0272/Desktop/San Antonio 2018/2019-04 Easter photosession/IMG_5397.JPG" : JPEG file identified [376328] digikam.dimg: "C:/Users/wca0272/Desktop/San Antonio 2018/2019-04 Easter photosession/IMG_5401.JPG" : JPEG file identified [376328] digikam.dimg: "C:/Users/wca0272/Desktop/San Antonio 2018/2019-04 Easter photosession/IMG_5404.JPG" : JPEG file identified [376328] digikam.dimg: "C:/Users/wca0272/Desktop/San Antonio 2018/2019-04 Easter photosession/IMG_5407.JPG" : JPEG file identified [376328] digikam.dimg: "C:/Users/wca0272/Desktop/San Antonio 2018/2019-04 Easter photosession/IMG_5412.JPG" : JPEG file identified [376328] digikam.dimg: "C:/Users/wca0272/Desktop/San Antonio 2018/2019-04 Easter photosession/IMG_5415.JPG" : JPEG file identified [376328] digikam.dimg: "C:/Users/wca0272/Desktop/San Antonio 2018/2019-04 Easter photosession/IMG_5423.JPG" : JPEG file identified [376328] digikam.dimg: "C:/Users/wca0272/Desktop/San Antonio 2018/2019-04 Easter photosession/IMG_5427.JPG" : JPEG file identified [376328] digikam.dimg: "C:/Users/wca0272/Desktop/San Antonio 2018/2019-04 Easter photosession/IMG_5432.JPG" : JPEG file identified [376328] digikam.dimg: "C:/Users/wca0272/Desktop/San Antonio 2018/2019-04 Easter photosession/IMG_5435.JPG" : JPEG file identified [376328] digikam.dimg: "C:/Users/wca0272/Desktop/San Antonio 2018/2019-04 Easter photosession/IMG_5453.JPG" : JPEG file identified [376328] digikam.dimg: "C:/Users/wca0272/Desktop/San Antonio 2018/2019-04 Easter photosession/IMG_5460.JPG" : JPEG file identified [376328] digikam.dimg: "C:/Users/wca0272/Desktop/San Antonio 2018/2019-04 Easter photosession/IMG_5476.JPG" : JPEG file identified [376328] digikam.dimg: "C:/Users/wca0272/Desktop/San Antonio 2018/2019-04 Easter photosession/IMG_5485.JPG" : JPEG file identified [376328] digikam.general: One job is done [376328] digikam.general: One job is done [376328] digikam.general: One job is done [376328] digikam.general: One job is done [376328] digikam.general: List of Pending Jobs is empty [376328] digikam.general: Event is dispatched through a passive pop-up [376328] QLayout: Attempting to add QLayout "" to QWidget "", which already has a layout [376328] digikam.general: Cancel Main Thread [376328] digikam.general: Cancel Main Thread --- It looks like digiKam actually sees all 28 items in the folder however it only displays 2 of them. If I click Album - Open in File Manager I can see all the images. Build date of my installation is July 14th https://cgit.kde.org/digikam.git/commit/?id=f60227908e73a6cb0ddcdc0fb9cbc03116ccb1ad Best regards, Andrey
Build date of my installation is July 14th ==> did you compile yourself digiKam or you use the windows installer ? Gilles Caulier
(In reply to caulier.gilles from comment #1) > Build date of my installation is July 14th ==> did you compile yourself > digiKam or you use the windows installer ? > > Gilles Caulier Gilles, I used your installer.
If I right click on the album in the folder tree and export to Google Photos I see that all the images are on the list. OpenGL Image Viewer displays all the images as well. So I think there is a possible bug with how the images displayed in album view. I tried Table view and I also tried playing with all Sort settings in View menu but it has not changed anything.
I do not think that it is a bug in digiKam-6.2.0, probably the images would not appear even with digiKam-6.1.0. One way that could produce this effect would be to have an album-spanning grouping done. Then you have to find the leader image and dissolve the group again. Maik
(In reply to Maik Qualmann from comment #4) > I do not think that it is a bug in digiKam-6.2.0, probably the images would > not appear even with digiKam-6.1.0. One way that could produce this effect > would be to have an album-spanning grouping done. Then you have to find the > leader image and dissolve the group again. > > Maik Maik, You are correct about 6.1.0 I am wondering how do I ungroup the images now.
(In reply to Maik Qualmann from comment #4) > One way that could produce this effect > would be to have an album-spanning grouping done. Then you have to find the > leader image and dissolve the group again. Maik, I am not sure how to do that. I only see 2 images of 28. I tried to group/ungroup them but nothing happens... Would you have any idea on how do I make the images visible again?
Do you use SQLite or MySQL as a database? Do you use grouping in digiKam or not? Maik
(In reply to Maik Qualmann from comment #7) > Do you use SQLite or MySQL as a database? Do you use grouping in digiKam or > not? > > Maik I use SQLite. The only grouping I use is 'group by filename' on DNG/JPG pairs. These particular images are JPG only though. I don't know if is relevant but I got these images from a photographer and I noticed the photographer used Adobe Lightroom to create them.
Git commit 1a5cf4a7885868a70e5ed07ab4ff4b4a7c80de9a by Maik Qualmann. Committed on 05/08/2019 at 18:57. Pushed by mqualmann into branch 'master'. add "Reset Grouping" option to the album context menu M +30 -0 core/libs/album/treeview/albumselectiontreeview.cpp M +2 -0 core/libs/album/treeview/albumselectiontreeview.h https://invent.kde.org/kde/digikam/commit/1a5cf4a7885868a70e5ed07ab4ff4b4a7c80de9a
This new option in the album context menu resets all groupings in the selected album. We'll see if it's the cause with the next pre-release. Maik
You can test this version of my GDrive: https://drive.google.com/open?id=11OqmZODKOeVABvVHEb4NulxTpxxmIyxm ---------- Compute package checksums for digiKam 6.3.0-git File : digiKam-6.3.0-git-20190805T223602-Win64.exe Size : 171M MD5 sum : a5d97934f75faca1db3ff74d5920e487 SHA1 sum : 3b2b61b452733ddbeefdd982c2dd89204a98b06c SHA256 sum : 1576c006691b39dce689d4d4d970adce31f422800acbbeb4acb8816e858b1d8e Maik
(In reply to Maik Qualmann from comment #11) > You can test this version of my GDrive: > > https://drive.google.com/open?id=11OqmZODKOeVABvVHEb4NulxTpxxmIyxm > > ---------- Compute package checksums for digiKam 6.3.0-git > > File : digiKam-6.3.0-git-20190805T223602-Win64.exe > Size : 171M > MD5 sum : a5d97934f75faca1db3ff74d5920e487 > SHA1 sum : 3b2b61b452733ddbeefdd982c2dd89204a98b06c > SHA256 sum : 1576c006691b39dce689d4d4d970adce31f422800acbbeb4acb8816e858b1d8e > > Maik Maik, digikam 6.3.0-git Build date: Aug 6 2019 It worked. I think I know what happened. I think I grouped "web" and "full_resolution" versions of each image and then moved some of the images from the pairs to another folder outside of digiKam. I was not able to reproduce it though. So it is probably the user error as usual :-)
Actually I did reproduce it. To reproduce try to: 1. group IMAGE-1 and IMAGE-2 2. then in Windows File Explorer move the image from the top of the stack e.g. IMAGE-1 to another folder 3. Refresh the album in digiKam 4. Move IMAGE-1 back to the original folder 5. Refresh the album in digiKam again
Git commit 982c1c1146317253ebb5119770d665cdd6e5bdd0 by Maik Qualmann. Committed on 11/08/2019 at 10:27. Pushed by mqualmann into branch 'master'. give the user a hint in status bar if items are hidden by grouping or versioning FIXED-IN: 6.3.0 M +2 -1 NEWS M +18 -2 core/app/main/digikamapp.cpp https://invent.kde.org/kde/digikam/commit/982c1c1146317253ebb5119770d665cdd6e5bdd0