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 searches for a desktop file for that appId, which it associates
with the process when it connects to Mir.
2. be only instance of a process with that appId running
The first point is there to ensure that every process which draws a UI must
have metadata associated with it, metadata like name, icon, etc, which the
shell requires to have app appear in launcher correctly. Alternative is the
current situation, where we have BAMF to heuristically match processes to
desktop files - which is undesirable.
The second point can be relaxed for desktop apps, but will probably be
maintained for phablet.
I'll try to determine if an app crashing correctly notifies QtMir, so
that if a new instance of it appears, QtMir will accept it. That's a
guess at the problem however, I'd need to reproduce.
** Summary changed:
- Qtmir aborts if it cannot connect to Mir
+ Qt app aborts if it cannot connect to Mir - QtMir rejecting the connection
** Also affects: qtmir
Importance: Undecided
Status: New
** Changed in: qtmir
Importance: Undecided => High
** Changed in: qtmir
Assignee: (unassigned) => Gerry Boland (gerboland)
--
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:
Qt app aborts if it cannot connect to Mir - QtMir rejecting the
connection
To manage notifications about this bug go to:
https://bugs.launchpad.net/qtmir/+bug/1422797/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
