Project

General

Profile

Bug #11527

Changed xmp files dialogue without effect

Added by Richard Wonka over 2 years ago. Updated over 2 years ago.

Status:
New
Priority:
Low
Category:
General
Target version:
-
Start date:
02/26/2017
Due date:
% Done:

0%

Estimated time:
Affected Version:
2.2.3
System:
other GNU/Linux
bitness:
64-bit
hardware architecture:
amd64/x86

Description

darktable recognises that xmp files have changed, but none of the proposed actions show any effect and the same dialogue is shown again when starting dt the next time.

darktable Screenshot from 2017-02-26 16_12_00.png (29.8 KB) darktable Screenshot from 2017-02-26 16_12_00.png none of the options have any effect. Richard Wonka, 02/26/2017 11:15 AM
dt.out (613 KB) dt.out two runs of darktable -d all -- re-reading xmp files, then overwriting them Richard Wonka, 02/27/2017 08:13 AM

History

#1 Updated by Tobias Ellinghaus over 2 years ago

  • Assignee set to Tobias Ellinghaus

Thus might be due to the checksum test which is trying to avoid writing XMP files when the content didn't change. I'll have a look.

#2 Updated by Tobias Ellinghaus over 2 years ago

Nope, I wasn't able to reproduce.

  • Could you please check file modification timestamps of the XMP when telling darktable to overwrite the sidecars?
  • What happens when you tell darktable to re-read the XMP files?
  • Do you have any unusual/special mount options for the drive where your images reside?
  • Are there any error messages shown when starting darktable from a terminal?

#3 Updated by Richard Wonka over 2 years ago

Tobias Ellinghaus wrote:

Nope, I wasn't able to reproduce.

Okay, let me see...

  • Could you please check file modification timestamps of the XMP when telling darktable to overwrite the sidecars?

Timestamps change to current time when overwriting.

  • What happens when you tell darktable to re-read the XMP files?

Apparently nothing. These are files I have not touched in ages.

  • Do you have any unusual/special mount options for the drive where your images reside?

These are in my /home partition (ext4) on an elementaryOS ext4 partition. here's the info:

richard@summersby:~$ mount | grep /home
/dev/sda2 on /home type ext4 (rw,relatime,data=ordered)
  • Are there any error messages shown when starting darktable from a terminal?

No error messages, I've appended full debugging output (-d all) of both attempts to this comment.

#4 Updated by Tobias Ellinghaus over 2 years ago

Please provide output of:

date "+%s" 
ls -l "/home/richard/Pictures/Keepers/2012-07-04_Lotus and Cat Pod_P1060378_02.jpg.xmp" 
sqlite3 ~/.config/darktable/library.db "select id, filename, version, max_version, write_timestamp from images where id = 814;" 

darktable thinks that the XMP of that image is newer than what it expects to see.

#5 Updated by Richard Wonka over 2 years ago

richard@summersby:~$ date "+%s" 
1488358945
richard@summersby:~$ ls -l "/home/richard/Pictures/Keepers/2012-07-04_Lotus and Cat Pod_P1060378_02.jpg.xmp" 
-rw-rw-r-- 1 richard richard 3533 Feb 28 18:18 /home/richard/Pictures/Keepers/2012-07-04_Lotus and Cat Pod_P1060378_02.jpg.xmp
richard@summersby:~$ sqlite3 ~/.config/darktable/library.db "select id, filename, version, max_version, write_timestamp from images where id = 814;" 
814|2012-07-04_Lotus and Cat Pod_P1060378.jpg|2|2|1488280725

#6 Updated by Tobias Ellinghaus over 2 years ago

Thanks, that shows that the XMP is newer than the timestamp in dt's database (1488280725 being Tue Feb 28 12:18:45 CET 2017). Please start dt, tell it to overwrite the XMP file, then immediately run the 3 lines from above again.
Btw, what time zone does your system clock run in? Maybe just add a 4th line "date" to the commands.

#7 Updated by Richard Wonka over 2 years ago

Thank you for your help.

system clock is indochina time (UTC+7)

richard@summersby:~$ date "+%s" 
1488389111
richard@summersby:~$ ls -l "/home/richard/Pictures/Keepers/2012-07-04_Lotus and Cat Pod_P1060378_02.jpg.xmp" 
-rw-rw-r-- 1 richard richard 3536 Mar  2 00:25 /home/richard/Pictures/Keepers/2012-07-04_Lotus and Cat Pod_P1060378_02.jpg.xmp
richard@summersby:~$ sqlite3 ~/.config/darktable/library.db "select id, filename, version, max_version, write_timestamp from images where id = 814;" 
814|2012-07-04_Lotus and Cat Pod_P1060378.jpg|2|2|1488280725
richard@summersby:~$ date
Thu Mar  2 00:25:16 ICT 2017

#8 Updated by Richard Wonka over 2 years ago

I started dt again, this time telling it to re-read the xmp files, closed dt and then re-ran the above commands.

Not sure if this is helpful.

here is the output:

richard@summersby:~$ date "+%s" 
1488389339
richard@summersby:~$ ls -l "/home/richard/Pictures/Keepers/2012-07-04_Lotus and Cat Pod_P1060378_02.jpg.xmp" 
-rw-rw-r-- 1 richard richard 3533 Mar  2 00:28 /home/richard/Pictures/Keepers/2012-07-04_Lotus and Cat Pod_P1060378_02.jpg.xmp
richard@summersby:~$ sqlite3 ~/.config/darktable/library.db "select id, filename, version, max_version, write_timestamp from images where id = 814;" 
814|2012-07-04_Lotus and Cat Pod_P1060378.jpg|2|2|1488389320
richard@summersby:~$ date
Thu Mar  2 00:29:03 ICT 2017

#9 Updated by Tobias Ellinghaus over 2 years ago

For some reason the timestamp in the database stayed old when re-writing the xmp. Re-reading updated it. Is that image still shown to have a changed XMP file now?

Are you able to compile darktable yourself?

#10 Updated by Richard Wonka over 2 years ago

I am still getting the same three pictures as updated, every time I start darktable.

I won't have the leisure to compile in the near future, sorry. I haven't done real geek stuff in a long time and need to get some work done. - Got presentations and a shoot coming up in a few days. :-)

Also available in: Atom PDF

Go to top