Found by verifying the previous release on a real desktop, then fixed and re-checked with drop-ins before the build:
- Two NTP clients. Buildroot builds systemd-timesyncd by default and nothing turned it off next to chrony,
which the spec already chose. chronyd logged "System clock interference detected" every few minutes. timesyncd
is out of the core layer, and an
ntp-units.dentry pointstimedatectl set-ntpand COSMIC's automatic-time switch at chrony, so those controls still work. - The hostname got renamed on every boot. avahi kept appending
-2,-3,-4to the machine's name with no other device using it, because systemd is built withdefault-mdns=yesand resolved was advertising the same name on :5353. resolved now only resolves.locallookups and avahi is the only advertiser. - VS Code opened with "Unable to watch for file changes". The kernel sizes
fs.inotify.max_user_watchesfrom RAM, which is 137,830 on a 14 GB machine. The Desktop sets 524,288. - The portal logged "error loading system light theme" at every start, and the accent colour fell back to
stock. The shipped theme files were missing two keys the pinned libcosmic reads. They're there now, and
list_buttonwas computed from the same libcosmic and builder input that reproduces the shippedlink_buttonandaccent_buttonbyte for byte, rather than guessed at.
On the build side: pengyos-build gained a leftovers pass that names files in the build output no installed
package claims any more, and it rebuilds a package whose recipe changed after it was built. Both are about the
same failure mode, which is an image quietly carrying something from three builds ago.