gwibber-service crashed with SIGSEGV in pthread_mutex_lock()

Bug #613651 reported by Jamie Strandboge
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
gwibber (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: gwibber

Upgraded from Lucid to Maverick. Upon starting gwibber, I get an apport message stating it crashes. I have twitter and facebook accounts.

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: gwibber-service 2.31.3-0ubuntu2
ProcVersionSignature: Ubuntu 2.6.35-14.19-generic 2.6.35
Uname: Linux 2.6.35-14-generic x86_64
Architecture: amd64
Date: Wed Aug 4 16:22:11 2010
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/gwibber-service
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100427.1)
InterpreterPath: /usr/bin/python2.6
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/gwibber-service
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=en_US.utf8
SegvAnalysis:
 Segfault happened at: 0x7f350d822644 <pthread_mutex_lock+4>: mov 0x10(%rdi),%esi
 PC (0x7f350d822644) ok
 source "0x10(%rdi)" (0xf80247f0) 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 kvm libvirtd lpadmin plugdev sambashare sbuild

Revision history for this message
Jamie Strandboge (jdstrand) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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