5.1.8 is a bug-fix release that gets minimize-to-tray working inside the Flatpak sandbox (flathub#79).
On the Flatpak the minimize-to-tray switch was greyed out with "No system tray was detected on this desktop" even on desktops that do run one, and granting the missing D-Bus permission by hand still produced no icon. Two separate things were wrong. The packaging never granted access to the org.kde.StatusNotifierWatcher name, so the tray host was invisible to the app; that is fixed in the Flathub manifest. And the tray insisted on owning org.kde.StatusNotifierItem-<pid>-1, a well-known bus name the sandbox refuses, then gave up when the request came back ServiceUnknown. It now registers with the tray host under its unique connection name instead, which needs no permission at all and is what Qt applications have done for years.
Fixes
- FIX: no tray icon appeared in sandboxed builds even with a tray host present, because the session bus refused the process-derived
org.kde.StatusNotifierItem-<pid>-1name and the tray tore itself down instead of falling back. The item is now registered under the unique bus connection name whenever the well-known one cannot be had, so the icon appears regardless of what the sandbox grants (flathub#79) - FIX: two sandboxed applications could not both show a tray icon. Every Flatpak process sees itself as pid 2 under
bwrap --unshare-pid, so their process-derived StatusNotifierItem names collided and whichever lost the race silently got none. Both now get an icon (flathub#79)
Packaging
- PACKAGING: the Flatpak lacked the D-Bus permissions that the tray and Auto-Lock need.
--talk-name=org.kde.StatusNotifierWatcherun-greys the minimize-to-tray switch, and the screensaver names make Auto-Lock on screen lock work; both had been silent no-ops. See flathub/com.github.paolostivanin.OTPClient#80 - Nothing changed in the build or its dependencies, so distribution packagers have nothing to adjust for this release.
Known limitation
Auto-Lock on suspend does not work in the Flatpak and logs Could not subscribe to suspend events. It needs PrepareForSleep from org.freedesktop.login1 on the system bus, which Flathub's linter does not permit an application to request. Auto-Lock on screen lock does work, and most desktops activate the screensaver around a suspend, so the common case is covered. Native packages are unaffected.
sha256: 3b45538fdf962f273cc4c18ef9851416515dd1cc46829f2c7a02cba5ae99c0e1