[Bug 1685186] Re: [SRU] Mir needs to be updated to 0.26 in 16.04LTS
Launchpad Bug Tracker
1685186 at bugs.launchpad.net
Sun May 28 13:18:03 UTC 2017
This bug was fixed in the package mir - 0.26.3+17.10.20170526.3-0ubuntu1
---------------
mir (0.26.3+17.10.20170526.3-0ubuntu1) artful; urgency=medium
[ Daniel van Vugt ]
* New upstream release 0.26.3 (https://launchpad.net/mir/+milestone/0.26.3)
- Enhancements:
. Make deprecations optional (and default to off for builds on 16.04 LTS)
. Added support for building on Ubuntu 17.10 artful.
- Bugs fixed:
. Mir needs to be updated to 0.26 in 16.04LTS (LP: #1685186)
. unity-system-compositor crashed with SIGSEGV in
libinput_device_config_accel_is_available() from
libinput_device_config_accel_set_speed() from
mir::input::evdev::LibInputDevice::apply_settings() (LP: #1672955)
. Please transition to Boost 1.62 (LP: #1675138)
. Mir sending key repeat events continually to nested shell after VT
switch (causes Unity8 lockup for a while) (LP: #1675357)
. mir_demo_standalone_render_overlays fails to link (LP: #1677239)
-- Alan Griffiths <alan.griffiths at canonical.com> Fri, 26 May 2017
16:57:20 +0000
** Changed in: mir (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1685186
Title:
[SRU] Mir needs to be updated to 0.26 in 16.04LTS
Status in mir package in Ubuntu:
Fix Released
Status in mir source package in Xenial:
Incomplete
Bug description:
[Impact]
Snap development using Mir has been using the "stable phone overlay" PPA which is both inconvenient and a legacy of the cancelled Unity8 project.
It would greatly simplify things if Mir were updated in the Xenial
archive.
[Test Case]
Build a Mir client snap (e.g. lp:~albaguirre/+snap/mir-client-demos)
against "Primary Ubuntu Archive" and deploy as described in
https://developer.ubuntu.com/en/snappy/guides/mir-snaps/
Expected: the client apps start and are visible on screen
Actual: the client apps don't start and are not visible on screen
[Regression Potential]
Mir has two categories of dependent project:
1 Unity8 and unity-system-compositor "server" packages
2 toolkits and other "clients" of Mir
"Server" packages from the archive will stop working in the LTS as
they will continue using the earlier libmirserver.so.38 (from Mir
0.21) which doesn't work with the libmirclient.so.9 from Mir 0.26.
This is unimportant as these packages were provided as an "early
experience", not for serious use.
"Client" packages are dependent only on libmirclient.so.9 which is ABI
stable. The principle type of regression would be FTBFS where APIs
have been deprecated in 0.26. The linked 0.26.3 release has these
deprecations disabled for 16.04.
The packages are available in silo:
https://bileto.ubuntu.com/#/ticket/2736
notes:
A recursive search or rdependencies identifies the following packages
in category 1:
camera-app-autopilot
gallery-app-autopilot
indicator-network-autopilot
indicators-client
qtdeclarative5-qtmir-plugin
qtmir-android
qtmir-desktop
qtmir-tests
ubuntu-desktop-mir
ubuntu-experience-tests
ubuntu-pocket-desktop
ubuntu-push-autopilot
ubuntu-touch
ubuntu-touch-session
unity8
unity8-autopilot
unity8-desktop-session-mir
unity-scope-click-autopilot
unity-system-compositor
unity-system-compositor-autopilot
Anyone wanting these packages should switch to the "unity8-desktop-
session" preview package in 17.04 where they are far more functional.
[Alternatives]
If we want to keep everything working in Xenial, we *could* bump the libmirclient SONAME to libmirclient.so.10. This would result in libmirclient9 being NBS, but continuing to work against the Mir servers available in 16.04[*] (until and unless they are rebuilt).
However, this does not enable the desired result for IoT deployments
of toolkits (GTK, Qt etc) and other clients working against servers
(specifically miral-kiosk) built against the updated libraries.
To work for IoT these would need to rebuilt from source - at which
point they (and their dependencies) would stop working against the
servers in category 1.
[*] with the exception of the servers provided in mir-examples, these
would only work with clients linking against libmirclient.so.10.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1685186/+subscriptions
More information about the Ubuntu-sponsors
mailing list