On Wed, Jun 25, 2025 at 05:59:14AM +0000, Alexander Huemer wrote:
> Hi!
> 
> Occasionally (perhaps once every two months or so) I run into the 
> situation that one of my urxvt windows makes itself 'ugrent' and is 
> stubborn about it. I believe this coincides with an ssh connection that 
> was established from that window getting killed by the laptop going to 
> sleep and then being woken up again. It's perfectly correct that the 
> window does the urgent thingy, but after baining focus, it should reset 
> that bit... but it doesn't.
> When a urxvt window get into that state, the shell that lives inside it 
> works normally.
> How do I debug this?
> 
> This is of an affected window:
> 
> $ xprop -id 0x40aa36
> WM_STATE(WM_STATE):
>               window state: Normal
>               icon window: 0x0
> _NET_WM_PID(CARDINAL) = 1159
> WM_PROTOCOLS(ATOM): protocols  WM_DELETE_WINDOW, _NET_WM_PING
> WM_LOCALE_NAME(STRING) = "en_US.UTF-8"
> WM_CLASS(STRING) = "urxvt", "URxvt"
> WM_HINTS(WM_HINTS):
>               Client accepts input or input focus: True
>               Initial state is Normal State.
>               window id # of group leader: 0x40aa36
>               The urgency hint bit is set
> WM_NORMAL_HINTS(WM_SIZE_HINTS):
>               program specified minimum size: 14 by 26
>               program specified resize increment: 10 by 22
>               program specified base size: 4 by 4
>               window gravity: NorthWest
> WM_CLIENT_MACHINE(STRING) = "memex"
> WM_COMMAND(STRING) = { "urxvt", "-cd", "/home/blackbit" }
> _NET_WM_ICON_NAME(UTF8_STRING) = "blackbit@stacey: /etc"
> WM_ICON_NAME(STRING) = "blackbit@stacey: /etc"
> _NET_WM_NAME(UTF8_STRING) = "blackbit@stacey: /etc"
> WM_NAME(STRING) = "blackbit@stacey: /etc"
> $
> 
> This is of an unaffected window:
> 
> $ xprop -id 0x40aaee
> WM_STATE(WM_STATE):
>               window state: Normal
>               icon window: 0x0
> _NET_WM_PID(CARDINAL) = 1159
> WM_PROTOCOLS(ATOM): protocols  WM_DELETE_WINDOW, _NET_WM_PING
> WM_LOCALE_NAME(STRING) = "en_US.UTF-8"
> WM_CLASS(STRING) = "urxvt", "URxvt"
> WM_HINTS(WM_HINTS):
>               Client accepts input or input focus: True
>               Initial state is Normal State.
>               window id # of group leader: 0x40aaee
> WM_NORMAL_HINTS(WM_SIZE_HINTS):
>               program specified minimum size: 14 by 24
>               program specified resize increment: 10 by 20
>               program specified base size: 4 by 4
>               window gravity: NorthWest
> WM_CLIENT_MACHINE(STRING) = "memex"
> WM_COMMAND(STRING) = { "urxvt", "-cd", "/home/blackbit" }
> _NET_WM_ICON_NAME(UTF8_STRING) = "urxvt"
> WM_ICON_NAME(STRING) = "urxvt"
> _NET_WM_NAME(UTF8_STRING) = "urxvt"
> WM_NAME(STRING) = "urxvt"
> $

These events seem to coincide with the following phenomenon:
when I click into the terminal emulator window, characters appear that 
look like escape sequences, without the escape itself.

blackbit@memex pts/7 ~ $ 0;12;12M0;12;12m7;5M0;7;5m

The numbers appear to be dependent on the mouse position.
If i click and move the mouse, there is a flood of these sequences.
Running `reset` doesn't fix it.

I can't claim to remotely understand what is happening here.

-Alex

_______________________________________________
rxvt-unicode mailing list
[email protected]
http://lists.schmorp.de/mailman/listinfo/rxvt-unicode

Reply via email to