bzr-notify crashed with SIGSEGV in g_type_get_qdata()

[Vincent Ladeuil]

Happens after boot. I'm a bit surprised it's not seen as a dupe as I encounter this semi-regularly and I'm pretty sure I've already reported it.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: bzr-gtk 0.103.0+bzr769-1
ProcVersionSignature: Ubuntu 3.2.0-15.24-generic 3.2.5
Uname: Linux 3.2.0-15-generic x86_64
NonfreeKernelModules: nvidia wl
ApportVersion: 1.91-0ubuntu1
Architecture: amd64
CheckboxSubmission: 34f5a9de644359b1b8e0705e7e99fd74
CheckboxSystem: 7e42599bda39ea7ff8b528272b6ef52b
CrashCounter: 1
Date: Mon Feb 13 08:54:18 2012
ExecutablePath: /usr/bin/bzr-notify
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/bzr-notify
SegvAnalysis:
 Segfault happened at: 0x7fb11b29d74b <vfprintf+155>: callq 0x7fb11b2e6a50 <strchrnul>
 PC (0x7fb11b29d74b) ok
 source "0x7fb11b2e6a50" (0x7fb11b2e6a50) ok
 destination "(%rsp)" (0x7fff1cdab000) not located in a known VMA region (needed writable region)!
 Stack memory exhausted (SP below stack segment)
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: bzr-gtk
StacktraceTop:
 g_type_get_qdata () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/python2.7/dist-packages/gobject/_gobject.so
 ?? () from /usr/lib/python2.7/dist-packages/gobject/_gobject.so
 ?? () from /usr/lib/python2.7/dist-packages/gobject/_gobject.so
 ?? () from /usr/lib/python2.7/dist-packages/gobject/_gobject.so
Title: bzr-notify crashed with SIGSEGV in g_type_get_qdata()
UpgradeStatus: Upgraded to precise on 2012-02-13 (0 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare wireshark

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #903444, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.