Digikam 5.1: No progress indicator when copying/moving images (+ no name collision resolution)!?

[Johannes Graumann-2]

Hello,

After managing the migration from 4.* to 5.1 on my debian stable/testing
system, I note that digikam 5.1 for me currently doesn't give any indication
as to whether a large copy/move process is finished - I have to watch the
database statement flying by on the console to be sure ... additionally there
is now image name collision resolution any longer ... 4.* used to throw a
dialog at me that offered to rename images where the file name was already
present in the target directory (while showing thumbnails making identity
checking easier) ... is that a shortcoming of the new version or the packaging
in debian?

Sincerely, Joh

[Gilles Caulier-4]

See this bugzilla entry :

https://bugs.kde.org/show_bug.cgi?id=233063

Gilles Caulier

2016-09-27 14:13 GMT+02:00 <[hidden email]>:

Hello,

After managing the migration from 4.* to 5.1 on my debian stable/testing
system, I note that digikam 5.1 for me currently doesn't give any indication
as to whether a large copy/move process is finished - I have to watch the
database statement flying by on the console to be sure ... additionally there
is now image name collision resolution any longer ... 4.* used to throw a
dialog at me that offered to rename images where the file name was already
present in the target directory (while showing thumbnails making identity
checking easier) ... is that a shortcoming of the new version or the packaging
in debian?

Sincerely, Joh

[Johannes Graumann]

Thank you for pointing out the feature request - I shall patiently wait and as
a temporary remedy watch the mysql statements fly by on the console in the
meantime ;)

Joh

On Tuesday, September 27, 2016 3:13:38 PM AST [hidden email]
wrote:

> Hello,
>
> After managing the migration from 4.* to 5.1 on my debian stable/testing
> system, I note that digikam 5.1 for me currently doesn't give any indication
> as to whether a large copy/move process is finished - I have to watch the
> database statement flying by on the console to be sure ... additionally
> there is now image name collision resolution any longer ... 4.* used to
> throw a dialog at me that offered to rename images where the file name was
> already present in the target directory (while showing thumbnails making
> identity checking easier) ... is that a shortcoming of the new version or
> the packaging in debian?
>
> Sincerely, Joh