SUMMARY When renaming an album, all collections' trees are expanded. In the collection tree where that album is, the whole tree is expanding. In other trees, only the first level. Observed on Win 10 and KDE Neon. STEPS TO REPRODUCE 1. Right-click in the tree, select Collapse all albums 2. Open a tree, select an album and rename it OBSERVED RESULT All the trees expand as described EXPECTED RESULT The trees stay as they were with the album renamed. SOFTWARE/OS VERSIONS Windows: 10 KDE Plasma: Neon with Plasma 5.27
Not a big bug, but a real annoyance when working on a large photo collection.
I only have Windows 10 here at the moment, but I can't reproduce this behavior. Maik
Same here with Kubuntu 22.04, 23.04, and 23.10. Not reproducible...
Really? That's weird because this is a bug I have been observing for weeks so not a sudden issue for me. Note that I started using DIgikam al lot a few weeks ago (instead of once in a while). Hum. I could send you a screen cast I presume - but that won't help a lot, will it ? Except showing that I have not gone postal. What can I do then to help make it reproducible?
yes, really. Qt6 is used everywhere on my computers, not Qt5
I happen to have upgraded to Plasma 6 and Wayland - without knowing it beforehand it was such a huge upgrade. I was lucky though, only details don't work. So I tested "my" tree bug and reproduced it once again. I also check through a remote session that it happens as well on my father's computer, a Win10 laptop. His digikam db and collections are different than mine, so it's not only "my" computer. A family bug? :-) My current Neon conf: Operating System: KDE neon 6.0 KDE Plasma Version: 6.0.0 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.5.0-21-generic (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-3770T CPU @ 2.50GHz Memory: 15,4 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 4000 At this point, I can only hope that other users confirm the issue. I've made many trials to find a circumstance when the bug would NOT appear. I just found that the bug is even more obvious when the album renamed is situated not in the first collection but on the next ones (the whole trees expand). However, it's just an annoyance and not a blocking thing, so no reason to make it a priority of any sort. In all cases, thank both of you for your super quick reaction to try and reproduce it ; it's super nice to feel supported and it shows how serious the Digikam team is. Best regards.
Wayland is really a mess for the moment to use in production. Use X11 instead. Gilles Caulier
Wayland would be an option under Linux and Neon means that an Snap package from digiKam with Sandbox is probably used. But - that does not explain the behavior under Windows10. I have now added a very large album tree under Windows10 for testing, but the problem cannot be reproduced. I am also sure that such behavior would have been reported immediately by other users. In the right mouse button menu do you use "Renaming" or the "Properties"? Maik
Can you also please test the pre-release version of digiKam-8.3.0, there is no database change in this version, download from here: https://files.kde.org/digikam/ Maik
There it is : using Right-Click and Rename works well. It's using "Properties" that provokes the trees expansion. I use Properties by habit, no reason else. Can you reproduce it now ? I'll tell you if this is also true on Win 10 tomorrow. I don't use Snap. I installed Digikam using pkcon (eg Neon wrapper for apt). I install my apps with pkcon (generic + private ppa's) or flathub. Should I prefer one method? I installed Digikam on both my Win10 and my father's using chocolatey, for the record. My father has a big db: 56 000 objects, several collections, lots of directories. Mine is much smaller, a few thousand photos and much simpler tree. I'm not sure this is part of the issue. I realize now that lead wasn't relevant, sorry for that. I'll try the 8.3 pre-release. I used X11 until yesterday and for now Wayland works ... perfectly well. Nothing to complain so far but I'll give it a try for a few days before making a decision. I'm agnostic on the matter and not technical enough to grasp the stakes between the two. I would not be surprised to move back to X11 : it has been fine for me for quite a few years.
Git commit c72441eedb8486d6da725ad9e16ea89d087169ce by Maik Qualmann. Committed on 02/03/2024 at 06:54. Pushed by mqualmann into branch 'master'. fix a possible expansion of the album tree view after editing album properties FIXED-IN: 8.3.0 M +1 -1 NEWS M +6 -0 core/app/views/sidebar/albumfolderviewsidebarwidget.cpp M +2 -0 core/app/views/sidebar/albumfolderviewsidebarwidget.h M +1 -20 core/app/views/stack/itemiconview_albums.cpp M +4 -0 core/libs/album/engine/albummodificationhelper.cpp https://invent.kde.org/graphics/digikam/-/commit/c72441eedb8486d6da725ad9e16ea89d087169ce
Git commit 94147e3e6a263e367ee6d0573385b49866e67f6a by Maik Qualmann. Committed on 02/03/2024 at 07:03. Pushed by mqualmann into branch 'master'. remove unused album sorting application setting M +1 -18 core/libs/album/treeview/abstractalbumtreeview.cpp M +0 -3 core/libs/settings/applicationsettings.h M +0 -10 core/libs/settings/applicationsettings_albums.cpp M +0 -2 core/libs/settings/applicationsettings_p.cpp M +0 -1 core/libs/settings/applicationsettings_p.h https://invent.kde.org/graphics/digikam/-/commit/94147e3e6a263e367ee6d0573385b49866e67f6a
In fact, I was only able to reproduce it in one of my test configurations by renaming it via the album properties. But the cause of the problem is clear and has now been resolved. Maik
Awesome! Thank you for your fortitude into solving this! My best regards to you and Gilles, and the whole team for Digikam - this such useful tool. We use it for family memories, like many obviously. The important thing here it that it brings a lot of happiness in this world: that's an important job you're doing. And it keeps that away from surveillance states (that even democracies have become) and greedy global corporations. That's important work and something to be proud of. Sorry if that feels a bit over, I needed to express my gratitude! Best regards.