shotwell crashed with SIGSEGV in g_strcmp0()

[spektakel]

Crashes while authenticating with flickr.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: shotwell 0.11.91-0ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-9.16-generic 3.2.1
Uname: Linux 3.2.0-9-generic i686
ApportVersion: 1.91-0ubuntu1
Architecture: i386
CrashCounter: 1
Date: Tue Feb 14 00:11:54 2012
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/shotwell
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha i386 (20111129.1)
ProcCmdline: shotwell
ProcEnviron:
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x42be41b: cmp %cl,(%edx)
 PC (0x042be41b) ok
 source "%cl" ok
 destination "(%edx)" (0x00000049) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: shotwell
StacktraceTop:
 ?? () from /lib/i386-linux-gnu/libc.so.6
 g_strcmp0 () from /lib/i386-linux-gnu/libglib-2.0.so.0
 publishing_rest_support_argument_compare () from /usr/lib/shotwell/plugins/builtin/shotwell-publishing.so
 ?? () from /lib/i386-linux-gnu/libc.so.6
 qsort_r () from /lib/i386-linux-gnu/libc.so.6
Title: shotwell crashed with SIGSEGV in g_strcmp0()
UpgradeStatus: Upgraded to precise on 2012-01-18 (26 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[Apport retracing service (apport)]

StacktraceTop:
 g_strcmp0 (str1=0x49 <Address 0x49 out of bounds>, str2=0x4325470 "\350\376\315\tX\224\315\t\310\222\315\tH\223\315\txT2\004xT2\004\200T2\004\200T2\004\210T2\004\210T2\004\220T2\004\220T2\004\230T2\004\230T2\004\240T2\004\240T2\004\250T2\004\250T2\004\260T2\004\260T2\004\270T2\004\270T2\004H\222\315\tH\222\315\t\310T2\004\310T2\004\320T2\004\320T2\004\330T2\004\330T2\004\340T2\004\340T2\004\350T2\004\350T2\004\360T2\004\360T2\004\370T2\004\370T2\004") at /build/buildd/glib2.0-2.31.16/./glib/gtestutils.c:1975
 publishing_rest_support_argument_compare () from /tmp/tmp_yqi2Y/usr/lib/shotwell/plugins/builtin/shotwell-publishing.so
 msort_with_tmp (p=0xbfd1c3bc, b=0x9cb6940, n=2) at msort.c:66
 msort_with_tmp (n=2, b=0x9cb6940, p=0xbfd1c3bc) at msort.c:46
 __GI_qsort_r (b=0x9cb6940, n=2, s=4, cmp=0x668523a <publishing_rest_support_argument_compare>, arg=0x0) at msort.c:298

[Laura Khalil (loura)]

Hi,

This is a known issue and has been reported upstream:

http://redmine.yorba.org/issues/4545

We are working to fix this bug for the next release of Shotwell. Please follow the bug report on Redmine to stay updated on its status.