Desktop Team Updates - Monday 28th October 2019

Desktop Team Updates
1

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 Update - Desktop Team Update - Monday 21st October 2019

3 Likes
2

:computer_mouse: Gnome Shell:

:hammer_and_wrench: Other:

:beetle: Release bugs and friends:

:chart_with_downwards_trend: Backlog tracking

1 Like
3
  • Reviewed internal doc
  • stats
  • Reproduced swap on zvol bug
4

Short week - away Wednesday to Friday.

libreoffice24-margin libreoffice

  • The usual dose of bug triaging & USN refreshes.
  • Earned Per-Package Upload rights :slight_smile:

Snapcraft snaps

:clipboard: other

  • Became an official Ubuntu Member!
4 Likes
5

ZSYS:

  • Investigated and fixed this annoying bug by providing backward compatibility. Uploaded to Focal, in unapproved for 19.10.
  • Separate zsys as daemon/server, with a grpc protobuf definition for existing calls. Factor as much as possible the code there so that new calls are pretty easy to add (basically, add to the protobuf file, generating code with will have logs handled automatically or not).
  • Many shell completion and argument requirement investigations. Reported a detailed upstream cobra bug and worked on a PR to enhance shell completion. Adapted some workaround in the meantime on ZSYS. Will adapt shell completion to it as well.
  • Investigated why zsys upstream CI tests are broken. This is only with 1.14 (dev release). go master is breaking go-cmp google package.
  • Work on 19.10 feedback and bug triaging
  • Proposed ZSYS planning for 20.04
2 Likes
6
  • autopkgtest week
    • Got IS to fix the remaining blockers, staging is now good to test with and I ran some test tests.
    • Various improvements to the Mojo spec / charm
    • RabbitMQ has been falling over under the load a little bit. Talked with apw about some tweaks that we could do there and tried them, seems to help a bit. The big improvement should come when we re-deploy and get bionic’s version.
    • Talked with IS about how to do monitoring so that at some point we can add a lot of metrics to it
  • Had a release retrospective call with the people who were there last week, discussed some possible improvements and bugs to follow up on.
  • Review and updates for mutter / gnome-shell
7
  • Travelled to London to review the desktop plans for next cycle and do some handover with Will&Martin
  • Verified some SRUs which were waiting for a while (nautilus/disco, pulseaudio/disco, gnome-settings-daemon/disco)
  • Launchpad bugs & e.u.c triaging post release
  • Updated some cards on the trello board, please review your items before we start the new cycle
  • Sponsored the new bluez version from Daniel to focal
  • Switched the ubuntu-desktop-versions vcs to git, did some tweaks/fixes on the way
8

firefox24 firefox

  • prepared 70.0+build2 update
  • updated symbolic icon to match the latest firefox brand update

thunderbird24 thunderbird

  • preparing update for 68.2.0+build1 in focal

chromium22 chromium

  • confirmed and fixed a number of regressions reported following the deb to snap transition in eoan:
    • bug #1849160 (after deb->snap transition, chromium no longer sees local password store): fixed in focal, uploaded SRU to eoan and validated it
    • bug #1849105 (cannot pause video with bluetooth headset buttons any more): fixed in the snap
    • bug #1849163 (after deb->snap transition, chromium loses desktop keybinding theme): fixed in the snap
  • followed up on auto-connection request for personal-files, added back the change to stable, and backported to beta and dev branches
  • started discussion about snapd being killed while installing chromium in test environments − it turns out this is a known bug, and a fix has been committed
  • added the output of snap changes --abs-time chromium to the apport hook for chromium-browser in focal, and backported to the eoan branch
  • updated stable to 78.0.3904.70
2 Likes
9
  • ippusbxd: Merged two pull requests from David Valleau from Google (Chrome OS), one for improving tthe efficiency of the list_service_threads() function and another for code style fixes. Also put up an idea as a feature request, namely, making ippusbxd allow parallel classic USB connections while it is running, for example for scanning on a multi-function device. David Valleau will look into this.
  • network-manager: Tested new Bionic SRU for Bug 1754671. The new SRU suggested only backports upstream fixes into 1.10.6 instead of upgrading to network-manager 1.10.14.
  • network-manager: Asked the reporters of the regressions in the old Bionic SRU (Bug 1829838, bug 1829913) whether the new SRU will not cause these regressions.
  • Google Code-In 2019: Added project contact info and lined up sample tasks on the Linux Foundation’s GCI page, also proofread and corrected sample tasks of other contributors. Now everything for the GCI application is complete. Deadline was today and announcement of accepted mentoring organizations is tomorrow.
  • Bugs.
10
  • tested and merged build snap contribution
  • some administrivia: setup weechat, subscribe to forum topics
  • build snap: dove into librsvg issue and determined that 3c0de55f on librsvg is the turning point where builds start to fail. The problem is that we want to use the newest librsvg-2.46 branch but are stuck on librsvg-2.44 until can build with librsvg-2.46. This is the only project in the build snap that hasn’t been updated from gnome-3-32-1804-sdk and the gnome-3-34-1804-sdk is in the edge channel, but use at your own risk :slight_smile:
  • made a gnome-3-34 extension and have been debugging issues with it using evince and gnome-clocks. This is where most of my time went, troubleshooting and fixing linking issues, path issues, you name it. Thanks @kenvandine @marcustomlinson and @sergiusens for all the help on the extension! We now have an extension that gnome-calculator, evince, and gnome-clocks can build with although there are still kinks to work out.

W44 plans:

  • add tests to snapcraft to cover the new gnome-3-34 extension
  • merge extension changes and extension tests
  • review snapcraft docs in detail and propose any changes that would help a reader use the new extension
  • write a blog post about the extension on snapcraft blog (draft in hands of advocacy team by the end of the week)
1 Like
11
  • Short week due to public holidays.
  • Reviewed gnome-control-center MRs.
  • Refactoring g-c-c network panel.
12

GNOME

  • Some more reviews on Daniel’s CLUTTER_ACTOR_NO_LAYOUT MR
  • Some upstraem cherry-picks to stable branches
  • Use gjs’ smarter GTypeName computation on shell [MR]
  • Updates to gjs MR to hide symbols by default [MR]
  • Lots of debugging on shell’s crash when using some java IDEs and found the fix [MR]
  • Some further analisys on fingerprint work

Packaging

  • Prepared snapshot upload for mutter and gnome shell [MR + extra-fix + MR]
  • Bugs SRUization (thanks laney for backporting to eoan)
  • Rebased gnome-shell, gnome-software and nautilus to latest version to support XUbuntuCancel method in Bionic, bileto ready for review.
1 Like
13
  • Tested final 19.10 Hyper-V images, which have now been published on partner-images. Still working to get Microsoft to publish it in their gallery.
  • Debugging crash in snaps using the gnome-3-32-1804 platform. Found the same is true if using gnome-3-34-1804
  • Helped with the gnome-3-34 snapcraft extension and successfully built several snaps using it. They all suffer from the above crasher though
  • Reviewed some interesting snapcraft PRs which further improve startup time
  • Focal image builds started failing, discovered there was some inconsistency with the seed validation in snapd which didn’t behave properly with seeded snaps that were built with the snapcraft extension. Submitted PR to snapcraft with a fix for both gnome-3-28 and kde-neon extensions. Snapd still looking at fixing the validation tools, but currently the pressure is off.
  • USN Refreshes
1 Like