Bug 240945 - Picture size does not report correctly after gimp
Summary: Picture size does not report correctly after gimp
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Database-Thumbs (show other bugs)
Version: 1.2.0
Platform: Ubuntu Linux
: NOR minor
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-06-06 21:46 UTC by Alexandre Racine
Modified: 2018-09-02 15:18 UTC (History)
1 user (show)

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


Attachments
Image Size incorrect (131.32 KB, image/jpeg)
2010-06-06 21:46 UTC, Alexandre Racine
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Alexandre Racine 2010-06-06 21:46:14 UTC
Created attachment 47753 [details]
Image Size incorrect

Version:           1.2.0 (using KDE 4.4.2) 
OS:                Linux

When editing some images in the Gimp, saving those images, I look at digiKam, and the file size in Digikam is not correct. See attached file. You can clearly see that the IMG_3539-diff1.JPG file size is not correct in Digikam.

Reproducible: Sometimes

Steps to Reproduce:
-Open Digikam
-Edit a picture with - right clic - open with - The Gimp
-In the gimp, save the picture
-Back in Digikam, the picture has an incorrect file size

Actual Results:  
-Correct file size
-Refresh should refresh that data too. (F5 or refresh)

Expected Results:  
-Have the correct picture size
-At least make F5 (refresh) reinitialize that data :)

OS: Linux (x86_64) release 2.6.32-22-generic
Compiler: cc
Comment 1 Marcel Wiesweg 2010-06-07 18:34:42 UTC
I have recently fixed the problem that sometimes the file scan can kick in too early, when the file is yet being written. This case seems very difficult to detect properly. Anyway, 1.3.0 will rescan (including F5) when the file size changed.
Comment 2 Andi Clemens 2010-07-17 13:14:14 UTC
Marcel, so this bug is fixed?
Then we should mark it as FIXED, to reduce the bug count (like we discussed on the mailinglist).
Users can VERIFY a bug (if they want to) or REOPEN it when it is definitely not fixed for them.

I would suggest to add the revision from now on when the bug has been fixed.

Andi
Comment 3 Marcel Wiesweg 2010-07-29 10:37:43 UTC
There is still some automatic check for wrong file size missing, but I'm not sure if there's a good way to achieve that. Anyway, we can merge with the older discussion (symptoms there are quite different)

*** This bug has been marked as a duplicate of bug 233222 ***
Comment 4 Alexandre Racine 2010-10-20 02:43:02 UTC
I am now using 1.4 and this still occurs. So I'll continue in the bug #233222.