*** This bug is a duplicate of bug 1154674 ***
https://bugs.launchpad.net/bugs/1154674
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.
** Attachment removed: "CoreDump.gz"
https://bugs.launchpad.net/bugs/1207978/+attachment/3759041/+files/CoreDump.gz
** Attachment removed: "Disassembly.txt"
https://bugs.launchpad.net/bugs/1207978/+attachment/3759043/+files/Disassembly.txt
** Attachment removed: "ProcMaps.txt"
https://bugs.launchpad.net/bugs/1207978/+attachment/3759045/+files/ProcMaps.txt
** Attachment removed: "ProcStatus.txt"
https://bugs.launchpad.net/bugs/1207978/+attachment/3759046/+files/ProcStatus.txt
** Attachment removed: "Registers.txt"
https://bugs.launchpad.net/bugs/1207978/+attachment/3759047/+files/Registers.txt
** Attachment removed: "Stacktrace.txt"
https://bugs.launchpad.net/bugs/1207978/+attachment/3759049/+files/Stacktrace.txt
** Attachment removed: "ThreadStacktrace.txt"
https://bugs.launchpad.net/bugs/1207978/+attachment/3759050/+files/ThreadStacktrace.txt
** This bug has been marked a duplicate of bug 1154674
mission-control-5 crashed with SIGSEGV in magazine_chain_pop_head()
** Information type changed from Private to Public
** Tags removed: need-amd64-retrace
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to telepathy-mission-control-5 in Ubuntu.
https://bugs.launchpad.net/bugs/1207978
Title:
mission-control-5 crashed with SIGSEGV in g_slice_alloc()
Status in “telepathy-mission-control-5” package in Ubuntu:
New
Bug description:
I'm not sure what's going on with my PC. Have upgraded to 13.10, and
the machine keeps popping up these error messages even though the
system seems to work fine for what I need.
ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: telepathy-mission-control-5 1:5.14.1-1ubuntu1
ProcVersionSignature: Ubuntu 3.10.0-6.17-generic 3.10.3
Uname: Linux 3.10.0-6-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.11-0ubuntu1
Architecture: amd64
Date: Tue Jul 30 15:57:09 2013
ExecutablePath: /usr/lib/telepathy/mission-control-5
MarkForUpload: True
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.10.0-6-generic
root=UUID=8a19114b-c0d6-4a9d-b77d-f089a6a95ee4 ro quiet splash
ProcEnviron:
SHELL=/bin/false
XDG_RUNTIME_DIR=<set>
PATH=(custom, no user)
LANGUAGE=en_US:en
LANG=en_US.UTF-8
SegvAnalysis:
Segfault happened at: 0x7f8a9b951767 <g_slice_alloc+167>: mov
(%rbx),%rax
PC (0x7f8a9b951767) 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-mission-control-5
StacktraceTop:
g_slice_alloc () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
g_slist_prepend () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
g_object_new_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: mission-control-5 crashed with SIGSEGV in g_slice_alloc()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/telepathy-mission-control-5/+bug/1207978/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
