Hi everyone, below you will find the updates from the Desktop team from the last week.
If you’re interested in discussing a topic please start a thread in the Desktop area of the Community Hub (this site).
We also have our weekly meeting on IRC. We meet on Tuesday at 13:30 UTC in #ubuntu-desktop on Freenode. There will be an “Any Other Business” section at the end where you are welcome to raise topics. These topics might be discussed during the meeting, or afterwards depending on the time, depth of conversation, topic and so on.
Last week’s notes are here: Monday 10th December
Next week’s notes are here: Monday 24th December 2018 🎄 🎅
This was a short week, I was offline on Friday.
- 64.0 was released as a stable update to all supported series (trusty, xenial, bionic, cosmic, disco)
- updated dev to 72.0.3626.14
- updated beta to 72.0.3626.17
- prepared stable update to 71.0.3578.98
- fixed s390x autopkgtest failures (bug #1808147) and backported to cosmic
bug #1754671 in network-manager: @willcooke’s testing is conclusive, we agreed to upload to bionic-proposed and leave it there for (at least) the duration of the Xmas break to give it wider and in-depth testing
bug #1765304 in gnome-shell: verified (by myself and others)
bug #1802208 in libreoffice: no progress this week
bug #1765304 in gnome-shell: in unapproved queue, but the bug doesn’t really affect cosmic anyway
bug #1803142 in libreoffice: was accepted in cosmic-proposed, but I had to do another upload to fix autopkgtests on s390x, so back in the unapproved queue
was a bit of a short week, since I was off on Friday
rls: I do have bug #1805857 assigned, which I didn’t work on this week. Looks like 1.12.6 didn’t fix it, so still something to do here. That’ll be one of my tasks before xmas.
- Still progressing on PR #6258. It is mostly done, but needs review.
- While updating the tests to use a confined client app so they could function on Ubuntu Core, I discovered activation triggered by confined apps was broken on 18.04+. I initially tried fixing this with a change to the AppArmor rules, but @jdstrand instead pointed me at the
AssumedAppArmor key that can be placed in D-Bus service files.
- I came up with some ideas to fix up the incompatibilities with 14.04, which I’m testing at the moment. If those are acceptable, it should get rid of the question about Trusty support.
snapd desktop portal testing
- At the moment, all of snapd’s tests for portal support run against a fake version of xdg-desktop-portal, or a filesystem hierarchy that resembles that provided by xdg-document-portal. It doesn’t test behaviour against the real thing.
- I started PR #6313 to address this. The idea is to test against the real xdg-desktop-portal and xdg-document-portal with a fake UI service. This allows testing of things like the portal file chooser API without trying to drive a GUI from the test harness.
- The plan is to only run the test on a few systems where we know portals should work. As we SRU portals to older Ubuntu releases, we can expand the list of systems to verify that they work with snaps.
snap application polkit support
- A while back Ken asked me to look at what would be needed to allow snapped daemons to make use of polkit authorisation (e.g. for things like fwupd).
- I started a thread on the forum outlining what I think is needed. The main open question is whether namespacing polkit action IDs to a snap is acceptable. Without namespacing, it is not clear we can safely let snaps install new
- At present, the forum thread is the extent of my work on this: it was a task to look at after sorting out dbus activation / shell search providers.