This will be solved basically in two parts:
1. Xmir will only launch when it needs to. The DISPLAY env var will be set and
some method of detecting when Xmir is needed will be used. There are a couple
of ways of starting Xmir on-demand and just picking one that will work both
with deb based systems and the future Xmir snap will be key.
2. Any toolkits that support Mir will need to try use Mir first before trying
to use X. It was recently discovered that, even though Qt apps are being told
to use Mir, if Xmir is available and DISPLAY is set, it will use X which is a
bug. Also, Gtk will need to be patched to try to use Mir first.
I will work on the libertine/ubuntu-app-launch part of this to make it
so Xmir will start only when needed.
** Changed in: libertine/devel
Status: Triaged => In Progress
** Changed in: libertine/devel
Assignee: (unassigned) => Christopher Townsend (townsend)
** Changed in: ubuntu-app-launch (Ubuntu)
Status: Confirmed => In Progress
** Changed in: ubuntu-app-launch (Ubuntu)
Assignee: (unassigned) => Christopher Townsend (townsend)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1672931
Title:
[regression] Qt & GTK apps on Unity8 are defaulting to Xmir instead of
native GTK/Qt (and so menus don't appear in the titlebar)
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1672931/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
