tmux rendering issues

[xxxserxxx]

Please give the following info:

• The output of uname -a: Linux owl 3.10.0-693.11.6.el7.x86_64 Add ability to send different signals to processes #1 SMP Thu Jan 4 01:06:37 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
• Any relevenat hardware info: Intel(R) Xeon(R) CPU E7330 @ 2.40GHz
• Terminal shell (like zsh or bash): bash
• Terminal emulator (like iTerm or gnome terminal): gnome
• tmux version if using tmux: tmux/2.2

I'm trying to use gotop on a cluster computing centos 7 system, but the program can only detect a few CPUs. The right configuration shows like this htop image, 16 cores. The display in tmux is not right but outside tmux is fine.

• Inside tmux
  

• outside
  

• Right config
  

[xxxserxxx]

Just fyi, you can display all the separate cpu cores in the graph with gotop -p. It only shows average by default if there are more then 8 cores.

[xxxserxxx]

Thanks for the info. I used gotop -p to display all cores. This doesn't fix the tmux display.

[xxxserxxx]

Confirming I've got the same issue with tmux, in both bash and zsh.

FreeBSD trident 11.2-RELEASE-p4 FreeBSD 11.2-RELEASE-p4 #5 r340144: Mon Nov 5 11:27:55 AEDT 2018 root@trident:/usr/obj/usr/src/sys/TRIDENT amd64

[xxxserxxx]

By the way, this bug doesn't appear on latest tmux version (2.8).

[xxxserxxx]

@wallace11 Did you get this issue on a previous version of tmux tho? I wasn't able to reproduce this with alacritty or gnome-terminal on any version of tmux back to 1.0.

[xxxserxxx]

@wallace11 Did you get this issue on a previous version of tmux tho? I wasn't able to reproduce this with alacritty or gnome-terminal on any version of tmux back to 1.0.

Sorry, I wasn't trying to replicate this on another version...

[xxxserxxx]

By the way, this bug doesn't appear on latest tmux version (2.8).

I do see this occurring on tmux 2.8, at least in Alpine Linux.

root at summit in ~
# tmux -V
tmux 2.8

[xxxserxxx]

Is this a unicode display issue? https://askubuntu.com/questions/410048/utf-8-character-not-showing-properly-in-tmux suggests running "tmux -u" to fix a similar issue.

[xxxserxxx]

This was closed in the upstream ticket after confirmation that tmux -u fixes the issue.

cjbassi#59