Skip to content

Rearm idle monitor after timeout changes - #9570

Open
rookepoole wants to merge 1 commit into
omacom:quattrofrom
rookepoole:fix/rearm-idle-monitor
Open

Rearm idle monitor after timeout changes#9570
rookepoole wants to merge 1 commit into
omacom:quattrofrom
rookepoole:fix/rearm-idle-monitor

Conversation

@rookepoole

Copy link
Copy Markdown

Summary

Re-arm Quickshell's IdleMonitor when a live shell.json edit changes the effective first idle timeout.

Changing idle.screensaver or idle.lock updates the QML timeout immediately, but affected Quickshell sessions can leave the underlying Wayland idle notification silent. The shell then reports the new values while screensaver, lock, and display-idle events never fire until a restart.

The idle service now pulses the monitor off for 150 ms and declaratively re-enables it with the new timeout. This spans the event-loop delay validated in the issue reproduction, remains gated by Stay Awake, coalesces rapid edits by restarting the one-shot timer, and exposes the re-arm state in idle diagnostics.

Closes #9496

Test plan

  • bash test/shell.d/idle-test.sh
  • /usr/lib/qt6/bin/qmllint -I /usr/lib/qt6/qml -I shell shell/plugins/services/idle/Service.qml (only existing QProcess::ExitStatus import warnings)
  • ./test/shell (changed test passes; suite retains five unrelated baseline failures: three require an omarchy-pkgs checkout, plus the existing launch-about and network-QR assertions)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

1 participant