bzr-notify crashed with SIGSEGV in g_return_if_fail_warning()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
bzr-gtk (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
fails on login to precise
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: bzr-gtk 0.103.0+bzr769-1
ProcVersionSign
Uname: Linux 3.2.0-16-generic i686
ApportVersion: 1.91-0ubuntu1
Architecture: i386
Date: Sun Feb 19 23:08:06 2012
DistributionCha
# This is a distribution channel descriptor
# For more information see http://
canonical-
ExecutablePath: /usr/bin/bzr-notify
InstallationMedia: Ubuntu 10.04 "Lucid" - Build i386 LIVE Binary 20100427-14:29
InterpreterPath: /usr/bin/python2.7
PackageArchitec
ProcCmdline: /usr/bin/python /usr/bin/bzr-notify
ProcEnviron:
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x8be8a4 <_IO_vfprintf_
PC (0x008be8a4) ok
source "0x8fb3e0" (0x008fb3e0) ok
destination "(%esp)" (0xbf2bd000) 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_return_
g_type_get_qdata () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
Title: bzr-notify crashed with SIGSEGV in g_return_
UpgradeStatus: Upgraded to precise on 2012-02-18 (1 days ago)
UserGroups: adm admin cdrom dialout disk lpadmin plugdev sambashare vboxusers
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 #903696, 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.