thinfloe v4.3.0

New

• ThinFloe now shows its picture on thin clients and mini PCs with AMD processors and their built-in Radeon graphics (those with Carrizo or Stoney graphics, for example the HP t530 and t630 thin clients, and Ryzen 2000 series and newer, up to Ryzen AI): the image carries the graphics firmware for these processors. AMD graphics cards still get no firmware.

Changed

• The daily release check, the Upgrade tile and thinfloe-upgrade take releases from https://github.com/oposs/thinfloe/releases instead of tobi.oetiker.ch. Every file of an upgrade or a fresh install comes from one release, the newest when the write starts, and is checked against that release's SHA256SUMS; a release without a line for a file fails with "the release has no checksum for " before the stick changes, and a write this machine refuses anyway (a swapped stick, an internal disk, a mounted stick) says so before the release is read. A source entered by hand is used as given and still accepts the older <file>.sha256 checksum files.
• The menu header of a self-built image shows a version such as 4.2.0-dev+85034f2 (with .dirty when built from changed or new files), and such an image is offered the current release as an upgrade. A build outside a git checkout stops at once with "TF_VERSION ... is neither RELEASE (...) nor a dev version" unless TF_VERSION=X.Y.Z is given, and a RELEASE file that is not one line X.Y.Z stops it with "RELEASE must be one line X.Y.Z".
• A new stick no longer comes with ThinLinc settings for the owner's server: ThinLinc starts with its own defaults. Upgraded sticks keep the settings they have.
• An upgrade or a netboot now downloads about 493 MB instead of 611 MB. The running system keeps Intel WiFi firmware only in the version its driver loads, and has no drivers for DVB, TV tuner and radio cards, none for older AMD (radeon) graphics, and no CPU microcode files, which are applied from initrd.img at boot as before. During boot, before the system is loaded, drivers for data-centre network cards, Fibre Channel and SAS storage controllers, InfiniBand and network file systems (CIFS, Ceph, AFS, NFS) are no longer available.
• locale-gen and systemd-hwdb update no longer work on a running machine: the locale and hardware database sources are left out. The locales of /etc/locale.gen and the hardware database ship ready to use.
• A ~/wifi.yaml or ~/ethernet.yaml for another netplan version than 2, or with another renderer than networkd (for the file or for one connection in it), counts as written by hand even when the menu wrote it, and "Let the menu manage it" is not offered for it. Nor is it offered for a /wifi.yaml with more than three DNS servers, the limit the wired connection already had; when the menu wrote such a file, a change of the DNS servers says "/wifi.yaml has settings the menu cannot keep, so the DNS servers cannot be set for WiFi."
• In the Settings Screen tab, Apply is offered only once something has changed.
• In the Settings Status tab, a click on a part's name ticks it, and a note such as "no room" that does not fit its row is cut short instead of running into the next column.

Fixed

• After the monitor woke from power save, the keyboard of a fullscreen ThinLinc session could stop working: the keys went to the hidden menu behind it, where Tab and Enter could start Restart. A fullscreen window on top now keeps the keyboard when the menu opens its window again; beside a window that is not fullscreen, the menu still takes the keyboard as before.
• OxuLnk no longer shows its keyboard grab as "not working" and no longer logs "keyboard grab unavailable reason=compositor does not support shortcut inhibition": the session now lets a window switch the desktop's key shortcuts off.
• The image no longer contains the build and test scripts in /scripts.
• Programs that looked up a host name early in the boot, before un-dockerize.service ran, found no name server: the image shipped no /etc/resolv.conf. It now ships the link to systemd-resolved, and un-dockerize.service no longer stops systemd-resolved and makes the link again, which made lookups fail for a moment.
• A fresh install from the Upgrade screen or over SSH that is cancelled or fails before its first byte is written leaves the stick as it was instead of clearing its start, and the menu says "Cancelled before anything was written. The stick is as it was." Restart, Power off and Log out warn that the stick will not start, and "Stop writing?" says so, only once writing has begun; during an upgrade "Stop writing?" says "The stick still starts its current release."