Ubuntu
gwibber package

gwibber-service crashed with SIGSEGV in pthread_mutex_lock()

Bug #647807 reported by Jacob Litewski on 2010-09-25

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

18

This bug affects 2 people

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

Bug Description

Binary package hint: gwibber

gwibber crashed out of nowhere. First time it has happened to me. Starts right back up without any hitch.

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: Sat Sep 25 16:08:41 2010
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/gwibber-service
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Beta amd64 (20100901.1)
InterpreterPath: /usr/bin/python2.6
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/gwibber-service
ProcEnviron:
LANG=en_US.utf8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7f28217f3634 <pthread_mutex_lock+4>: mov 0x10(%rdi),%esi
PC (0x7f28217f3634) ok
source "0x10(%rdi)" (0x04053cc0) 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 () 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

Tags:

Revision history for this message

Jacob Litewski (j.litewski) wrote on 2010-09-25:

#1

CoreDump.gz Edit (3.8 MiB, application/x-gzip)
Dependencies.txt Edit (3.2 KiB, text/plain; charset="utf-8")
Disassembly.txt Edit (1.0 KiB, text/plain; charset="utf-8")
ProcMaps.txt Edit (66.9 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (803 bytes, text/plain; charset="utf-8")
Registers.txt Edit (787 bytes, text/plain; charset="utf-8")
Stacktrace.txt Edit (3.2 KiB, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (9.7 KiB, text/plain; charset="utf-8")
gwibber.log.txt Edit (21.9 KiB, text/plain; charset="utf-8")

visibility:

private → public

Revision history for this message

Apport retracing service (apport) wrote on 2010-09-25: Possible regression detected

#2

This crash has the same stack trace characteristics as bug #630890. However, the latter was already fixed in an earlier package version than the one in this report. This might be a regression or because the problem is in a dependent package.

tags:	added: regression-retracer
tags:	removed: need-amd64-retrace

Revision history for this message

Jacob Litewski (j.litewski) wrote on 2010-09-27:

#3

Do i need to do anything special to help this bug? It usually crashes after I log in if that helps.

Revision history for this message

Ken VanDine (ken-vandine) wrote on 2010-09-28:

#4

So this crash happens often? Looking at the log in the bug report, gwibber-service had been running for nearly a fully day before crashing. Since then has it been crashing more often?

Do you have a proxy set?

Revision history for this message

Jacob Litewski (j.litewski) wrote on 2010-09-28:

#5

I don't have a proxy set, and It crashed right after I booted up yesterday. So far it's running without a hitch, but the last couple of times I started up before I submitted a bug report it crashed either when I was editing accounts or right after I log in.

Revision history for this message

Jens (jens.timmerman) wrote on 2010-09-29:

#6

I had this same crash after rebooting for a big partial upgrade, maybe this was a crash report generated during shut down after the upgrade?

no more crashing since then...

Revision history for this message

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

#7

maybe this issue is connected to bug 649381

Changed in gwibber (Ubuntu):
importance:	Undecided → Medium

Revision history for this message

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

#8

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.

Report a bug

This report contains Public information

Everyone can see this information.

Duplicate of bug #651761 Remove

You are

Subscribing...

Edit bug mail

Other bug subscribers

Bug attachments

Add attachment

Remote bug watches

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