aksakalli / gtop

System monitoring dashboard for terminal
MIT License
9.7k stars 325 forks source link

Layout glitches #3

Open devunt opened 7 years ago

devunt commented 7 years ago

chrome_2017-08-11_01-43-31

aksakalli commented 7 years ago

Hi,

Could you try to run it like:

LANG=en_US.utf8 TERM=xterm-256color gtop
devunt commented 7 years ago

Hi

It is still glitched as same as above screenshot. I tried to run it without byobu and tmux, but the result was same. So it is not related to terminal multiplexers. I tried running it on both bash and zsh, but again the result was same. Attaching my environment variables for your reference.

USER=devunt
LOGNAME=devunt
HOME=/home/devunt
PATH=/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl
MAIL=/var/spool/mail/devunt
SHELL=/bin/zsh
SSH_CLIENT=192.168.136.1 5591 22
SSH_CONNECTION=192.168.136.1 5591 192.168.136.132 22
SSH_TTY=/dev/pts/0
TERM=xterm-256color
XDG_SESSION_ID=c3
XDG_RUNTIME_DIR=/run/user/1000
DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus
SHLVL=1
PWD=/home/devunt
OLDPWD=/home/devunt
LANG=en_US.UTF-8
ZSH=/home/devunt/.oh-my-zsh
PAGER=less
LESS=-R
LC_CTYPE=en_US.UTF-8
LSCOLORS=Gxfxcxdxbxegedabagacad
LS_COLORS=rs=0:di=01;34:ln=01;36:mh=00:pi=40;33:so=01;35:do=01;35:bd=40;33;01:cd=40;33;01:or=40;31;01:mi=00:su=37;41:sg=30;43:ca=30;41:tw=30;42:ow=34;42:st=37;44:ex=01;32:*.tar=01;31:*.tgz=01;31:*.arc=01;31:*.arj=01;31:*.taz=01;31:*.lha=01;31:*.lz4=01;31:*.lzh=01;31:*.lzma=01;31:*.tlz=01;31:*.txz=01;31:*.tzo=01;31:*.t7z=01;31:*.zip=01;31:*.z=01;31:*.Z=01;31:*.dz=01;31:*.gz=01;31:*.lrz=01;31:*.lz=01;31:*.lzo=01;31:*.xz=01;31:*.zst=01;31:*.tzst=01;31:*.bz2=01;31:*.bz=01;31:*.tbz=01;31:*.tbz2=01;31:*.tz=01;31:*.deb=01;31:*.rpm=01;31:*.jar=01;31:*.war=01;31:*.ear=01;31:*.sar=01;31:*.rar=01;31:*.alz=01;31:*.ace=01;31:*.zoo=01;31:*.cpio=01;31:*.7z=01;31:*.rz=01;31:*.cab=01;31:*.wim=01;31:*.swm=01;31:*.dwm=01;31:*.esd=01;31:*.jpg=01;35:*.jpeg=01;35:*.mjpg=01;35:*.mjpeg=01;35:*.gif=01;35:*.bmp=01;35:*.pbm=01;35:*.pgm=01;35:*.ppm=01;35:*.tga=01;35:*.xbm=01;35:*.xpm=01;35:*.tif=01;35:*.tiff=01;35:*.png=01;35:*.svg=01;35:*.svgz=01;35:*.mng=01;35:*.pcx=01;35:*.mov=01;35:*.mpg=01;35:*.mpeg=01;35:*.m2v=01;35:*.mkv=01;35:*.webm=01;35:*.ogm=01;35:*.mp4=01;35:*.m4v=01;35:*.mp4v=01;35:*.vob=01;35:*.qt=01;35:*.nuv=01;35:*.wmv=01;35:*.asf=01;35:*.rm=01;35:*.rmvb=01;35:*.flc=01;35:*.avi=01;35:*.fli=01;35:*.flv=01;35:*.gl=01;35:*.dl=01;35:*.xcf=01;35:*.xwd=01;35:*.yuv=01;35:*.cgm=01;35:*.emf=01;35:*.ogv=01;35:*.ogx=01;35:*.aac=00;36:*.au=00;36:*.flac=00;36:*.m4a=00;36:*.mid=00;36:*.midi=00;36:*.mka=00;36:*.mp3=00;36:*.mpc=00;36:*.ogg=00;36:*.ra=00;36:*.wav=00;36:*.oga=00;36:*.opus=00;36:*.spx=00;36:*.xspf=00;36:
_=/usr/bin/env
devunt commented 7 years ago

