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
Sorry but I have just time to see the desk and the messages appears.
3 messages this time, one after the others.
Thanks for all problems you have still resolved.
Please note I have 2 computers : i-386 and i-86-64, both with Ubuntu 13-10.
Christian.
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: Wed Aug 21 14:46:43 2013
ExecutablePath: /usr/lib/
MarkForUpload: True
ProcCmdline: BOOT_IMAGE=
ProcEnviron:
SHELL=/bin/false
XDG_RUNTIME_
PATH=(custom, no user)
LANG=fr_FR.UTF-8
SegvAnalysis:
Segfault happened at: 0xb716d96e <g_slice_
PC (0xb716d96e) ok
source "(%edi)" (0xac712264) 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_append () from /lib/i386-
g_queue_push_tail () from /lib/i386-
?? () from /usr/lib/
tp_debug_
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 #1159389, 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.