*** 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/1206101/+attachment/3753169/+files/CoreDump.gz
** Attachment removed: "Disassembly.txt"
https://bugs.launchpad.net/bugs/1206101/+attachment/3753171/+files/Disassembly.txt
** Attachment removed: "ProcMaps.txt"
https://bugs.launchpad.net/bugs/1206101/+attachment/3753173/+files/ProcMaps.txt
** Attachment removed: "ProcStatus.txt"
https://bugs.launchpad.net/bugs/1206101/+attachment/3753174/+files/ProcStatus.txt
** Attachment removed: "Registers.txt"
https://bugs.launchpad.net/bugs/1206101/+attachment/3753175/+files/Registers.txt
** Attachment removed: "Stacktrace.txt"
https://bugs.launchpad.net/bugs/1206101/+attachment/3753177/+files/Stacktrace.txt
** Attachment removed: "ThreadStacktrace.txt"
https://bugs.launchpad.net/bugs/1206101/+attachment/3753178/+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/1206101
Title:
mission-control-5 crashed with SIGSEGV in g_slice_alloc()
Status in “telepathy-mission-control-5” package in Ubuntu:
New
Bug description:
This apport dialog appears shortly after logging in. I don't have any
online accounts configured, so can't tell whether telepathy crashes
when logging in or when logging out from the previous session...
ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: telepathy-mission-control-5 1:5.14.1-1ubuntu1
ProcVersionSignature: Ubuntu 3.10.0-5.15-generic 3.10.2
Uname: Linux 3.10.0-5-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.11-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Mon Jul 29 02:12:50 2013
ExecutablePath: /usr/lib/telepathy/mission-control-5
InstallationDate: Installed on 2012-07-11 (382 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64+mac (20120627)
MarkForUpload: True
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.10.0-5-generic
root=UUID=57a1d5b6-4b80-45e4-9aae-3271e49f4da3 ro nomodeset quiet splash
ProcEnviron:
SHELL=/bin/false
XDG_RUNTIME_DIR=<set>
PATH=(custom, no user)
LANG=en_GB.utf8
SegvAnalysis:
Segfault happened at: 0x7f96dc556767 <g_slice_alloc+167>: mov
(%rbx),%rax
PC (0x7f96dc556767) ok
source "(%rbx)" (0x0000001f) not located in a known VMA region (needed
readable region)!
destination "%rax" ok
SegvReason: reading NULL 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 (1 days ago)
UserGroups:
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/telepathy-mission-control-5/+bug/1206101/+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
