Ubuntu
gwibber package

gwibber-service crashed with SIGSEGV in pthread_mutex_lock()

Bug #651761 reported by Stuart Bishop
58
This bug affects 8 people
Affects Status Importance Assigned to Milestone
Gwibber
Fix Released
High
Ken VanDine
Gwibber 2.32.0
gwibber (Ubuntu)
Fix Released
High
Unassigned
Maverick
Fix Released
Undecided
Unassigned
libproxy (Ubuntu)
Invalid
Medium
Unassigned
Maverick
Won't Fix
Undecided
Unassigned

Bug Description

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

Revision history for this message
Stuart Bishop (stub) wrote :
Revision history for this message
Victor Vargas (kamus) wrote :

maybe you are facing bug 649381

Changed in gwibber (Ubuntu):
importance: Undecided → Medium
Revision history for this message
Ken VanDine (ken-vandine) wrote :

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

Ken VanDine (ken-vandine)
Changed in gwibber:
status: New → Fix Committed
assignee: nobody → Ken VanDine (ken-vandine)
milestone: none → 2.32.1
Ken VanDine (ken-vandine)
Changed in gwibber (Ubuntu):
importance: Medium → Critical
importance: Critical → High
Changed in gwibber:
importance: Undecided → High
milestone: 2.32.1 → 2.32.0
Ken VanDine (ken-vandine)
Changed in gwibber:
status: Fix Committed → Fix Released
Victor Vargas (kamus)
Changed in gwibber (Ubuntu):
status: New → Fix Released
Changed in libproxy (Ubuntu):
importance: Undecided → Medium
status: New → Triaged
Omer Akram (om26er)
Changed in gwibber (Ubuntu):
status: Fix Released → Triaged
Revision history for this message
Martin Pitt (pitti) wrote : Please test proposed package

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!

Changed in gwibber (Ubuntu Maverick):
status: New → Fix Committed
tags: added: verification-needed
Revision history for this message
Omer Akram (om26er) wrote :

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

tags: added: verification-done
removed: verification-needed
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in gwibber (Ubuntu Maverick):
status: Fix Committed → Fix Released
Revision history for this message
Martin Pitt (pitti) wrote :

copied to natty as well.

Changed in gwibber (Ubuntu):
status: Triaged → Fix Released
Revision history for this message
Heimen Stoffels (vistaus) wrote :

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

Adolfo Jayme Barrientos (fitojb)
Changed in libproxy (Ubuntu Maverick):
status: New → Won't Fix
Revision history for this message
dino99 (9d9) wrote :

This version is expired

Changed in libproxy (Ubuntu):
status: Triaged → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.