gwibber is a poorly-designed, useless pile of SIGSEGV

[Tom Webb]

Binary package hint: gwibber

3) To be able to add a Facebook account
4) I couldn't.

I had to try restarting gwibber in order to make it work, but it never did. It DID crash, though. :-)

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: gwibber-service 2.31.92-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.35-20.29-generic 2.6.35.4
Uname: Linux 2.6.35-20-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Sat Sep 11 16:00:18 2010
ExecutablePath: /usr/bin/gwibber-service
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Beta amd64 (20100901.1)
InterpreterPath: /usr/bin/python2.6
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/gwibber-service
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.utf8
SegvAnalysis:
 Segfault happened at: 0x7fce1904dc2d <free+29>: mov -0x8(%rdi),%rsi
 PC (0x7fce1904dc2d) ok
 source "-0x8(%rdi)" (0x04019018) not located in a known VMA region (needed readable region)!
 destination "%rsi" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gwibber
StacktraceTop:
 free () from /lib/libc.so.6
 ffi_call_unix64 () from /usr/lib/python2.6/lib-dynload/_ctypes.so
 ffi_call () from /usr/lib/python2.6/lib-dynload/_ctypes.so
 _CallProc () from /usr/lib/python2.6/lib-dynload/_ctypes.so
 ?? () from /usr/lib/python2.6/lib-dynload/_ctypes.so
Title: gwibber-service crashed with SIGSEGV in free()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

StacktraceTop:
 *__GI___libc_free (mem=0x4019020) at malloc.c:3709
 ffi_call_unix64 ()
 ffi_call ()
 _CallProc (pProc=<value optimized out>,
 CFuncPtr_call (self=0x2304870, inargs=0x241a750,

[Victor Vargas (kamus)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 631147, so it 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. Feel free to continue to report any other bugs you may find.