QtMir has strict policy that every app that tries to connect to Mir
must:
1. either be launched via upstart-app-launch [unsupported hack: launched
with --desktop_file_hint=/path/to/desktopfile.desktop]. Upstart notifies
QtMir that a process with a particular appId is about to start. QtMir
then sea
** No longer affects: autopilot
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1422797
Title:
Qtmir aborts if it cannot connect to Mir
To manage notifications about this bug go to:
https://bugs.laun
like dobey said, if you just run qmlscene you can see the result
phablet@ubuntu-phablet:~$ qmlscene
[1424984233.100272] Loader: Loading modules from:
/usr/lib/arm-linux-gnueabihf/mir/client-platform/
[1424984233.101127] Loader: Loading module:
/usr/lib/arm-linux-gnueabihf/mir/client-platform/mes
renamed based on discussion with dobey
can we make Qtmir log a message with qCritical() and exit with
QApplication.exit()
** Summary changed:
- Mir refuses the app to connect
+ Qtmir aborts if it cannot connect to Mir
** Changed in: qtmir (Ubuntu)
Status: Invalid => New
** Changed in:
