Had Monday off for the WA Day public holiday. Enjoyed listening to The Waifs, plus watching the fireworks.
- More work laying the ground work for making the themes API available without snapd-control:
- With the
desktop-launch feature merged, there were some unit test failures showing up on 14.04. I helped diagnose the problem, but it was at the end of my work day mvo beat me to fixing it with snapd PR #10337.
snapd dbus activation:
- I updated snapcraft PR #3425 (add support for the
activates-on syntax to Snapcraft) to pass CI with current snapcraft master.
- While following up on the above, the question came up about whether review-tools supported the new syntax. It turned out there was an implementation of the snap.yaml syntax we decided not to use, so I’ve been working on PR to update that. Still working through the associated test changes, but should have the proposal ready tomorrow.
Fcitx 5 snap compatibility:
@gunnarhj ran into some compatibility problems between the new version of the Fcitx input method framework and snapped applications, with the discussion recorded in bug #1928360. The new version claims to provide compatibility with Fcitx 4’s IPC system, but we couldn’t get it to activate in the module in Chromium.
- It turns out the problem is that they renamed the GTK IM module to
im-fcitx5.so. That module doesn’t exist in any of our platform snaps, and they won’t use the available
im-fcitx.so due to the name mismatch. Explicitly running Chromium with
GTK_IM_MODULE=fcitx allowed it to talk to fcitx5.
- The end result is that we need to include the new module in our platform snaps. Doing so for
gnome-3-38-2004 is not too difficult, since there is a packaged version of the IM in Ubuntu 20.04. Doing so for older releases might mean building it locally. It doesn’t look like we can just symlink the modules, since it looks up the extracted module name in