Bug 464613

Summary:	Moving images to another album from fuzzy search copies first file (instead of moving it)
Product:	[Applications] digikam	Reporter:	Jens <jens-bugs.kde.org>
Component:	Searches-Similarity	Assignee:	Digikam Developers <digikam-bugs-null>
Status:	REPORTED ---
Severity:	normal	CC:	caulier.gilles, metzpinguin
Priority:	NOR
Version First Reported In:	7.10.0
Target Milestone:	---
Platform:	Appimage
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Jens 2023-01-21 21:23:29 UTC

SUMMARY: see $SUBJECT

STEPS TO REPRODUCE
1.  Search for some images by similarity
2. Select some of the results
3. Right-click, choose "Move to album ...", select album

OBSERVED RESULT
All but one images are moved.
One is copied.

EXPECTED RESULT
All images should be moved.

SOFTWARE/OS VERSIONS: KDE Neon 22.04 with all updates applied. Digikam appimage 7.10.0.

Comment 1 Maik Qualmann 2023-01-21 21:37:01 UTC

I cannot reproduce the problem here under digiKam-8.0.0-Beta1, all selected images are moved to the album. We need a debug log from the action when the problem occurs.

Don't expect the selected images to disappear from the duplicate search. If you have grouping by albums enabled, you can see the album path change.

Maik

Comment 2 Jens 2023-01-21 21:40:32 UTC

Sorry, I have to rephrase. To reproduce:

1. same but limit the similarity search to some folders
2. select
3. move to another album NOT selected (ie. outside the search scope)

Result:
All images are moved correctly.
But one of them (I think always the first) stays in the search view, although it is now out of search scope.

Expected: All moved images should disappear from the similarity search window.

This is obvious if you have grouping by folder/album activated (thanks for that idea).

Comment 3 caulier.gilles 2023-05-03 03:05:42 UTC

Hi Jens,

With next 8.1.0 (current implementation from git/master), few important patches have been applied into the similarities search engine. Can you reproduce the problem ?

Best

Gilles Caulier

Comment 4 caulier.gilles 2023-10-10 03:12:10 UTC

@Jens,

Please give us a fresh feedback using the current digiKam AppImage Linux bundle
pre-release 8.2.0 available here:

https://files.kde.org/digikam/

This one is compiled with last Qt 5.15.11 (previous one used Qt 5.15.7)
Thanks in advance

Gilles Caulier

Comment 5 caulier.gilles 2023-10-11 05:35:24 UTC

@Jens,

What's about this file using current 8.2.0 AppImage Linux bundle ? It's
reproducible ?

https://files.kde.org/digikam/

Thanks in advance

Gilles Caulier

Comment 6 caulier.gilles 2024-04-20 03:22:59 UTC

Hi all,

The digiKam 8.4.0 Appimage bundle pre-release is now based on last modern frameworks Qt 6.7.0 and KDE 6.2.0.

File can be downloaded at usual place : https://files.kde.org/digikam/
Take a  care : the bundle is named with the suffix "-Qt6" not "-Qt5". This bundle is compiled under Ubuntu 22.04 and require a Linux with GlibC version >= 2.35 to run.

Can you reproduce the dysfonction with this version?

Thanks in advance

Gilles Caulier

Comment 7 caulier.gilles 2025-04-04 01:43:23 UTC

Hi Jens,

The new AppImage bundle 8.7.0 pre-release for Linux based on Qt 6.8.3 is
online at usual place :

https://files.kde.org/digikam/

Let's me know if the problem remain.

Best regards

Gilles Caulier

Comment 8 caulier.gilles 2025-12-18 13:00:23 UTC

Jens,

Any feedback using 8.8.0 stable release ?

Gilles Caulier