gwibber crashed with SIGSEGV in PyObject_SetAttrString()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gwibber (Ubuntu) |
Invalid
|
Medium
|
Unassigned |
Bug Description
Binary package hint: gwibber
Gwibber won't start
ProblemType: Crash
Architecture: amd64
CrashCounter: 1
Date: Sun Oct 18 08:48:00 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/gwibber
InterpreterPath: /usr/bin/python2.6
NonfreeKernelMo
Package: gwibber 2.0.0~bzr466-
PackageArchitec
ProcCmdline: /usr/bin/python /usr/bin/gwibber
ProcEnviron:
SHELL=/bin/bash
LANG=en_US.UTF-8
ProcVersionSign
SegvAnalysis:
Segfault happened at: 0x45186e <PyObject_
PC (0x0045186e) ok
source "0x8(%rdi)" (0x00000008) not located in a known VMA region (needed readable region)!
destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gwibber
StacktraceTop:
PyObject_
?? ()
?? ()
PyEval_EvalFrameEx ()
PyEval_EvalCodeEx ()
Title: gwibber crashed with SIGSEGV in PyObject_
Uname: Linux 2.6.31-9-rt x86_64
UserGroups: adm admin audio cdrom dialout dip fax fuse plugdev tape video
visibility: | private → public |
StacktraceTop: PyObject_ SetAttrString (v=0x0, name=0x7f23c6f5b4f8 "_dbus_error_name",
?? ()
?? ()
PyEval_EvalFrameEx (f=0x2c2b210,
PyEval_EvalCodeEx (co=0x7f23c6cc8c60,