| Summary: | Some PEF/jpeg files not recognized as raw/non raw | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | Rinus Bakker <sleeplessregulus> |
| Component: | Metadata-Raw | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | major | CC: | caulier.gilles, sleeplessregulus |
| Priority: | NOR | ||
| Version: | 2.0.0 | ||
| Target Milestone: | --- | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | 7.0.0 | |
| Sentry Crash Report: | |||
| Attachments: | illustration of problem | ||
|
Description
Rinus Bakker
2011-05-07 19:14:58 UTC
Created attachment 59736 [details]
illustration of problem
No idea why these file are not parsed properlly. Perhaps something is broken with your Exiv2 install... Please attach me some files to test in local with my computer... Gilles Caulier After resizing the problem has gone, so I have to send the original but as I expected that failed. What should I do? Rinus Op 07-05-11 22:49, Gilles Caulier schreef: > https://bugs.kde.org/show_bug.cgi?id=272725 > > > Gilles Caulier<caulier.gilles@gmail.com> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > CC| |caulier.gilles@gmail.com > Component|Filters |Metadata > > > > > --- Comment #2 from Gilles Caulier<caulier gilles gmail com> 2011-05-07 22:49:38 --- > No idea why these file are not parsed properlly. Perhaps something is broken > with your Exiv2 install... > > Please attach me some files to test in local with my computer... > > Gilles Caulier > What digiKam said in the console when you import a new image in full size, and show with dumy dimension in incon view ? Gilles Caulier I did some tests. copying an affected file within dk passed te problems on to the copied image. After copy image outside dk the copy had not such issues. I concluded that the problem is a corrupte db and did reread metadata from file. This solved the issue. Probably no further action required. What do you think? Only problem. How becomes the db corrupted in a way the image properties assumed are incorrect while the info is correct in the metadata? Rinus Op 08-05-11 15:23, Gilles Caulier schreef: > https://bugs.kde.org/show_bug.cgi?id=272725 > > > > > > --- Comment #4 from Gilles Caulier<caulier gilles gmail com> 2011-05-08 15:23:00 --- > What digiKam said in the console when you import a new image in full size, and > show with dumy dimension in incon view ? > > Gilles Caulier > What about the file size (in bytes) entry in the right side bar? Is it 0 or correct? Does the problem go away after a restart (given "Scan at startup" is enabled)? There is the long-standing problem #233222 which is not trivial to fix perfectly. If not fixed by a restart, is it fixed by F5? Op 11-06-11 17:00, Marcel Wiesweg schreef: > https://bugs.kde.org/show_bug.cgi?id=272725 > > > > > > --- Comment #6 from Marcel Wiesweg<marcel wiesweg gmx de> 2011-06-11 17:00:48 --- > What about the file size (in bytes) entry in the right side bar? Is it 0 or yes 0 > correct? Does the problem go away after a restart (given "Scan at startup" is > enabled)? did not try fixed it by reread metadata from photo (is that F5? have no dk at hand at the moment) > There is the long-standing problem #233222 which is not trivial to fix > perfectly. > F5 will do less than Reread metadata, but it will certainly rescan zero size images. What is missing is to rescan partial files after they have reached their final size, but I did not find a cross-platform method to check if a file is currently written to, nor is there any form of notification. *** This bug has been marked as a duplicate of bug 233222 *** Not reproducible with digiKam 7.0.0-beta1. |