gwibber-service crashed with SIGSEGV in pthread_mutex_lock()

[Stuart Bishop]

Binary package hint: gwibber

gwibber-service died running in the background. Using gwibber for Facebook, Twitter and Identica.

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: Thu Sep 30 10:30:57 2010
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/gwibber-service
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
InterpreterPath: /usr/bin/python2.6
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/gwibber-service
ProcEnviron:
 LANGUAGE=en_AU:en_GB:en
 PATH=(custom, user)
 LANG=en_AU.utf8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f302037d634 <pthread_mutex_lock+4>: mov 0x10(%rdi),%esi
 PC (0x7f302037d634) ok
 source "0x10(%rdi)" (0x00001940) not located in a known VMA region (needed readable region)!
 destination "%esi" ok
SegvReason: reading NULL 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

[Victor Vargas (kamus)]

maybe you are facing bug 649381

[Ken VanDine (ken-vandine)]

Upstream bug report http://code.google.com/p/libproxy/issues/detail?id=146

[Martin Pitt (pitti)]

Accepted gwibber into maverick-proposed, the package will build now and be available in a few hours. Please test and give feedback here. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance!

[Omer Akram (om26er)]

i have been using the proposed gwibber for 7 days and have not found any regressions.

[Launchpad Janitor (janitor)]

This bug was fixed in the package gwibber - 2.32.0.2-0ubuntu1

---------------
gwibber (2.32.0.2-0ubuntu1) maverick-proposed; urgency=low

  * New upstream release (LP: #660693)
    - Reuse the libproxy.ProxyFactory object to prevent a race
      condition (LP: #651761)
    - Facebook: Check for new messages since "updated_time" instead
      of "created_time", to prevent losing status updates (LP: #541831)
    - Facebook: Better handling of data returned from facebook (LP: #615339)
    - Facebook: fixed matching of uid with profiles (LP: #524510)
    - Facebook: fixed missing notifications (LP: #575394)
    - Facebook: when checking for new content, use localtime
    - Update existing record if it conflicts instead of just
      ignoring it (LP: #541831)
    - Added a missing import to properly log failure on avatar resize
    - Fix for internal Digg errors, thanks Vadim Rutkovsky (LP: #352226)
    - Branch fixes gwibber icon is broken on the right
      side, thanks Vish. (LP: #655159)
    - start gwibber-service anytime the client needs it, not just for
      service operations
    - dropped print statement used for debugging scrolling
 -- Ken VanDine <email address hidden> Wed, 13 Oct 2010 15:19:46 -0400

[Martin Pitt (pitti)]

copied to natty as well.

[Heimen Stoffels (vistaus)]

Just a heads-up: Maverick is dead so it can be removed from the report.

[dino99 (9d9)]

This version is expired