Ubuntu
gwibber package

gwibber-accounts crashed with SIGSEGV in __pthread_mutex_lock()

Bug #649381 reported by Deactivated User on 2010-09-27

This bug report is a duplicate of: Bug #651761: gwibber-service crashed with SIGSEGV in pthread_mutex_lock(). Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	gwibber (Ubuntu)	New	Medium	Unassigned

Bug Description

Binary package hint: gwibber

Crash on add (facebook) account.

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: gwibber 2.31.95-0ubuntu2
ProcVersionSignature: Ubuntu 2.6.35-22.33~ppa1-generic-tuxonice 2.6.35.4
Uname: Linux 2.6.35-22-generic-tuxonice x86_64
NonfreeKernelModules: wl
Architecture: amd64
Date: Mon Sep 27 17:56:17 2010
ExecutablePath: /usr/bin/gwibber-accounts
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha amd64 (20100122)
InterpreterPath: /usr/bin/python2.6
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/gwibber-accounts
ProcEnviron:
SHELL=/bin/bash
PATH=(custom, user)
LANG=en_US.utf8
SegvAnalysis:
Segfault happened at: 0x7f43fda05634 <__pthread_mutex_lock+4>: mov 0x10(%rdi),%esi
PC (0x7f43fda05634) ok
source "0x10(%rdi)" (0xe001dd70) 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 (mutex=0xe001dd60) at pthread_mutex_lock.c:50
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-accounts crashed with SIGSEGV in __pthread_mutex_lock()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Tags:

Revision history for this message

Deactivated User (deactivated-user636007-deactivatedaccount) wrote on 2010-09-27:

Dependencies.txt Edit (5.4 KiB, text/plain; charset="utf-8")
Disassembly.txt Edit (1.1 KiB, text/plain; charset="utf-8")
ProcMaps.txt Edit (77.7 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (802 bytes, text/plain; charset="utf-8")
Registers.txt Edit (843 bytes, text/plain; charset="utf-8")
Stacktrace.txt Edit (7.7 KiB, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (11.2 KiB, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2010-09-27:

StacktraceTop:
pthread_mutex_lock () from /lib/libpthread.so.0
px_proxy_factory_get_proxies (self=0xe001dd60,
ffi_call_unix64 ()
ffi_call ()
_CallProc (pProc=<value optimized out>,

Revision history for this message

Apport retracing service (apport) wrote on 2010-09-27: Stacktrace.txt

Stacktrace.txt Edit (11.6 KiB, text/plain)

Revision history for this message

Apport retracing service (apport) wrote on 2010-09-27: ThreadStacktrace.txt

ThreadStacktrace.txt Edit (14.2 KiB, text/plain)

Changed in gwibber (Ubuntu):
importance:	Undecided → Medium
tags:	removed: need-amd64-retrace

Victor Vargas (kamus) on 2010-09-30

visibility:

private → public

Revision history for this message

Victor Vargas (kamus) wrote on 2010-10-12:

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.