| Summary: | Crash in image editor when moving to the next image | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | Alex G <gforce> |
| Component: | DImg-Processing | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | crash | CC: | caulier.gilles, liviux, webmaster |
| Priority: | NOR | ||
| Version: | 3.1.0 | ||
| Target Milestone: | --- | ||
| Platform: | Compiled Sources | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | 4.0.0 | |
| Sentry Crash Report: | |||
| Attachments: |
EXIF data of a photo crashing Digikam's editor
Metadata extracted with exiv2 |
||
|
Description
Alex G
2012-12-28 00:10:28 UTC
It crash in DImg::rotate() code, probably about Exif autorotation at loading. Can you identify which file crash digiKam in this case and check if it's always reproducible. If yes, please provide file for download on the web. Gilles Caulier Created attachment 78396 [details] EXIF data of a photo crashing Digikam's editor Generated with: exiftool /home/liviux/Documenti/Immagini/foto/Pentax/2013/IMGP7796.JPG > DigikamCrashExif.txt Original 7.8 MB file at http://dl.dropbox.com/u/30331506/IMGP7796.JPG I found the editor crashes consistently when moving to the next image, if it is vertical. Even without performing any edit and without saving the current image. I did just open the editor with F4, then moved to the next image. All is well as long as the photos are horizontal, but loading the first vertical one invariably crashes the application. This happens both using the on-screen arrows and moving with the spacebar. If exif metadata are the problem, try to use Exiv2 command line tool to read metadata and see if it crash. LibExiv2 is used by digiKam in background to manage Exif, Iptc and XMP... Gilles Caulier Created attachment 78399 [details]
Metadata extracted with exiv2
exiv2 worked regularly on the "problem" file
Exiv worked flawlessly, just like Digikam reads EXIF metadata in general. I forgot to mention that the same file can be selected in the main window and opened for editing with F4 without any problem. Only moving to another photo while in the editor causes the crash. I also forgot some basic information: Application: digikam (2.8.0) KDE Platform Version: 4.9.5 Qt Version: 4.8.3 Operating System: Linux 3.5.0-26-generic i686 Distribution: Ubuntu 12.10 *** Bug 317990 has been marked as a duplicate of this bug. *** digiKam 3.5.0 is out. Can you give a fresh feedback about your report ? Crash still reproducible ? Thanks in advance Gilles Caulier The crash can't be reproduced in the latest 3.4 version (on Kubuntu 13.10 32 bit), simply because the ability to move from one photo to the next has been disabled in the editor, apparently. While this prevents undesirable crashes, it's hard to think of it as a "solution". In my workflow, working with many shots at a time, I used to open the editor and perform quick corrections (or deletions) moving forward with the spacebar and confirming changes with the same key. It was a very efficient way to "fix" many photos in a short time, and I miss it very much since this bug appeared. Please, put back the "forward/back" functionality in Digikam Editor! I'll do anything I can to help pinpoint the causes of this problem. Thank you. Livio I compiled Digikam 3.5 (not yet in the Ubuntu repositories) and can see that even in this version the user can't move from one image to another in the editor. Should I open a new request in order to get back this fundamental feature? Livio, Nothing has changed in digiKam 3.5.0. You can of course switch to another image through thumbbar as digiKam 3.1.0 (there is no reason to remove this feature)... Please check better again... Gilles Caulier Sorry, it was not clear to me that the thumbbar in the editor shows only the photos already selected in the main window. I opened the editor with "F4" and its thumbbar showed only one image, thus making impossible to move back and forward! Now I tried selecting all the photos in the folder before opening the editor: Ctrl+A, F4, Space, and when I got to the photo that caused the problem it opened flawlessly! Then I tried editing the previous one, pressing Space to move forward, Space again when prompted for saving, and again no crash opening the infamous IMGP7796.JPG Seems like the bug is gone. Thank you a lot! |
