*** This bug is a duplicate of bug 621048 ***
https://bugs.launchpad.net/bugs/621048
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.
** Attachment removed: "CoreDump.gz"
https://bugs.launchpad.net/bugs/1585956/+attachment/4670663/+files/CoreDump.gz
** Attachment removed: "Disassembly.txt"
https://bugs.launchpad.net/bugs/1585956/+attachment/4670665/+files/Disassembly.txt
** Attachment removed: "ProcMaps.txt"
https://bugs.launchpad.net/bugs/1585956/+attachment/4670669/+files/ProcMaps.txt
** Attachment removed: "ProcStatus.txt"
https://bugs.launchpad.net/bugs/1585956/+attachment/4670670/+files/ProcStatus.txt
** Attachment removed: "Registers.txt"
https://bugs.launchpad.net/bugs/1585956/+attachment/4670671/+files/Registers.txt
** Attachment removed: "Stacktrace.txt"
https://bugs.launchpad.net/bugs/1585956/+attachment/4670673/+files/Stacktrace.txt
** Attachment removed: "ThreadStacktrace.txt"
https://bugs.launchpad.net/bugs/1585956/+attachment/4670674/+files/ThreadStacktrace.txt
** This bug has been marked a duplicate of bug 621048
mission-control-5 crashed with SIGSEGV in __libc_start_main()
** 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/1585956
Title:
mission-control-5 crashed with SIGSEGV
Status in telepathy-mission-control-5 package in Ubuntu:
New
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
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/telepathy-mission-control-5/+bug/1585956/+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
