gwibber-service crashed with SIGSEGV
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gwibber (Ubuntu) |
Fix Released
|
Medium
|
Unassigned |
Bug Description
random crash
I believe this is due to thread-unsafe usage of libdbus, care of glib implicitly spawning a thread for gdbus. A call to dbus_threads_
ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: gwibber-service 3.5.4-0ubuntu1
ProcVersionSign
Uname: Linux 3.5.0-14-generic x86_64
ApportVersion: 2.5.1-0ubuntu7
Architecture: amd64
CrashCounter: 1
Date: Mon Sep 17 14:48:08 2012
ExecutablePath: /usr/bin/
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110919)
InterpreterPath: /usr/bin/python2.7
PackageArchitec
ProcCmdline: /usr/bin/python /usr/bin/
Signal: 11
SourcePackage: gwibber
StacktraceTop:
?? () from /lib/x86_
?? () from /lib/x86_
?? () from /lib/x86_
?? () from /lib/x86_
?? () from /lib/x86_
Title: gwibber-service crashed with SIGSEGV
UpgradeStatus: Upgraded to quantal on 2012-07-23 (55 days ago)
UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare
Changed in gwibber (Ubuntu): | |
status: | Invalid → Confirmed |
importance: | Undecided → High |
importance: | High → Medium |
description: | updated |
StacktraceTop: lib/x86_ 64-linux- gnu/libdbus- 1.so.3 lib/x86_ 64-linux- gnu/libdbus- 1.so.3 lib/x86_ 64-linux- gnu/libdbus- 1.so.3 lib/x86_ 64-linux- gnu/libdbus- 1.so.3 lib/x86_ 64-linux- gnu/libdbus- 1.so.3
?? () from /tmp/tmpASFzAG/
?? () from /tmp/tmpASFzAG/
?? () from /tmp/tmpASFzAG/
?? () from /tmp/tmpASFzAG/
?? () from /tmp/tmpASFzAG/