mission-control-5 crashed with SIGSEGV in g_slice_alloc()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
telepathy-mission-control-5 (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
I have a popup signaling that there is a software pb at each start up. This is Ubuntu 13.10, I am pushing all the updates released, but so far it's still the sme
ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: telepathy-
ProcVersionSign
Uname: Linux 3.11.0-3-generic i686
ApportVersion: 2.12.1-0ubuntu2
Architecture: i386
Date: Mon Aug 26 00:07:34 2013
ExecutablePath: /usr/lib/
MarkForUpload: True
ProcCmdline: BOOT_IMAGE=
SegvAnalysis:
Segfault happened at: 0xb7214a6e <g_slice_
PC (0xb7214a6e) ok
source "(%edi)" (0x41d486a3) not located in a known VMA region (needed readable region)!
destination "%edx" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: telepathy-
StacktraceTop:
g_slice_alloc () from /lib/i386-
g_list_prepend () from /lib/i386-
?? () from /usr/lib/
?? () from /usr/lib/
dbus_g_
Title: mission-control-5 crashed with SIGSEGV in g_slice_alloc()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
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 #1129879, 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.