Red Hat Bugzilla – Bug 472439
Crash in libexempi when viewing certain image's EXIV properties
Last modified: 2009-01-23 21:35:13 EST
Created attachment 324231 [details]
Exiv data that upsets Nautilus
Description of problem:
Attempting to view the properties sheet of JPEG image files created with a Kodak EasyShare CD43 camera causes nautilus to restart. In fact, it seems to be the exiv data that's the trouble: extracting it with exiv2 and inserting it into any other JPEG image also provokes the problem. An example .exv file is attached.
Note that exiftool and exiv2 behave OK with these images.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Insert attached exiv data into a JPEG using exiv2.
2. Attempt to view its properties sheet.
Nautilus restarts. Can't find any evidence of a core dump.
nautilus-2.24.1-3.fc10.i386 is not affected by this issue, so it would be nice to see the fix backported.
This has shown up in nautilus-2.24.2-1.fc10.x86_64. Make the following file as exiv2.txt:
# exiv2 -m exiv2.txt *.JPG
set Exif.Image.Make "Pentax"
set Exif.Image.Model "Pentax P30N"
set Exif.Image.Orientation 0
set Exif.Image.XResolution 600/1
set Exif.Image.YResolution 600/1
set Exif.Image.ResolutionUnit 1
set Exif.Photo.ExposureProgram 1
set Exif.Photo.ISOSpeedRatings 400
set Exif.Photo.ExposureBiasValue 0/3
set Exif.Photo.Flash 1
and apply it to a JPEG using
exiv2 -m exiv2.txt mypicture.jpeg
For me, JPEGs thus treated cause nautilus to restart when viewing their properties (although it's not always 100% reproducible and I don't know what precise set of tags triggers it).
Created attachment 328013 [details]
gdb session provoking the crash
I've found out it's a segfault in libexempi. The attached gdb log contains a backtrace. I've also attached below the image blank-crasher.jpeg I crafted to get this fault.
Created attachment 328014 [details]
Example image that crashes nautilus
Created attachment 328015 [details]
More detailed gdb transcript
I can confirm that this is, in fact, an exempi bug. So far, I don't see the problem when using the upstream exempi 2.1.0, built by dropping the original sources into the SRPM for exempi 2.0.1.
exempi-2.1.0-1.fc10 has been submitted as an update for Fedora 10.
exempi-2.1.0-1.fc10 has been pushed to the Fedora 10 testing repository. If problems still persist, please make note of it in this bug report.
If you want to test the update, you can install it with
su -c 'yum --enablerepo=updates-testing update exempi'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F10/FEDORA-2009-0251
exempi-2.1.0-1.fc10 has been pushed to the Fedora 10 stable repository. If problems still persist, please make note of it in this bug report.