*** 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/1562442/+attachment/4613109/+files/CoreDump.gz
** Attachment removed: "Disassembly.txt"
https://bugs.launchpad.net/bugs/1562442/+attachment/4613111/+files/Disassembly.txt
** Attachment removed: "ProcMaps.txt"
https://bugs.launchpad.net/bugs/1562442/+attachment/4613115/+files/ProcMaps.txt
** Attachment removed: "ProcStatus.txt"
https://bugs.launchpad.net/bugs/1562442/+attachment/4613116/+files/ProcStatus.txt
** Attachment removed: "Registers.txt"
https://bugs.launchpad.net/bugs/1562442/+attachment/4613117/+files/Registers.txt
** Attachment removed: "Stacktrace.txt"
https://bugs.launchpad.net/bugs/1562442/+attachment/4613119/+files/Stacktrace.txt
** Attachment removed: "ThreadStacktrace.txt"
https://bugs.launchpad.net/bugs/1562442/+attachment/4613120/+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 Ubuntu
Touch seeded packages, which is subscribed to telepathy-mission-
control-5 in Ubuntu.
https://bugs.launchpad.net/bugs/1562442
Title:
mission-control-5 crashed with SIGSEGV in __libc_start_main()
Status in telepathy-mission-control-5 package in Ubuntu:
New
Bug description:
I got this after logging in. The last thing I did before reboot was
install dbus user session and gnome activity journal
ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: telepathy-mission-control-5 1:5.16.3-1ubuntu6
ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6
Uname: Linux 4.4.0-16-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
CurrentDesktop: MATE
Date: Sat Mar 26 22:52:51 2016
ExecutablePath: /usr/lib/telepathy/mission-control-5
InstallationDate: Installed on 2016-03-05 (21 days ago)
InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Alpha amd64
(20160224)
ProcCmdline: BOOT_IMAGE=/vmlinuz-4.4.0-16-generic.efi.signed
root=/dev/mapper/ubuntu--mate--vg-root ro quiet splash 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 () from /lib/x86_64-linux-gnu/libc.so.6
?? ()
Title: mission-control-5 crashed with SIGSEGV in __libc_start_main()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip libvirtd lpadmin lxd plugdev sambashare sudo
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/telepathy-mission-control-5/+bug/1562442/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
