bzr-notify crashed with SIGSEGV in g_type_get_qdata()

Bug #926837 reported by NamelessOne on 2012-02-04
This bug affects 1 person
Affects Status Importance Assigned to Milestone
bzr-gtk (Ubuntu)

Bug Description

bzr-notify crashed with SIGSEGV

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: bzr-gtk 0.103.0+bzr769-1
ProcVersionSignature: Ubuntu 3.2.0-12.21-generic 3.2.2
Uname: Linux 3.2.0-12-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.91-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Sat Feb 4 22:45:46 2012
ExecutablePath: /usr/bin/bzr-notify
ExecutableTimestamp: 1324481098
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/bzr-notify
ProcCwd: /home/serge
 PATH=(custom, no user)
 Segfault happened at: 0x7f3f9211359b <_IO_vfprintf_internal+155>: callq 0x7f3f9215bc80 <strchrnul>
 PC (0x7f3f9211359b) ok
 source "0x7f3f9215bc80" (0x7f3f9215bc80) ok
 destination "(%rsp)" (0x7fff37bb7fa0) 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
 g_type_get_qdata (type=<optimized out>, quark=55) at /build/buildd/glib2.0-2.31.14/./gobject/gtype.c:3681
 pygobject_lookup_class (gtype=0) at /build/buildd/pygobject-2-2.28.6/gobject/pygobject.c:905
 pygobject_lookup_class (gtype=0) at /build/buildd/pygobject-2-2.28.6/gobject/pygobject.c:894
 pyg_type_get_bases (gtype=0) at /build/buildd/pygobject-2-2.28.6/gobject/pygobject.c:659
 pygobject_new_with_interfaces (gtype=0) at /build/buildd/pygobject-2-2.28.6/gobject/pygobject.c:702
Title: bzr-notify crashed with SIGSEGV in g_type_get_qdata()
UpgradeStatus: Upgraded to precise on 2012-01-27 (8 days ago)
UserGroups: adm admin cdrom dialout fuse lpadmin plugdev powerdev sambashare scanner vboxusers

NamelessOne (frure-8) wrote :

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  Edit
Everyone can see this information.

Other bug subscribers