gwibber-service crashed with SIGSEGV in px_module_load()

[alelondon]

Binary package hint: gwibber

another random crash

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: gwibber-service 2.31.91-0ubuntu2
ProcVersionSignature: Ubuntu 2.6.35-19.28-generic 2.6.35.3
Uname: Linux 2.6.35-19-generic i686
NonfreeKernelModules: nvidia
Architecture: i386
CrashCounter: 1
Date: Sun Sep 5 14:07:42 2010
Disassembly: => 0xba6: Cannot access memory at address 0xba6
ExecutablePath: /usr/bin/gwibber-service
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Release Candidate i386 (20100419.1)
InterpreterPath: /usr/bin/python2.6
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/gwibber-service
ProcEnviron:
 PATH=(custom, user)
 LANG=en_GB.utf8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0xba6: Cannot access memory at address 0xba6
 PC (0x00000ba6) not located in a known VMA region (needed executable region)!
 Stack memory exhausted (SP below stack segment)
SegvReason: executing NULL VMA
Signal: 11
SourcePackage: gwibber
StacktraceTop:
 ?? ()
 px_module_load ()
 px_module_manager_load () from /usr/lib/libproxy.so.0
 px_module_manager_load_dir () from /usr/lib/libproxy.so.0
 px_proxy_factory_new () from /usr/lib/libproxy.so.0
Title: gwibber-service crashed with SIGSEGV in px_module_load()
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse libvirtd lpadmin netdev plugdev sambashare tape video

[Apport retracing service (apport)]

StacktraceTop:
 ?? ()
 px_module_manager_load (self=0x8b12990,
 px_module_manager_load_dir (self=0x8b12990,
 px_proxy_factory_new () at proxy.c:180
 ffi_call_SYSV ()

[Victor Vargas (kamus)]

aleondon, Please could you check if this behaviour is still affecting you under latest release of gwibber included in Ubuntu Maverick? Thanks

[Omer Akram (om26er)]

We'd like to figure out what's causing this bug for you, but we haven't heard back from you in a while. Could you please provide the requested information? 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. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. 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!