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 Discourse.
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: Desktop Team Updates - Monday 29th June 2020
snapd dbus activation support:
snapd PR #8860 (detect conflicts between snaps wanting to activate the same D-Bus service) has been merged.
snapd PR #8861 (add dbus-daemon config to find service activation files under
/var/lib/snapd/dbus-1) is still waiting for a second review sign off.
snapd PR #8943 (install D-Bus service activation files) is still sitting in draft state. At the moment the spread tests are failing on Ubuntu and Debian, but it looks like that should clear up once #8861 is merged and a new
core snap containing it is released to edge. I have also updated the PR to ensure service activation packages are correctly purged if snapd itself is removed.
- I wrote a spread test for Alan’s snapd PR #8699.
- I’ve still got some concerns about some things like the environment handling and the subprocess handling (the current code looks like it could result in userd creating an unbounded number of threads). Everything looks solvable though.
font support for snaps:
- I posted a prototype for a shared private fontconfig cache to the Snapcraft forum. The eventual goal would be for the various GNOME platform snaps to generate a fontconfig cache from fonts in
/usr/local/share/fonts that is guaranteed to be compatible with the platform snap’s fontconfig and freetype.
- On the application snap side, the best ideal approach would be to mount this cache to
/var/cache/fontconfig so that it would automatically be used by the default fontconfig configuration. There’s two main blockers for that:
desktop interface tries to mount the host system
/var/cache/fontconfig there, which we no longer consider desirable.
content interface can only mount to locations under
$SNAP_COMMON. We can’t work around this with layouts, since their mounts are ordered before the interface mounts. Ideally the content interface could mount to any directory a layout could.
- If we solve the above two snapd issues, we should be able to update the Snapcraft extensions to use the private cache. That would mean for many snaps a simple rebuild would be sufficient.
Short week again, had one day off. Last one of those, boo!
- britney migration: ran on stable series, found a crash bug! in the middle of debugging that now.
- new autopkgtest deployment: wrote a script to sync data over to the new host, so the old results will come across
- reviewed some code changes from Séb, Balint and others for ^- related items
- Did some initial actions related to Eoan’s end of life