gwibber-service crashed with SIGSEGV in pthread_mutex_lock()

[Jacob Litewski]

Binary package hint: gwibber

gwibber crashed out of nowhere. First time it has happened to me. Starts right back up without any hitch.

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: gwibber-service 2.31.95-0ubuntu2
ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic x86_64
Architecture: amd64
CrashCounter: 1
Date: Sat Sep 25 16:08:41 2010
EcryptfsInUse: Yes
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:
 LANG=en_US.utf8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f28217f3634 <pthread_mutex_lock+4>: mov 0x10(%rdi),%esi
 PC (0x7f28217f3634) ok
 source "0x10(%rdi)" (0x04053cc0) not located in a known VMA region (needed readable region)!
 destination "%esi" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gwibber
StacktraceTop:
 pthread_mutex_lock () from /lib/libpthread.so.0
 px_proxy_factory_get_proxies () from /usr/lib/libproxy.so.0
 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
Title: gwibber-service crashed with SIGSEGV in pthread_mutex_lock()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

This crash has the same stack trace characteristics as bug #630890. However, the latter was already fixed in an earlier package version than the one in this report. This might be a regression or because the problem is in a dependent package.

[Jacob Litewski (j.litewski)]

Do i need to do anything special to help this bug? It usually crashes after I log in if that helps.

[Ken VanDine (ken-vandine)]

So this crash happens often? Looking at the log in the bug report, gwibber-service had been running for nearly a fully day before crashing. Since then has it been crashing more often?

Do you have a proxy set?

[Jacob Litewski (j.litewski)]

I don't have a proxy set, and It crashed right after I booted up yesterday. So far it's running without a hitch, but the last couple of times I started up before I submitted a bug report it crashed either when I was editing accounts or right after I log in.

[Jens (jens.timmerman)]

I had this same crash after rebooting for a big partial upgrade, maybe this was a crash report generated during shut down after the upgrade?

no more crashing since then...

[Victor Vargas (kamus)]

maybe this issue is connected to bug 649381

[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 651761, 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.