The 26.10.18 fix for apps that draw a close button and nothing else was still working, but on a fresh
install it stopped applying. cosmic-settings-daemon writes four GNOME keys at login as four
concurrent gsettings set processes. Without dconf, GSettings falls back to its keyfile backend, where
every writer rewrites the entire file, so the writes race. On a fresh Desktop NVIDIA install the two
font keys survived and button-layout and icon-theme were lost. Reproduced on the build host: 6 of
50 runs lost the button layout. Machines whose keyfile happened to keep the key were never affected,
which is why it looked random.
Two changes. The Desktop's gschema override now sets COSMIC's own values as the defaults,
:minimize,maximize,close and the Cosmic icon theme, so a lost write no longer changes anything, and a
test compiles that override against the real schemas with --strict and reads the keys back (the
26.10.18 fix had no test at all, which is how it regressed). And the Desktop editions now ship dconf
51.0, the GSettings backend GNOME, Pop!_OS and Ubuntu use: writes are applied in order. A user unit
loads the old keyfile into dconf on the first login after the update and renames the file, so settings
you made by hand carry over rather than silently reverting.
Two build-side fixes that would have bitten later: published release files are written with umask 022, because a manifest the web server can't read is an update that doesn't arrive; and the iwlwifi firmware pruner now keeps everything when a driver names firmware that doesn't exist in the Linux tree, instead of quietly deleting firmware a card needs.