gwibber-service crashed with SIGSEGV in pthread_mutex_lock()

[lakiu]

Binary package hint: gwibber

It suddenly crashes with no action on user side, and doesn't refresh the streams after that anymore.

gwibber:
  Installed: 2.31.90-0ubuntu1
  Candidate: 2.31.90-0ubuntu1
  Version table:
 *** 2.31.90-0ubuntu1 0
        500 http://archive.ubuntu.com/ubuntu/ maverick/main amd64 Packages
        100 /var/lib/dpkg/status

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: gwibber-service 2.31.90-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.35-19.28-generic 2.6.35.3
Uname: Linux 2.6.35-19-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
CrashCounter: 1
Date: Tue Aug 31 10:22:05 2010
ExecutablePath: /usr/bin/gwibber-service
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha amd64 (20100825)
InterpreterPath: /usr/bin/python2.6
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/gwibber-service
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7ff6c1d8e634 <pthread_mutex_lock+4>: mov 0x10(%rdi),%esi
 PC (0x7ff6c1d8e634) ok
 source "0x10(%rdi)" (0xa800cca0) not located in a known VMA region (needed readable region)!
 destination "%esi" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gwibber
StacktraceTop:
 pthread_mutex_lock () from /lib/libpthread.so.0
 px_proxy_factory_get_proxies ()
 ffi_call_unix64 ()
 ffi_call ()
 _CallProc ()
Title: gwibber-service crashed with SIGSEGV in pthread_mutex_lock()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[James Clemence (jvc26)]

Also affects me.

J

[Jens (jens.timmerman)]

is this a duplicate of #600010 ?

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #630890, 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.