Repository navigation
Tmux shows rgb control sequences during resize/reconnect #4569
Description
This is a continuation of #4541 .
I was finally able to rebuild (from main) and retest this. I can still reproduce this failure, although the signature is not identical:
$ 11;rgb:ffff/ffff/ffff11;rgb:ffff/ffff/ffff11;rgb:ffff/ffff/ffff11;rgb:ffff/ffff/ffff11;rgb:ffff/ffff/ffff
Activity
solace-rcampbell commentedon Jul 30, 2025
I didn't have the server log enabled during the last reproduction, I'm now trying with server logging enabled. It took me multiple days to reproduce it last time.
solace-rcampbell commentedon Jul 31, 2025
log.txt.gz
I was able to gather a server log when it happened.
nicm commentedon Aug 1, 2025
OK I forgot that colour requests are also sent on resize. If you're trying to reproduce, you need to wait 30 seconds between resizes before it will request again.
Please try this rgbreq.diff.txt and let me know if it helps. If it still happens, please send another server log.
qgates commentedon Aug 30, 2025
@nicm rgbreq.diff patch doesn't appear to be in master, is it planned to be included or has this issue already been fixed on master? Seeing this issue regularly in 3.5a
nicm commentedon Aug 30, 2025
Does it fix the problem for you?
solace-rcampbell commentedon Aug 30, 2025
Yes, this seems to have fixed the problem for me. Thanks.
nicm commentedon Sep 1, 2025
I have applied this to OpenBSD now, will be in GitHub later. Thanks!
onyto commentedon Sep 14, 2025
Hey @nicm, will this fix be included in an upcoming release? Although building from master solves this problem, it causes other issues, so it's not a viable solution for me.
onyto commentedon Sep 24, 2025
For more context: I have this issue too, and it is 100% reproducible for me. It always prints 11;rgb:0c0c/0c0c/0c0c when I reattach to a tmux session, and not on resize. It only started happening after I upgraded from Debian 12 to Debian 13 (tmux 3.3a -> 3.5a). Building from master doesn't print the sequence, but instead always prints "server exited unexpectedly". Finally, downgrading to 3.3a seemed to run stable until I tried to yank a line (which highlights it) in neovim, and tmux crashes. In conclusion, all recent tmux versions are unstable for me.
github-actions commentedon Oct 25, 2025
This issue has been automatically locked since there has not been any recent activity after it was closed.