Bug 367083 - Not Writing Labels to XMP Sidecar
Summary: Not Writing Labels to XMP Sidecar
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Metadata-Sidecar (show other bugs)
Version: 5.1.0
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-08-17 10:33 UTC by red72
Modified: 2017-01-19 11:40 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In: 5.5.0


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description red72 2016-08-17 10:33:03 UTC
I have been using digikam for many years and writing labels (ratings, colors, etc) to xmp sidecars.  I cannot get them to write now after many hours of trying.  I think the problem started when I updated to Ubuntu 16.04 back in May but I am not sure of that as I just noticed.  I had both digikam 4.12 and 5.01 installed and neither worked.  I uninstalled both and reinstalled 5.01 and still does not work.  It is writing to the digikam database because the ratings are still there after I close and open digikam.   Under the configuration menu I have played with every every combination of writing metadata with no luck.

Reproducible: Always
Comment 1 caulier.gilles 2016-08-17 10:36:37 UTC
start digiKam from a console. What do you see as debug trace while you try to repeat the operation with different settings.

Gilles Caulier
Comment 2 red72 2016-08-17 10:44:04 UTC
Nothing happens in the colsole.  In the bottom right corner of digikam I get a message that says "Assign Image Rating".  When I quit digikam I get the following.  


digikam.geoiface: ----
defaultServiceProvider::requestService(): no service found for - "org.qt-project.qt.mediaplayer"
digikam.general: Cancel Main Thread
digikam.general: Cancel Main Thread
digikam.general: Cancel Main Thread
digikam.general: Cancel Main Thread
digikam.general: Cancel Main Thread
digikam.general: Cancel Main Thread
QThreadStorage: Thread 0x233a6c0 exited after QThreadStorage 16 destroyed
QThreadStorage: Thread 0x233a6c0 exited after QThreadStorage 13 destroyed
fischer@fischer-ThinkPad-T430s:~$
Comment 3 red72 2016-08-17 11:04:39 UTC
I forgot to mention in my first post, that I think I had a error when I first installed digikam.  I did a few google searches and got digikam working with someone's suggestion.  I looked through my history and could not find anything about the error.   Sorry.
Comment 4 caulier.gilles 2016-11-28 11:41:40 UTC
Can you reproduce the problem using digiKam Linux AppImage bundle ? The last
bundle is available at this url:

https://drive.google.com/drive/folders/0BzeiVr-byqt5Y0tIRWVWelRJenM

Gilles Caulier
Comment 5 red72 2017-01-19 11:28:08 UTC
I just installed and 5.4 and the issue is resolved.  Thank you!