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
This occurred after booting into gnome-session-
ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: telepathy-
ProcVersionSign
Uname: Linux 3.10.0-2-generic x86_64
ApportVersion: 2.10.2-0ubuntu4
Architecture: amd64
Date: Sun Jul 14 21:57:19 2013
ExecutablePath: /usr/lib/
InstallationDate: Installed on 2012-08-21 (327 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120821)
MarkForUpload: True
ProcCmdline: BOOT_IMAGE=
ProcEnviron:
SHELL=/bin/false
XDG_RUNTIME_
PATH=(custom, no user)
LANGUAGE=en_US:en
LANG=en_US.UTF-8
SegvAnalysis:
Segfault happened at: 0x7fd864c9b767 <g_slice_
PC (0x7fd864c9b767) ok
source "(%rbx)" (0x00010000) not located in a known VMA region (needed readable region)!
destination "%rax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: telepathy-
StacktraceTop:
g_slice_alloc () from /lib/x86_
g_slist_prepend () from /lib/x86_
?? () from /usr/lib/
?? () from /usr/lib/
g_object_
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 #1154674, 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.