bzr-notify crashed with SIGSEGV in g_type_get_qdata()

Bug #939422 reported by Andy Whitcroft
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
bzr-gtk (Ubuntu)
New
Undecided
Unassigned

Bug Description

Unsolicited crash report following reboot.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: bzr-gtk 0.103.0+bzr769-1
ProcVersionSignature: Ubuntu 3.2.0-17.26-generic 3.2.6
Uname: Linux 3.2.0-17-generic x86_64
ApportVersion: 1.92-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Thu Feb 23 11:19:42 2012
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/bzr-notify
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/bzr-notify
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7fc908e7274b <vfprintf+155>: callq 0x7fc908ebba50 <strchrnul>
 PC (0x7fc908e7274b) ok
 source "0x7fc908ebba50" (0x7fc908ebba50) ok
 destination "(%rsp)" (0x7fffc09faf70) 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-01 (21 days ago)
UserGroups: adm admin audio cdrom dialout dip floppy fuse libvirtd lpadmin plugdev sambashare sbuild video voice

Revision history for this message
Andy Whitcroft (apw) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

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.

visibility: private → public
visibility: private → public
tags: removed: need-amd64-retrace
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.