shotwell crashed with SIGSEGV in photo_source_get_dimensions()

[Roland Dreier]

Binary package hint: shotwell

After looking at pictures for a while, shotwell crashes and generates this huge core dump. Not sure what in particular provokes this...

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: shotwell 0.6.1-1ubuntu1
ProcVersionSignature: Ubuntu 2.6.35-8.13-generic 2.6.35-rc5
Uname: Linux 2.6.35-8-generic x86_64
Architecture: amd64
CrashCounter: 1
Date: Sun Jul 18 21:13:01 2010
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/shotwell
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100318)
ProcCmdline: shotwell
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.utf8
SegvAnalysis:
 Segfault happened at: 0x501c50 <photo_source_get_dimensions>: mov (%rdi),%rax
 PC (0x00501c50) ok
 source "(%rdi)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: shotwell
StacktraceTop:
 photo_source_get_dimensions ()
 ?? ()
 ?? ()
 ?? () from /lib/libglib-2.0.so.0
 g_main_context_dispatch ()
Title: shotwell crashed with SIGSEGV in photo_source_get_dimensions()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors: (polkit-gnome-authentication-agent-1:2118): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed

[Apport retracing service (apport)]

StacktraceTop:
 photo_source_get_dimensions (self=0x0, result=0x7fff5fe81540)
 editing_host_page_update_pixbuf (self=0x2c84380)
 _page_check_configure_halted_gsource_func (
 g_timeout_dispatch (source=0x3d1dd80,
 g_main_context_dispatch (context=0xdbeff0)

[Omer Akram (om26er)]

Thanks for the bug report. Could you please check if this is still an issue with Shotwell 0.7.1-0ubuntu2 ?

[Omer Akram (om26er)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a backtrace following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.

[Jim Nelson (yorba-jim)]

The Apport tracing service suggests to me this was fixed in 0.7: http://trac.yorba.org/ticket/2343

I highly recommend the user upgrade.

[Omer Akram (om26er)]

marking this bug as fixed as there has been no duplicates and as Jim suggested the issue should be fixed in shotwell 0.7