Some modules stop responding/updating after monitor hotplug

[rhelmot]

NixOS 25.11
Waybar v0.14.0
swayfx version 0.5.3 (based on sway 1.11.0)

I have observed that, at least for the power-profiles-daemon module and the idle-inhibitor module, once I unplug or plug an external monitor these modules stop updating and interacting with them does nothing. Restarting waybar makes everything work fine again.

Here are some relevant logs from unplugging a monitor, clicking on power-profiles-daemon, and then re-plugging it:

Feb 06 14:21:17 daisy waybar[618896]: [2026-02-06 14:21:17.682] [info] Bar removed from output: DP-6
Feb 06 14:21:17 daisy waybar[618896]: [2026-02-06 14:21:17.683] [error] g_bus_connection_close_sync failed(): The connection is closed
Feb 06 14:21:17 daisy waybar[618896]: [2026-02-06 14:21:17.685] [info] Bar removed from output: DP-7
Feb 06 14:21:17 daisy waybar[618896]: [2026-02-06 14:21:17.843] [info] Bar configured (width: 1536, height: 32) for output: eDP-1
Feb 06 14:21:17 daisy waybar[618896]: [2026-02-06 14:21:17.848] [info] Bar configured (width: 1920, height: 32) for output: eDP-1
Feb 06 14:21:26 daisy waybar[618896]: [2026-02-06 14:21:26.220] [error] Failed to set the active power profile: The connection is closed
Feb 06 14:21:36 daisy waybar[618896]: Unable to replace properties on 0: Error getting properties for ID
Feb 06 14:21:36 daisy waybar[618896]: Unable to replace properties on 0: Error getting properties for ID
Feb 06 14:21:36 daisy waybar[618896]: Unable to replace properties on 0: Error getting properties for ID
Feb 06 14:21:38 daisy waybar[618896]: [2026-02-06 14:21:38.857] [error] Failed to create the power profiles daemon DBus proxy: Error calling StartServiceByName for net.hadess.PowerProfiles: The connection is closed
Feb 06 14:21:38 daisy waybar[618896]: [2026-02-06 14:21:38.857] [error] Failed to create the power profiles daemon DBus proxy: Error calling StartServiceByName for net.hadess.PowerProfiles: The connection is closed
Feb 06 14:21:38 daisy waybar[618896]: [2026-02-06 14:21:38.861] [info] Bar configured (width: 1920, height: 32) for output: eDP-1
Feb 06 14:21:38 daisy waybar[618896]: [2026-02-06 14:21:38.863] [info] Bar configured (width: 1920, height: 32) for output: eDP-1
Feb 06 14:21:38 daisy waybar[618896]: [2026-02-06 14:21:38.864] [info] Bar configured (width: 1920, height: 32) for output: eDP-1
Feb 06 14:21:38 daisy waybar[618896]: [2026-02-06 14:21:38.890] [info] Bar configured (width: 1536, height: 32) for output: eDP-1
Feb 06 14:21:38 daisy waybar[618896]: [2026-02-06 14:21:38.892] [info] Bar configured (width: 1920, height: 32) for output: DP-7
Feb 06 14:21:38 daisy waybar[618896]: [2026-02-06 14:21:38.893] [info] Bar configured (width: 1920, height: 32) for output: DP-6
Feb 06 14:21:38 daisy waybar[618896]: [2026-02-06 14:21:38.916] [info] Bar configured (width: 1920, height: 32) for output: DP-7
Feb 06 14:21:38 daisy waybar[618896]: [2026-02-06 14:21:38.918] [info] Bar configured (width: 1920, height: 32) for output: DP-6
Feb 06 14:21:42 daisy waybar[618896]: Unable to replace properties on 0: Error getting properties for ID
Feb 06 14:21:42 daisy waybar[618896]: Unable to replace properties on 0: Error getting properties for ID
Feb 06 14:21:42 daisy waybar[618896]: Unable to replace properties on 0: Error getting properties for ID
Feb 06 14:21:42 daisy waybar[618896]: Unable to replace properties on 0: Error getting properties for ID
Feb 06 14:21:42 daisy waybar[618896]: Unable to replace properties on 0: Error getting properties for ID

Looks like some socket gets closed and needs to be re-opened?