telepathy-idle crashed with SIGSEGV in ffi_call_unix64()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
telepathy-idle (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Crash if same account is added as google account and jabber account in online accounts settings.
ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: telepathy-idle 0.1.12-1
ProcVersionSign
Uname: Linux 3.5.0-11-generic x86_64
ApportVersion: 2.5.1-0ubuntu1
Architecture: amd64
Date: Wed Aug 22 23:40:16 2012
ExecutablePath: /usr/lib/
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
ProcCmdline: /usr/lib/
SegvAnalysis:
Segfault happened at: 0x40a920: mov 0x88(%rbp),%eax
PC (0x0040a920) ok
source "0x88(%rbp)" (0x00000088) not located in a known VMA region (needed readable region)!
destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: telepathy-idle
StacktraceTop:
?? ()
ffi_call_unix64 () from /usr/lib/
ffi_call () from /usr/lib/
g_cclosure_
g_closure_invoke () from /usr/lib/
Title: telepathy-idle crashed with SIGSEGV in ffi_call_unix64()
UpgradeStatus: Upgraded to quantal on 2012-07-24 (28 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
description: | updated |
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 #1039234, 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.