mission-control-5 crashed with SIGSEGV in g_slist_append()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
telepathy-mission-control-5 (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Crash.
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: Tue Jul 9 09:34:31 2013
ExecutablePath: /usr/lib/
InstallationDate: Installed on 2013-07-05 (4 days ago)
InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Alpha amd64 (20130621)
MarkForUpload: True
ProcCmdline: BOOT_IMAGE=
ProcEnviron:
SHELL=/bin/false
XDG_RUNTIME_
PATH=(custom, no user)
LANGUAGE=es_CL:es
LANG=es_CL.UTF-8
SegvAnalysis:
Segfault happened at: 0x7f6e23a83c19 <g_slist_
PC (0x7f6e23a83c19) ok
source "%rbp" ok
destination "(%rax)" (0x7f6e24b5fa0e) in non-writable VMA region: 0x7f6e24a4e000-
SegvReason: writing VMA /usr/lib/
Signal: 11
SourcePackage: telepathy-
StacktraceTop:
g_slist_append () from /lib/x86_
g_object_
?? () from /usr/lib/
g_type_class_ref () from /usr/lib/
g_object_
Title: mission-control-5 crashed with SIGSEGV in g_slist_append()
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 #1197578, 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.