Bug 247108

Summary: digikam: setting file date/time stamp refused, with umlauts or prior file movements
Product: [Applications] digikam Reporter: Michael <mifireg>
Component: Plugin-Generic-TimeAdjustAssignee: Digikam Developers <digikam-bugs-null>
Status: RESOLVED FIXED    
Severity: normal CC: caulier.gilles, karol.slanina, r.biegel
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed In: 3.1.0
Sentry Crash Report:

Description Michael 2010-08-09 04:26:42 UTC
Version:           1.2.0 (using KDE 4.4.5) 
OS:                Linux

When adapting the "file change date" among other metadata (or without changing the other metadata at least) (adding 1 hour, or setting file-date = digikam-date) by Menu->Picture->Chance Date/Time it happened in some folders, that a information-window appeared, saying: No change of timestamp possible. Unfortunately without naming the reason or specific error message (due to access rights - whatsoever).

I suppose one of two possible reasons:
1. If the albums name (not the file's name) has umlauts (ä,ö,ü), then the timestamp change will fail. When I changed the albums names into one without umlauts it worked.

2. Prior to the change command, I started digicam, moved some folders (=albums) into the digicam aware "Bilder"-Directory and then started the operation in some of the moved and some of the older unmoved directories. Maybe only in the cases, where a prior movement has taken place, the timestamp change fails.

The stdout output says:
mf@hai:~/Bilder$ digikam(9047)/digikam (core): Got wrong change event for index with row  -1 , column  -1  and parent  QModelIndex(-1,-1,0x0,QObject(0x0) )  in model  Digikam::AbstractCheckableAlbumModel(0x2afece0) . Ignoring it. 
digikam(9047)/digikam (core): Got wrong change event for index with row  -1 , column  -1  and parent  QModelIndex(-1,-1,0x0,QObject(0x0) )  in model  Digikam::AbstractCheckableAlbumModel(0x2aff770) . Ignoring it. 
digikam(9047)/digikam (core): Got wrong change event for index with row  -1 , column  -1  and parent  QModelIndex(-1,-1,0x0,QObject(0x0) )  in model  Digikam::AbstractCheckableAlbumModel(0x37550e0) . Ignoring it. 
digikam(9047)/digikam (core) Digikam::CollectionScanner::scanAlbum: Folder does not exist or is not readable:  "/home/mf/Bilder/Geburtstag/DSC_1508.JPG" 

But maybe that's another error message from something else.


Reproducible: Didn't try

Steps to Reproduce:
Have digikam aware directory and other directory containing pictures.
start digikam, so watching of the digikam aware directory starts
move folder into digicam aware directory
try to change metadata timestamp by adding 1 hour based on digcam-internal-timestamp. As result, the creation date and the change date should differ by 1 hour.
Then try to change only the last change date to 0 hours based on the digkam-internal-date.
(maybe you can skip the last steps by only changing the picture file change date)
then error message shall occur.
Removing the umlauts or having digikam started after movements of folders should avoid the problem.

Try this for folder with umlauts and without.




OS: Linux (x86_64) release 2.6.32-24-generic
Compiler: cc
Comment 1 Marcel Wiesweg 2011-01-26 14:12:52 UTC
I can confirm the error message with the Time Adjust Kipi plugin. Nonetheless, changing the time in database and file metadata seems to have succeeded.
Comment 2 Reinhard Biegel 2011-04-15 15:29:41 UTC
I can confirm the bug too. Did a strace on digikam, which shows that the filename used at (successful) filesystem calls is e.g.
"/home/rbiegel/Bilder/Sound Adventure/B\303\274hnen\303\274berdachung/Bild0091.jpg"
But the filename provided to the utime call is:
"/home/rbiegel/Bilder/Sound Adventure/B\374hnen\374berdachung/Bild0091.jpg"
Note the two missing \303
utime returns: -1 ENOENT (No such file or directory)
Comment 3 caulier.gilles 2011-12-20 10:51:26 UTC
Michael,

This file still valid using kipi-plugins 2.4 ?

Gilles Caulier
Comment 4 Karol Slanina 2013-02-16 23:48:01 UTC
I believe that this is a duplicate of https://bugs.kde.org/show_bug.cgi?id=308465 and that is has been solved in v3.0.0.
Comment 5 caulier.gilles 2013-02-17 08:04:55 UTC
Right Karol.

This file have been fixed in 3.0.0

Gilles Caulier