/usr/bin/dialer-app:6:qt_message_fatal:QMessageLogger::fatal:UbuntuClientIntegration::UbuntuClientIntegration:UbuntuMirClientIntegrationPlugin::create:loadIntegration

[errors.ubuntu.com bug bridge]

The Ubuntu Error Tracker has been receiving reports about a problem regarding dialer-app. This problem was most recently seen with version 0.1+15.10.20150615-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/d4b5f8e8e69986f28fd161d677a4cea7c76e4c7f contains more details.

Rank 4 on errors.u.c with an increased number of reports with 0.1+15.04.20151112.1-0ubuntu1

[Bill Filler (bfiller)]

from stacktrace it appears that connection to MIR server is being rejected for some reason. Looking at the "Examples" in the errors.ubuntu.com page, seems like the condition is when dialer is being invoked with url like "tel:///<phoneNumber>"

[Bill Filler (bfiller)]

Get the exact same stacktrace on this bug launching mediaplayer:
https://bugs.launchpad.net/ubuntu/+source/mediaplayer-app/+bug/1474106

pretty clear it's not an app specific bug, but a mir/shell issue.

[Jean-Baptiste Lallement (jibel)]

Moving to backlog and setting severity to medium, only 2 instances of this crash reported on recent builds.

[Daniel van Vugt (vanvugt)]

The stack trace does not contain any frames from Mir. Only Ubuntu platform code and Q-things.

[Daniel van Vugt (vanvugt)]

Actually, this looks like the kind of error you might get from any app/client if Unity8 freezes or deadlocks somewhere. And that kind of bug is just as likely to be in the Mir server itself.