Bug 256776 - Digikam leaves ".digikam-exifrotate" files etc. on harddisk
Summary: Digikam leaves ".digikam-exifrotate" files etc. on harddisk
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Import-PostProcessing (show other bugs)
Version: 2.0.0
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-11-13 10:02 UTC by wuselwu
Modified: 2017-08-16 05:55 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In: 2.1.0
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description wuselwu 2010-11-13 10:02:04 UTC
Version:           1.5.0 (using KDE 4.5.3) 
OS:                Linux

I don't know under which circumstances this happens, but while using digikam intensively for my photo management, sooner or later in some picture drawers stale hidden files named ".digikam-exitrote*", sometimes ".digikam.xml.bak", appear. 
(Maybe this is the result of some program crash at the wrong time, I can't reproduce it. However, as digikam runs rather stable, I doubt that.)
Proposal: It would be great if digikam would clean up such temporary files the next time it  encounters them when scanning folders etc.

Reproducible: Didn't try
Comment 1 wuselwu 2011-03-25 07:14:03 UTC
Problem still persists with current beta versions of Digikam2. However, I cannot find a way to reproduce it, it simply happens from time to time.
Comment 2 caulier.gilles 2011-03-25 08:24:27 UTC
This file is create when Exif orientation tag is used to rotate JPEG image automatically. It appear with :

- Camera interface during download,
- Batch Queue Manager rotate tool.
- Album interface, when right image option is used.

Typically, code source relevant is there :

https://projects.kde.org/projects/extragear/graphics/digikam/repository/revisions/master/entry/libs/jpegutils/jpegutils.cpp#L311

And sound like something is wrong here :

https://projects.kde.org/projects/extragear/graphics/digikam/repository/revisions/master/entry/libs/jpegutils/jpegutils.cpp#L484

... it miss "unlink(out);" before to return false...

Gilles Caulier
Comment 3 Marcel Wiesweg 2011-05-23 21:05:58 UTC
Git commit dd76b93b523044b8d792efce88e001809ca024e8 by Marcel Wiesweg.
Committed on 23/05/2011 at 21:05.
Pushed by mwiesweg into branch 'master'.

Unlink the temp file on error.

CCBUG: 256776

M  +1    -0    libs/jpegutils/jpegutils.cpp     

http://commits.kde.org/digikam/dd76b93b523044b8d792efce88e001809ca024e8
Comment 4 Marcel Wiesweg 2011-05-23 21:06:33 UTC
Any idea where the digikam.xml.bak file is coming from? Any kipi plugin?
Comment 5 caulier.gilles 2011-05-23 21:12:37 UTC
Marcel,

Perhaps Exiv2, but i doubt.

No kipi-plugins manage XMP files yet (still in my todo list), excepted perhaps GPSSync 2.0 where i remember Michael questions about when i started to implement sidecar support...

Gilles
Comment 6 caulier.gilles 2011-05-23 21:17:42 UTC
Oups sorry Marcel : XML != XMP

This digikam.xml file come from an old 0.6.x version where DB have not yet been implemented. 

After 0.7.x (if i remember), this storage have been replaced by Sqlite...

Gilles
Comment 7 caulier.gilles 2011-08-04 14:12:45 UTC
Tested with 2.x. Not reproducible. temp files are removed...

Gilles Caulier