mission-control-5 crashed with SIGSEGV

Bug #1585956 reported by Iain Lane
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
telepathy-mission-control-5 (Ubuntu)
New
Undecided
Unassigned

Bug Description

This has only appeared since I switched to dbus-user-session - maybe unreleated, but who knows.

ProblemType: Crash
DistroRelease: Ubuntu 16.10
Package: telepathy-mission-control-5 1:5.16.3-1ubuntu6
ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10
Uname: Linux 4.4.0-23-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.1-0ubuntu4
Architecture: amd64
CrashCounter: 1
CurrentDesktop: Unity
Date: Thu May 26 10:25:26 2016
ExecutablePath: /usr/lib/telepathy/mission-control-5
InstallationDate: Installed on 2015-06-05 (355 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150605)
ProcCmdline: BOOT_IMAGE=/vmlinuz-4.4.0-23-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash swapaccount=1 vt.handoff=7
SegvAnalysis:
 Segfault happened at: 0x4104f0: mov 0x20(%rdi),%rdi
 PC (0x004104f0) ok
 source "0x20(%rdi)" (0x00000020) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: telepathy-mission-control-5
StacktraceTop:
 ()
 ()
 __libc_start_main (main=0x40e580, argc=1, argv=0x7fffda8d37e8, init=<optimised out>, fini=<optimised out>, rtld_fini=<optimised out>, stack_end=0x7fffda8d37d8) at ../csu/libc-start.c:291
 ()
Title: mission-control-5 crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip libvirt libvirtd lpadmin lxd plugdev sambashare sbuild sudo

Revision history for this message
Iain Lane (laney) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

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 #621048, 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.

information type: Private → Public
tags: removed: need-amd64-retrace
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.