Summary: | =sys-process/atop-2.3.0 with sys-libs/ncurses 6.1 - atop output is corrupted | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Vincent de Phily <moltonel> |
Component: | Current packages | Assignee: | Gentoo's Team for Core System packages <base-system> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | odi |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
See Also: | https://bugs.gentoo.org/show_bug.cgi?id=652678 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 652080 |
Description
Vincent de Phily
2018-03-27 14:41:16 UTC
Which terminal emulator do you use? My original test terminals were konsole-17.12.3 and yakuake (uses the konsole component underneath, AFAIK). I've now tried with xterm-327, xfce4-terminal-0.8.6. and x11-terms/cool-retro-term-1.0.1. None of those trigger the bug, so it does look terminal-specific as well as being tied to the ncurses version. In all these terminals, I have either $TERM=xterm or $TERM=xterm-256colors. Exporting TERM=konsole in the konsole shell fixes the atop behaviour. I couldn't find any place where I'd have configured that away from the default (I use bash and KDE), so for the moment I'm assuming that "TERM=xterm" is set by konsole. I'm not sure who's at fault here: * did I configure a bad TERM somewhere ? * does konsole deviate from normal xterm behaviour but fail to set TERM=konsole ? * should ncurse have kept the konsole-compatible behaviour of TERM=xterm that it had in 6.0 ? I'm glad I found the `export TERM=konsole` workaround (even though I'm not sure where it should be applied), but I'm also waiting on #651720 before unmasking ncurses-6.1 on my machine. Same here, and upstream bug: https://github.com/Atoptool/atop/issues/25 *** This bug has been marked as a duplicate of bug 648338 *** |