Following the releases of Mir 2.16 and 2.13.1 Ubuntu Frame and Mir Kiosk have been updated in the following channels:
snap | channel | version |
---|---|---|
Ubuntu Frame | 22/candidate | 123-mir2.16.0 |
Ubuntu Frame | 20/candidate | 104-mir2.13.1 |
Mir Kiosk | latest/candidate | 2.13.1-snap139 |
There has not been (and will not be) any update to the latest
track for Ubuntu Frame. If you have Ubuntu Frame track latest
deployed, please switch to track 20
for the least disruption (or track 22
for the latest features). For details see PSA: Retiring the latest
tracks for ubuntu-frame*, graphics- and mir-test-tools (action required).
Ubuntu Frame track 22
The 22
track is the focus of ongoing development and contains the latest version of Mir: Mir Release 2.16.0
This contains a significant reworking of the graphics support. We expect systems with a single hardware graphics stack to be unaffected by these changes (but please verify this for your own systems). Existing deployments are likely to be in this category.
More complex systems (such as “hybrid graphics”) can be affected by the availability of support for more configuration may need configuration to specify the appropriate “display platform” and “rendering platform” configuration:
Platform | configuration key | Options |
---|---|---|
display | platform-display-libs |
Comma separated list from [mir:gbm-kms , mir:eglstream-kms , mir:x11 , mir:wayland , mir:virtual ] |
rendering | platform-rendering-libs |
A single item (currently) from [mir:gbm-kms , mir:eglstream-kms , mir:egl-generic ] |
Testing Ubuntu Frame track 22
To test, just switch to the candidate
channel. For example:
snap refresh --channel 22/candidate ubuntu-frame
And use as normal. Please let us know any results here.
Because of the significant changes to the Mir architecture in 2.16 we will allow an extended period for testing. If no problems are identified we aim to promote to stable
in two weeks.
Ubuntu Frame track 20 or Mir Kiosk
These contain a bugfix release of Mir 2.13:
- Unable to close miral-shell using keybind via VNC due to DecorationProvider (Fixes #3070)
- [input] keyboard meta key state gets out of step (Fixes: #2837)
- [platforms] Handle libinput device rejections better #2927
- [platforms] Assume evdev platform is supported (Fixes: #2837)
- [platforms] Fix naming of outputs on Nvidia cards (Fixes: #2968)
- server/ShmBacking: Fix leak in
install_sigbus_handler
(Fixes: #2895)
Unless affected by one of the above, you are unlikely to see any differences.
Testing Ubuntu Frame track 20 or Mir Kiosk
To test, just switch to the candidate
channel. For example:
snap refresh --channel 20/candidate ubuntu-frame
snap refresh --channel candidate mir-kiosk
And use as normal. Please let us know any results here.
If no problems are identified we aim to promote to stable
in a week.