gwibber-service crashed with SIGSEGV in __pthread_mutex_lock()
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| gwibber (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
Binary package hint: gwibber
gwibber-service crashed with SIGSEGV
ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: gwibber-service 2.31.5-0ubuntu1
ProcVersionSign
Uname: Linux 2.6.35-15-generic x86_64
Architecture: amd64
CrashCounter: 1
Date: Mon Aug 16 00:12:17 2010
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/
InstallationMedia:
InterpreterPath: /usr/bin/python2.6
PackageArchitec
ProcCmdline: /usr/bin/python /usr/bin/
ProcEnviron:
LANGUAGE=
LANG=pt_BR.utf8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7f1a44647644 <__pthread_
PC (0x7f1a44647644) ok
source "0x10(%rdi)" (0x28004c70) 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_
px_proxy_
ffi_call_unix64 ()
ffi_call ()
_CallProc ()
Title: gwibber-service crashed with SIGSEGV in __pthread_
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin netdev plugdev sambashare tape video
| Apport retracing service (apport) wrote This bug is a duplicate | #2 |
| visibility: | private → public |
| tags: | removed: need-amd64-retrace |
Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #630890, so 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. Please continue to report any other bugs you may find.