unity8 crashed with SIGSEGV in TiledDisplayConfigurationPolicy::apply_to()

[navalis]

After login Unity8 turns to a black screen

ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: unity8 8.11+16.04.20160129-0ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0
Uname: Linux 4.4.0-2-generic x86_64
ApportVersion: 2.19.4-0ubuntu2
Architecture: amd64
CrashCounter: 1
Date: Mon Feb 8 07:56:22 2016
ExecutablePath: /usr/bin/unity8
InstallationDate: Installed on 2016-02-04 (4 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160203)
ProcCmdline: unity8
ProcEnviron:
 LANGUAGE=pt:pt_BR:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=pt_PT.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7fd127b0aef8: mov (%rax),%eax
 PC (0x7fd127b0aef8) ok
 source "(%rax)" (0x7fe1181288e0) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: unity8
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqpa-mirserver.so
 ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.37
 ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.37
 TiledDisplayConfigurationPolicy::apply_to(mir::graphics::DisplayConfiguration&) () from /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqpa-mirserver.so
 ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.37
Title: unity8 crashed with SIGSEGV in TiledDisplayConfigurationPolicy::apply_to()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[Apport retracing service (apport)]

StacktraceTop:
 __event_probe__qtmirserver___touchEventDispatch_end (__tp_data=0x7fd1219617a0, event_time=140536188377104) at /build/qtmir-gles-8kNXkL/qtmir-gles-0.4.7+16.04.20160212/build-android/src/platforms/mirserver/./tracepoints.h:27
 ?? ()
 ?? ()
 ?? ()
 ?? ()

[Albert Astals Cid (aacid)]

Seems more a mir or qtmir issue

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Daniel van Vugt (vanvugt)]

The stack is a bit corrupt, but given the offending function is tiny this is very likely just another case of bug 1560497.