image

Running on tty1 of the same system (accessed via vmware window) has no issues (at least no layout glitches). However running it with TERM=xterm-256color on tty1 produces some glitches, but it is not a problem.

I guess this is the problem of the secure shell chrome extension?

devunt commented 7 years ago

image Running with openssh windows binary on cmder shows another glitches.

image However running with putty.exe works normally if TERM=linux if given. Without TERM=linux, it shows as q and as q which will be look like qqqqqqqqqq on the top.

behnambagheri commented 7 years ago

I'm having the same problem and try to run with: LANG=en_US.utf8 TERM=konsole-256color gtop But no different! and try to run in tty > everything is good


- archlinux x86_64 Linux 4.12.4-1-ARCH
- bash 4.4.12 & fish 2.6.0
- npm 5.3.0
- node 8.3.0
- resolution 1920*1080
- konsole 17.04.3

In Fullscreen: screenshot_20170810_232413

other size: image

extensionsapp commented 7 years ago
screenshot_7

Putty. Debian 8 x64 Node v6.10.2

devunt commented 7 years ago

@extensionsapp Try using TERM=linux gtop.

jacktuck commented 7 years ago

Zeit's Hyper has same issues

@extensionsapp Didn't make a difference in hyper at least.

Iterm2 on the other hand is perfect!

wachunei commented 7 years ago

on Mac OS X:

Same issues with hyper screen shot 2017-08-11 at 10 14 27 am

here it is with terminal.app screen shot 2017-08-11 at 10 15 49 am

None of the solutions above worked, any way we could help debug this?

darxtrix commented 7 years ago

So, I wrote a task manager back in 2015 https://github.com/darxtrix/ptop

I had the same issues with gibberish text appearing on the screen. Pressing CTRL+L(clear) will make them disappear but the problems keep ticking in. So, I did a bit research on how to solve this and found out it is due to fast updating/drawing of UI on the terminal. I kind of adopted a technique for lazy loading of UI component on the terminal to solve this. This is the commit: https://github.com/darxtrix/ptop/commit/5a7b3f826c5062fde3cdfca0dd7063647258a3cc

The crux is to replace the display() method of the underlying curses library to DISPLAY() which is slow but overall avoids the random stuff on the screen. ptop is in Python and I don't know how relevant it is here.

Hope it helps.

aksakalli commented 7 years ago

This might be helpful for font related issues #21

Syedayesha commented 7 years ago

I too have the same problem.How can I solve this issue in windows 8.1?Using this LANG=en_US.utf8 TERM=xterm-256color gtop didn't solve my problem.?How can I use this in windows command prompt?

MaxBGreenberg commented 1 year ago

I too am experiencing an issue. When I run gtop in GNOME Terminal in Fedora 37, the layout is different from how it's supposed to. Looks blockier compared to what I got using Ubuntu or MacOS. Additionally, I get an error output to the terminal:

Error on xterm-256color.plab_norm: "%t;7%;%?%p4%t;5%;%?%p7%t;8%;m"

var v, stack = [], out = []; ) {out.push("; 7")}; if ((stack.push(v = params[3]), v)) {out.push("; 5")}; if ((stack.push(v = params[6]), v)) {out.push("; 8")}out.push("m"); return out.join("");

I know nothing about JavaScript so this error message means nothing to me. Running LANG=en_US.utf8 TERM=xterm-256color gtop does not help. This issue does not exist at all in TTY mode. I am using NodeJS v18.12.1

Screenshot from 2023-01-05 23-06-51