gwibber-service crashed with SIGSEGV in g_simple_async_result_complete()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gwibber (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
bug report by apport
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
CheckboxSubmission: 93065c6f67bd29c
CheckboxSystem: b1865df84255b87
Date: Sun Sep 16 22:36:20 2012
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110901)
InterpreterPath: /usr/bin/python2.7
PackageArchitec
ProcCmdline: /usr/bin/python /usr/bin/
SegvAnalysis:
Segfault happened at: 0x7f9df23ed7eb: mov 0x8(%rax),%rcx
PC (0x7f9df23ed7eb) ok
source "0x8(%rax)" (0x00000008) not located in a known VMA region (needed readable region)!
destination "%rcx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gwibber
StacktraceTop:
?? () from /usr/lib/
g_simple_
?? () from /usr/lib/
g_main_
?? () from /lib/x86_
Title: gwibber-service crashed with SIGSEGV in g_simple_
UpgradeStatus: Upgraded to quantal on 2012-09-16 (0 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1047749, 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.