** Changed in: canonical-devices-system-image
Milestone: u8c-1 => p2
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtubuntu in Ubuntu.
https://bugs.launchpad.net/bugs/1662145
Title:
[regression] Some apps fail to
** No longer affects: qtubuntu
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to platform-api in Ubuntu.
https://bugs.launchpad.net/bugs/1662145
Title:
[regression] Some apps fail to start with [QPA]
** Tags added: unity8-desktop
** Tags removed: unity8-desktop
** Tags added: unity8-session-snap
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtubuntu in Ubuntu.
https://bugs.launchpad.net/bugs/1662145
Title:
> Also very important that those apps (toolkits) choose native Mir over
> X when both are available.
Qt isn't designed to make the choice itself, it expects to be told if either X
or Mir should be used.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
** Changed in: canonical-devices-system-image
Milestone: p2 => u8c-1
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtubuntu in Ubuntu.
https://bugs.launchpad.net/bugs/1662145
Title:
[regression] Some apps fail to
** Branch linked: lp:~ci-train-bot/webbrowser-app/webbrowser-app-ubuntu-
zesty-2504
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtubuntu in Ubuntu.
https://bugs.launchpad.net/bugs/1662145
Title:
[regression] Some apps
** Branch linked: lp:webbrowser-app/staging
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to platform-api in Ubuntu.
https://bugs.launchpad.net/bugs/1662145
Title:
[regression] Some apps fail to start with [QPA]
They should add mir, yeah. No need to replace unity8, necessarily [1].
[1] For the moment, plugging unity8 will make you uninstallable. This
is to prevent widespread use of that interface before we finish it. The
default set of core apps have an exception to this, though.
--
You received
Does that mean that apps that plug to the "unity8" iface should be
updated to plug to "mir" now?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to platform-api in Ubuntu.
https://bugs.launchpad.net/bugs/1662145
Title:
Agreed. I was just trying to highlight that an app that used to work as
Mir might now be run under XMir because we switched which interface we
look at.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to platform-api in Ubuntu.
Sure, it's important to offer both X and Mir sockets to all apps.
Also very important that those apps (toolkits) choose native Mir over X
when both are available.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to platform-api
Daniel, that may be because now we choose whether to use xmir or not
based on the presence of the 'mir' interface (used to be the 'unity8'
interface). Not all apps may plug into that interface.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
Further to comment #12, I've noticed in a few other bug reports people
are experiencing rendering glitches in Qt apps that should only happen
with Xmir. So we seem to have a problem with our own Qt apps incorrectly
choosing X(mir) when native Mir is available and should be used instead.
--
You
Seemed to have been fixed with develop rc_proposed but then the wifi
broke!
On 23 February 2017 at 15:53, Michael Terry
wrote:
> Is this still happening?
>
> --
> You received this bug notification because you are subscribed to Ubuntu
> Touch Developer Preview.
>
Is this still happening?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to platform-api in Ubuntu.
https://bugs.launchpad.net/bugs/1662145
Title:
[regression] Some apps fail to start with [QPA]
UbuntuClientIntegration:
The log file makes this look like an app that is exporting the unity7
interface as well as the unity8 one. But the snapd in zesty doesn't have
a unity8 interface. So we're starting it as a unity7 app. It is not
realizing this and trying to connect to Mir, even after we've setup XMir
for it.
--
I understand. Unfortunately we're hitting new launch failure bugs every
few days now. So the launch failure one logged days ago might not be the
same bug experienced today.
Regardless of bug status we just need to get the code back to a semi-
working state where apps will actually run, and then
This is not the original issue, but yesterday I switched the unity8 snap
to use a different, more standard path (/run/user/xxx/mir_socket) for
the socket.
So if testing against the u8 snap, please re-create your app snaps to
pull down the latest version of the desktop-launch script which will
** Description changed:
Zesty
unity8-session 16.04 396 canonical
devmode
Test Case
1. Open the app drawer
2. Launch an app (eg calculator)
Expected result
It starts successfully and the app works as expected
Actual Result
It
19 matches
Mail list logo