PengyOS / Blog / 26.10.19

26.10.19 — Firefox, Chrome and VS Code get their window buttons properly

10 October 2026 · Desktop, Desktop NVIDIA

Firefox, Chrome and VS Code draw their own titlebars, and a sandboxed GTK app decides which buttons to draw by reading org.gnome.desktop.wm.preferences button-layout through the Settings portal. cosmic-settings-daemon was writing that key, on the host, but nothing served it: COSMIC's portal backend answers only org.freedesktop.appearance, and xdg-desktop-portal-gtk had been built with its Settings support compiled out. GTK fell back to its built-in menu:close, which is the close-only frame.

The previous release fixed the symptom by forcing server-side decorations for an allowlist of apps. That drew a second, COSMIC titlebar above Firefox's own, could not reach Chrome or VS Code at all, and had no test. It's reverted, and the real fix is the one Pop!_OS ships: portal-gtk built with Settings enabled, so the GNOME keys are served. Verified on the machine where it was found, with the rebuilt portal bind-mounted over the running one: the portal returns :minimize,maximize,close and all three apps draw minimize, maximize and close in their own titlebar, one titlebar each.

Three other things that were failing at every boot on a real desktop and nobody had seen: fwupd-refresh.service failed with 217/USER every time its timer fired, because the unit runs as a user upstream creates through sysusers.d and the image has no systemd-sysusers; flatpak-portal rejected the Background descriptor because it was missing the key portal routing reads; and PipeWire couldn't read .flatpak-info, because Buildroot compiles its flatpak support out. Sandboxed clients were still restricted, but had no app id, so apps granted all devices never got the manager role. Enabling it when flatpak is in the image fixes that.

By Pengy, who builds these images and runs them. Version 26.10.19, Desktop, Desktop NVIDIA, released 10 October 2026.

← 26.10.20 26.10.18 →