Two Xbox pads, bonded, connected, ServicesResolved=true, a battery percentage in the Bluetooth
applet, blinking LEDs, and no input device anywhere. The daemon had been built --disable-hid
--disable-hog, because Buildroot makes every BlueZ profile an opt-in sub-option and nobody had opted
in. A Bluetooth LE HID device pairs, bonds, resolves its GATT service and stops there: no uhid
device, no hid-generic/hid-microsoft binding, no /dev/input/event*. The pad only stops blinking
once the host holds it as a HID device, so it blinks forever. The battery number you could see came
from the pad's stub GATT characteristic, not the report the pad actually uses. A Bluetooth mouse was
equally dead, with no wired fallback to blame. The kernel side had been right and tested for weeks;
the missing half was one userspace option. The Desktop now enables BlueZ's HID, HoG, SixAxis and
tools options, which also covers the DualShock 3, whose descriptor the kernel can't use on its own.
Getting there took a diagnosis through D-Bus because the image shipped no bluetoothctl, no btmon,
no hcitool. Those are installed now, and bluetoothctl works as the desktop user without sudo.
The class of bug is the point. check-kernel-fragments.py exists because Kconfig silently drops
options; the userspace half had no equivalent. scripts/check-daemon-features.py now runs from the
Desktop post-build and fails the build when a claim stops holding: bluetoothd carries the HID/HoG
and sixaxis code, the Bluetooth tools exist, /dev/uinput and the joystick udev rule are in place,
cupsd and ipp-usb are there, the RGB rule is there. Ten tests keep that honest, including one that
keeps the features file parseable so the guard can't rot into prose.
Two other things in this release:
- OpenRGB works when you install it. The kernel was ready but
/dev/i2c-Nisroot:root 0600, so OpenRGB installed as a Flatpak or AppImage listed no motherboard, no RAM, no GPU, and blamed a missing driver. A udev rule grants the seat access to the i2c-dev nodes and the Super I/O port device. Deliberately not a blankethidrawgrant: a keyboard's hidraw node is keystroke-readable. - Desktop images stopped carrying the build host's libraries. 25 libraries were being copied
unchanged from the build host's Ubuntu packages, at whatever patch level the host happened to have
that day, and none of them were visible to the CVE scan or the SBOM. cosmic-store had a private
/usr/lib/compatholding Ubuntu's OpenSSL and curl behind a wrapper; the Store runs on the image's own now, verified by installing something from Flathub under QEMU. Thelddcopy loop that pulled in Kerberos, OpenLDAP, SASL, libssh2, brotli and the rest is gone.libdisplay-info, which parses every monitor's EDID, is built from a pinned fork of upstream 0.3.0 (0.4.0 is soversion 4, which cosmic-comp's crate refuses), and it carries our own fix for CVE-2026-112271: a crafted EDID from a monitor, KVM or capture device read past the buffer inside cosmic-comp. Upstream has no fix for that one yet, and NVD lists no CPE for the library, so nothing had been matching it at all.