mirror of
https://github.com/DeeJanuz/frametop.git
synced 2026-10-08 17:00:13 +02:00
DeeJanuzandClaude Opus 5.5
903abd75dd
While ft-floatd isn't running, the watchdog fired every 30 s for as long as the desktop ran, and each fire was two lines in the journal: the script's own and KWin's "Received D-Bus message is error" for the call that failed. That was about 5800 lines a day, for nothing: only starting ft-floatd again helps, and it reloads the script when it starts. ft-floatd starts from the session's autostart, and nothing restarts it. The script now says it once per outage, and the next reply clears that. Each fire after the first waits twice as long, up to 5 minutes, which also cuts KWin's line. A reply starts over at 30 s, so a lost reply is still polled again after 30 s. In the poll model: ft-floatd gone for 10 minutes went from 20 fires and 20 prints to 4 fires (after 30, 60, 120 and 240 s) and 1 print. A lost reply still recovers at 30 s. Two lost in a row, with no reply between them, now wait 30 and then 60 s. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>