*** This bug is a duplicate of bug 1118114 *** https://bugs.launchpad.net/bugs/1118114
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 #1118114, 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/1123183/+attachment/3525479/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1123183/+attachment/3525481/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1123183/+attachment/3525483/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1123183/+attachment/3525484/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1123183/+attachment/3525485/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1123183/+attachment/3525487/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1123183/+attachment/3525488/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1118114 ** Information type changed from Private to Public ** Tags removed: need-i386-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/1123183 Title: mission-control-5 crashed with SIGSEGV in g_slice_alloc() Status in “telepathy-mission-control-5” package in Ubuntu: New Bug description: when i started my computer this error came up ProblemType: Crash DistroRelease: Ubuntu 13.04 Package: telepathy-mission-control-5 1:5.14.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-5.10-generic 3.8.0-rc6 Uname: Linux 3.8.0-5-generic i686 ApportVersion: 2.8-0ubuntu4 Architecture: i386 Date: Tue Feb 12 16:31:32 2013 ExecutablePath: /usr/lib/telepathy/mission-control-5 InstallationDate: Installed on 2012-11-22 (82 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha i386 (20121113) MarkForUpload: True ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.8.0-5-generic root=UUID=a59a2c73-2bf1-4c04-a0a4-1167b06b6229 ro quiet splash vt.handoff=7 ProcEnviron: SHELL=/bin/false XDG_RUNTIME_DIR=<set> PATH=(custom, no user) LANGUAGE=sv:en LANG=sv_SE.UTF-8 SegvAnalysis: Segfault happened at: 0xb71c8882 <g_slice_alloc+178>: mov (%edi),%edx PC (0xb71c8882) ok source "(%edi)" (0x00000001) not located in a known VMA region (needed readable region)! destination "%edx" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: telepathy-mission-control-5 StacktraceTop: g_slice_alloc () from /lib/i386-linux-gnu/libglib-2.0.so.0 g_string_sized_new () from /lib/i386-linux-gnu/libglib-2.0.so.0 g_string_new () from /lib/i386-linux-gnu/libglib-2.0.so.0 g_key_file_to_data () from /lib/i386-linux-gnu/libglib-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/1123183/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp