shotwell crashed with SIGSEGV in gexiv2_metadata_get_orientation()

[David Dando]

Binary package hint: shotwell

The crash happened while the screen was locked.

TEST CASE:
1. install gexiv2 from maverick-proposed
2. import/open images in shotwell
3. see shotwell works fine

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: shotwell 0.7.1-0ubuntu2
ProcVersionSignature: Ubuntu 2.6.35-20.29-generic 2.6.35.4
Uname: Linux 2.6.35-20-generic i686
NonfreeKernelModules: nvidia
Architecture: i386
Date: Sun Sep 12 13:28:46 2010
ExecutablePath: /usr/bin/shotwell
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
ProcCmdline: shotwell
ProcEnviron:
 LANG=en_AU.utf8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x1ec0a1: movzwl (%eax,%edx,2),%eax
 PC (0x001ec0a1) ok
 source "(%eax,%edx,2)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: shotwell
StacktraceTop:
 ?? () from /usr/lib/libexiv2.so.6
 gexiv2_metadata_get_orientation () from /usr/lib/libgexiv2.so.0
 photo_metadata_get_orientation ()
 transformable_photo_prepare_for_import ()
 ?? ()
Title: shotwell crashed with SIGSEGV in gexiv2_metadata_get_orientation()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Omer Akram (om26er)]

seems like the crash was in libexiv

[Jim Nelson (yorba-jim)]

This is fixed in gexiv 0.2.1.

[Omer Akram (om26er)]

Jim, gexiv2 0.2.1 was it a bug fix release? i mean is it safe for ubuntu to backport it?

[Jim Nelson (yorba-jim)]

Pure bug fix. The only change (other than versioning and packaging) was for this bug. Here's the key diff: http://trac.yorba.org/changeset/2219/gexiv2/trunk

We've had 2 - 3 people in the past few weeks report this bug. I would recommend taking it.

[Jim Nelson (yorba-jim)]

I should also add that this fix solves this particular problem only. A more general solution has been committed to trunk and will be available in the next release of gexiv2. I would consider taking that as well, since this bug can bite users in other ways as well.

[Omer Akram (om26er)]

the only change in the new upstream release is a fix for this bug and is recommended by the upstream developers.

[Martin Pitt (pitti)]

Looks fine, please get it uploaded. Thanks!

[Omer Akram (om26er)]

updated so that it does not update the upstream version.

[Michael Vogt (mvo)]

I uploaded the maverick-proposed branch now, removing ubuntu-sposnors now as the sponsoring is done.

[Omer Akram (om26er)]

gexiv 0.2.1 is already in natty so marking as fix released.

[Omer Akram (om26er)]

have been using the proposed version of gexiv2 in maverick. no regressions found or reported

[Omer Akram (om26er)]

the proposed version fixes this issue as someone in the duplicate reliably faced the crash and proposed version of gexiv2 fixed the issue.

[Launchpad Janitor (janitor)]

This bug was fixed in the package gexiv2 - 0.2.0-0ubuntu2.1

---------------
gexiv2 (0.2.0-0ubuntu2.1) maverick-proposed; urgency=low

  * debian/patches/do_not_crash_when_importing_images.patch:
    - do not crash when importing files with zero size
      ExifImage.Orientation field (LP: #636161)
 -- Omer Akram <email address hidden> Sat, 20 Nov 2010 15:15:16 +0500