bzr-notify crashed with SIGSEGV in g_type_get_qdata()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar GTK+ Frontends |
New
|
Undecided
|
Unassigned | ||
bzr-gtk (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
This might be a duplicate of bug 903444, but I see a stack trace that is not described in that bug. bzr-gtk tip should not be importing any gtk2.
/usr/lib/
import gobject._gobject
** WARNING **: Trying to register gtype 'GMountMountFlags' as enum when in fact it is of type 'GFlags'
** WARNING **: Trying to register gtype 'GDriveStartFlags' as enum when in fact it is of type 'GFlags'
/usr/lib/
from gtk import _gtk
/usr/lib/
from gtk import _gtk
Segmentation fault (core dumped)
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: bzr-gtk 0.103.0+bzr769-1
ProcVersionSign
Uname: Linux 3.2.0-12-generic x86_64
NonfreeKernelMo
ApportVersion: 1.91-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Fri Feb 3 10:08:41 2012
ExecutablePath: /usr/bin/bzr-notify
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
InterpreterPath: /usr/bin/python2.7
PackageArchitec
ProcCmdline: /usr/bin/python /usr/bin/bzr-notify
SegvAnalysis:
Segfault happened at: 0x7fac76a1959b <vfprintf+155>: callq 0x7fac76a61c80 <strchrnul>
PC (0x7fac76a1959b) ok
source "0x7fac76a61c80" (0x7fac76a61c80) ok
destination "(%rsp)" (0x7fffe933efb0) 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/
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
Title: bzr-notify crashed with SIGSEGV in g_type_get_qdata()
UpgradeStatus: Upgraded to precise on 2012-02-03 (0 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
Changed in bzr-gtk (Ubuntu): | |
status: | New → In Progress |
assignee: | nobody → Curtis Hovey (sinzui) |
assignee: | Curtis Hovey (sinzui) → nobody |
status: | In Progress → Confirmed |
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.