Skip to content

Recover screen-recording indicator after stuck probes - #9296

Open
fresh3nough wants to merge 1 commit into
omacom:quattrofrom
fresh3nough:fix/issue-9205-screenrecord-indicator
Open

Recover screen-recording indicator after stuck probes#9296
fresh3nough wants to merge 1 commit into
omacom:quattrofrom
fresh3nough:fix/issue-9205-screenrecord-indicator

Conversation

@fresh3nough

Copy link
Copy Markdown

Summary

Fixes #9205.

ScreenRecording.qml polls with a one-shot Process (pgrep). refresh() returns early while statusProc.running is true. If onExited never fires cleanly (abrupt recorder kill, handler glitch, etc.), that flag stays true forever — no further probes run and the bar icon freezes on "recording" even when no gpu-screen-recorder process exists. Workaround was omarchy restart shell.

Change

  • Arm a 2s watchdog when a probe starts; if still running, force statusProc.running = false and refresh again.
  • Add a 2s poll timer so kills that skip omarchy-capture-screenrecording's indicator toggle still update the bar.

Test plan

  • Static contract: watchdog + poll + stuck-clear path present
  • Existing screenrecording-test.sh still passes
  • Verified on GCP VM
./test/shell.d/screenrecording-indicator-test.sh
./test/shell.d/screenrecording-test.sh

refresh() skipped work while statusProc.running was true. If onExited never
fired after an abrupt gpu-screen-recorder death, the Process stayed "running"
forever and the bar icon froze on the last state. Watchdog-clear stuck probes
and poll every 2s so abnormal kills are noticed without a shell restart.

Fixes omacom#9205

Signed-off-by: fresh3nough <anonwurcod@proton.me>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Screen recording bar indicator gets stuck 'active' after a stopped/crashed recording

1 participant