Bug 391170 - terminal emulation issues with atop
Summary: terminal emulation issues with atop
Status: RESOLVED DUPLICATE of bug 384620
Alias: None
Product: konsole
Classification: Applications
Component: emulation (show other bugs)
Version: 17.08.3
Platform: Debian unstable Linux
: NOR normal
Target Milestone: ---
Assignee: Konsole Developer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-02-27 16:04 UTC by Marc Haber
Modified: 2018-03-15 03:47 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
atop in konsole (235.13 KB, image/png)
2018-02-27 16:04 UTC, Marc Haber 		Details
atop in xterm (108.26 KB, image/png)
2018-02-27 16:04 UTC, Marc Haber 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Marc Haber 2018-02-27 16:04:11 UTC 
Created attachment 111051 [details]
atop in konsole

atop is one of my most important tools. Since a few weeks, in konsole, atop output looks really weird. See attachment. I have also attached how atop looks in xterm, and is supposed look like.

I have also seen that kind of weird behavior in mutt or vim, but it's not as readily reproducible in those applications like it is in atop.

Greetings
Marc
Comment 1 Marc Haber 2018-02-27 16:04:32 UTC 
Created attachment 111052 [details]
atop in xterm
Comment 2 Kurt Hindenburg 2018-02-27 16:12:43 UTC 
What shell are you using?  Any changes to your Konsole settings?  Fullscreen, etc.

Looks fine here on master.
Comment 3 Wolfgang Bauer 2018-02-27 17:37:59 UTC 
Likely related to bug#384620 I think, which is fixed in master. (by adding support for the REP sequence that is used by the latest ncurses if TERM=xterm*)

Does it work if you run e.g. "TERM=konsole atop" instead?
Comment 4 Christoph Feck 2018-03-15 03:47:13 UTC 
No response; assume it is a duplicate. If you still have the issue with the Konsole 18.04 version (to be released in April), please add a comment.
Comment 5 Christoph Feck 2018-03-15 03:47:56 UTC 

*** This bug has been marked as a duplicate of bug 384620 ***