messaging-app crashed with SIGABRT in qt_message_fatal()

[dinamic]

messaging-app crashed with SIGABRT in QMessageLogger::fatal()

ProblemType: Crash
DistroRelease: Ubuntu 17.04
Package: messaging-app 0.1+17.04.20161130-0ubuntu1
ProcVersionSignature: Ubuntu 4.10.0-8.10-generic 4.10.0-rc8
Uname: Linux 4.10.0-8-generic x86_64
ApportVersion: 2.20.4-0ubuntu2
Architecture: amd64
CrashCounter: 1
CurrentDesktop: Unity:Unity8
Date: Thu Feb 16 13:50:05 2017
ExecutablePath: /usr/bin/messaging-app
InstallationDate: Installed on 2016-12-12 (67 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20161108)
ProcCmdline: messaging-app
Signal: 6
SourcePackage: messaging-app
StacktraceTop:
 QMessageLogger::fatal(char const*, ...) const () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
 QSGRenderLoop::handleContextCreationFailure(QQuickWindow*, bool) () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
 ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
 ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
 QWindow::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
Title: messaging-app crashed with SIGABRT in QMessageLogger::fatal()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[Apport retracing service (apport)]

StacktraceTop:
 qt_message_fatal (context=..., message=<synthetic pointer>) at global/qlogging.cpp:1682
 QMessageLogger::fatal (this=this@entry=0x7ffecedf80d0, msg=msg@entry=0x7f174f099bf7 "%s") at global/qlogging.cpp:793
 QSGRenderLoop::handleContextCreationFailure (this=this@entry=0x556018879560, window=0x5560188771a0, isEs=isEs@entry=false) at scenegraph/qsgrenderloop.cpp:264
 QSGThreadedRenderLoop::handleExposure (this=this@entry=0x556018879560, window=window@entry=0x5560188771a0) at scenegraph/qsgthreadedrenderloop.cpp:952
 QSGThreadedRenderLoop::exposureChanged (this=0x556018879560, window=0x5560188771a0) at scenegraph/qsgthreadedrenderloop.cpp:890

[Launchpad Janitor (janitor)]

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