[digikam] [Bug 347348] New: Moving a directory loses metadata in database associated with .cr2 raw files

[Kenneth Ingham]

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

            Bug ID: 347348
           Summary: Moving a directory loses metadata in database
                    associated with .cr2 raw files
           Product: digikam
           Version: 4.9.0
          Platform: openSUSE RPMs
                OS: Linux
            Status: UNCONFIRMED
          Severity: critical
          Priority: NOR
         Component: Database
          Assignee: [hidden email]
          Reporter: [hidden email]

With two versions of digikam running, I move a directory(folder) from one
location to another.  The files, including the metadata sidecar files are
properly moved.  However, after the move, the .cr2 raw files no longer show any
metadata.  Looking in the sidecar file, I can see the tags, copyright, caption,
etc.  However, they do not show up with the thumbnails nor in the metadata side
panel.  Selecting read metadata from file to database does nothing (shouldn't
it try reading the sidecar?).

 JPEG, TIFF, and other files where the metadata is stored in the file itself
seem to move OK; I am guessing that scanning a new directory picks it up.
However, since digikam is doing the moving, shouldn't it know to update the
database as it moves the files?  And, it should be able to read metadata from
the sidecar in any case.

Reproducible: Always

Steps to Reproduce:
1. Add metadata to a .cr2 file with sidecar storage.
2. Move the folder somewhere else.
3. Look at the new location.

Actual Results:  
All raw files have lost metadata, but JPEG, TIFF, and other files where the
metadata is stored in the file itself move OK.

Expected Results:  
Metadata stored in the database moves with the files.  Metadata in sidecar
files should be able to be loaded into the database.

Possibly relevant packages:
digikam-4.9.0-1.1.x86_64
digikam-doc-4.9.0-1.1.noarch
digikam-debuginfo-4.9.0-1.1.x86_64
kipi-plugins-geolocation-4.9.0-1.1.x86_64
kipi-plugins-lang-4.9.0-1.1.noarch
kipi-plugins-acquireimage-debuginfo-4.9.0-1.1.x86_64
kipi-plugins-4.9.0-1.1.x86_64
libkipi-devel-14.12.3-16.1.x86_64
kipi-plugins-geolocation-debuginfo-4.9.0-1.1.x86_64
kipi-plugins-acquireimage-4.9.0-1.1.x86_64
kipi-plugins-debuginfo-4.9.0-1.1.x86_64
libkipi11-14.12.3-16.1.x86_64

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Kenneth Ingham]

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

--- Comment #1 from Kenneth Ingham <[hidden email]> ---
This is related to, but different from 326112.

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Maik Qualmann]

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

Maik Qualmann <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[hidden email]

--- Comment #2 from Maik Qualmann <[hidden email]> ---
The problem is not reproducible in a short test. All metadata from sidecar are
displayed after moving the CR2 files. If the images are stored on a network or
local drive?

Maik

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-4]

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

Gilles Caulier <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[hidden email]

--- Comment #3 from Gilles Caulier <[hidden email]> ---
Same here : not reproducible with files in local collection.

Gilles Caulier

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Kenneth Ingham]

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

--- Comment #4 from Kenneth Ingham <[hidden email]> ---
This is bizarre.  It happened yesterday.  Today, I cannot reproduce it.  I will
keep experimenting to figure out what the specific circumstances are.

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-4]

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

Gilles Caulier <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|---                         |WAITINGFORINFO

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Kenneth Ingham]

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

--- Comment #5 from Kenneth Ingham <[hidden email]> ---
It just happened again.

OK, this is weird.  The data was not showing up, and then when I went to gather
additional data for this update, it was there.  Is there a noticeable delay (at
least a couple of minutes) between moving and the data showing up in the
database?

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-4]

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

--- Comment #6 from Gilles Caulier <[hidden email]> ---
It can be. This depend of many factor.

I think the most important is DB file fragmentation, especially if file size is
big, refer to a huge collection of image, and is located to an hard drive.

Personalty, i use SSD to host BD (and also photo : 1Gb device). Time responsive
is very very fast. I manage over 250Gb of photo.

Note : It miss a tool to check DB integrity in digiKam. There is a file in
bugzilla about this topic.
Gilles

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-4]

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

--- Comment #7 from Gilles Caulier <[hidden email]> ---
It can be a good indicator to evaluate the CPU/Memory overload when it's
happen. Perhaps something take a while and slow down DB on your system.

Gilles Caulier

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-4]

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

--- Comment #8 from Gilles Caulier <[hidden email]> ---
New digiKam 4.11.0 is available :

https://www.digikam.org/node/740

Can you reproduce the problem with this release ?

Gilles Caulier

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-4]

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

--- Comment #9 from Gilles Caulier <[hidden email]> ---
digiKam 4.12.0 is out :

https://www.digikam.org/node/741

We need a fresh feedback using this release please...
Thanks in advance.

Gilles Caulier

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Kenneth Ingham]

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

--- Comment #10 from Kenneth Ingham <[hidden email]> ---
I do not see this problem with 4.11.

Thanks.

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-4]

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

Gilles Caulier <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|WAITINGFORINFO              |FIXED
   Version Fixed In|                            |4.13.0

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[bugzilla_noreply]

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

[hidden email] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|Database                    |Database-Files

--
You are receiving this mail because:
You are the assignee for the bug.