gwibber crashed with SIGSEGV in PyObject_SetAttrString()

[hanzomon4]

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
NonfreeKernelModules: nvidia
Package: gwibber 2.0.0~bzr466-0ubuntu1
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/gwibber
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-9.152-rt
SegvAnalysis:
 Segfault happened at: 0x45186e <PyObject_SetAttrString+14>: mov 0x8(%rdi),%rax
 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_SetAttrString ()
 ?? ()
 ?? ()
 PyEval_EvalFrameEx ()
 PyEval_EvalCodeEx ()
Title: gwibber crashed with SIGSEGV in PyObject_SetAttrString()
Uname: Linux 2.6.31-9-rt x86_64
UserGroups: adm admin audio cdrom dialout dip fax fuse plugdev tape video

[Apport retracing service (apport)]

StacktraceTop:PyObject_SetAttrString (v=0x0, name=0x7f23c6f5b4f8 "_dbus_error_name",
?? ()
?? ()
PyEval_EvalFrameEx (f=0x2c2b210,
PyEval_EvalCodeEx (co=0x7f23c6cc8c60,

[Victor Vargas (kamus)]

Can you try to reproduce this issue in latest version of gwibber? Thanks!

[Victor Vargas (kamus)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!