*** 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/1228586/+attachment/3833315/+files/CoreDump.gz
** Attachment removed: "Disassembly.txt"
https://bugs.launchpad.net/bugs/1228586/+attachment/3833317/+files/Disassembly.txt
** Attachment removed: "ProcMaps.txt"
https://bugs.launchpad.net/bugs/1228586/+attachment/3833319/+files/ProcMaps.txt
** Attachment removed: "ProcStatus.txt"
https://bugs.launchpad.net/bugs/1228586/+attachment/3833320/+files/ProcStatus.txt
** Attachment removed: "Registers.txt"
https://bugs.launchpad.net/bugs/1228586/+attachment/3833321/+files/Registers.txt
** Attachment removed: "Stacktrace.txt"
https://bugs.launchpad.net/bugs/1228586/+attachment/3833323/+files/Stacktrace.txt
** Attachment removed: "ThreadStacktrace.txt"
https://bugs.launchpad.net/bugs/1228586/+attachment/3833324/+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/1228586
Title:
mission-control-5 crashed with SIGSEGV in g_slice_alloc()
Status in “telepathy-mission-control-5” package in Ubuntu:
New
Bug description:
going by the crash's timestamp it seems to have occurred while
shutting down
ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: telepathy-mission-control-5 1:5.14.1-1ubuntu5
ProcVersionSignature: Ubuntu 3.11.0-8.15-generic 3.11.1
Uname: Linux 3.11.0-8-generic x86_64
ApportVersion: 2.12.4-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Sat Sep 21 14:28:04 2013
ExecutablePath: /usr/lib/telepathy/mission-control-5
InstallationDate: Installed on 2013-05-16 (128 days ago)
InstallationMedia: Ubuntu-Server 13.04 "Raring Ringtail" - Release amd64
(20130423.1)
MarkForUpload: True
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.11.0-8-generic.efi.signed
root=UUID=d4bc1b56-12b9-4442-b2f7-168a22853e56 ro quiet splash vt.handoff=7
ProcEnviron:
SHELL=/bin/false
XDG_RUNTIME_DIR=<set>
PATH=(custom, no user)
LANGUAGE=en_GB
LANG=en_GB.UTF-8
SegvAnalysis:
Segfault happened at: 0x7fc012e87ad7 <g_slice_alloc+167>: mov
(%rbx),%rax
PC (0x7fc012e87ad7) 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: Upgraded to saucy on 2013-07-27 (55 days ago)
UserGroups:
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/telepathy-mission-control-5/+bug/1228586/+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
