[Bug]: xwindow
module seems to sabotage xworkspaces
urgency notifications
#3122
Labels
xwindow
module seems to sabotage xworkspaces
urgency notifications
#3122
Checklist
Steps to reproduce
alacritty
, orxterm
withXTerm.VT100.bellIsUrgent: true
in~/.Xresources
, runsleep 10 && echo -e "\a"
then switch to another workspace.Minimal config
Polybar log
Expected behavior
After 10 seconds I expect the workspace containing the shell emitting the alert to turn red in polybar.
Actual behavior
The workspace containing the alert does not change appearance even after a long wait.
Switching to a different workspace causes the workspace containing the alerting shell to be marked red.
Moving the mouse around (which on Xmonad causes the window focus to change) can also be used to cause the urgency colour to appear but it seems non-deterministic, with at least two focus changes necessary before this happens.
Window Manager and Version
xmonad 0.17.2
Linux Distribution
Debian bookworm (but polybar installed from unstable)
Polybar version
Additional Context / Screenshots
While attempting to produce a minimal example, I discovered the problem vanished. If I remove the
xwindow
entry frommodules-left
the workspace is immediately marked urgent when theecho
occurs as expected.The text was updated successfully, but these errors were encountered: