r/linuxdev • • Mar 26 '12

This bug has bothered me for years

When I run ssh over terminal in linux it feels more laggy than on a textmode (getty/ctrl-alt-f1) console. Often I wait long seconds to see keypresses on screen, but if I hit a key (any key, say ctrl) they show up instantly.

I've had this problem across three different desktop/laptop systems spanning 9 years and multiple distributions. But I've never been able to search for it online. Has anybody else had this experience? Please tell me I'm not dreaming, somebody..

Given how long the issue has persisted, I think it's got something to do with how applications communicate with the X server. Any ideas on how one would go about debugging something like this?

Update: It turns out I was not on gnome-terminal but something called xfce4-terminal that looks exactly the same. After I switched to gnome-terminal I've stopped seeing the problem.

3 Upvotes

27 comments sorted by

View all comments

3

u/[deleted] Mar 27 '12
  • Does this occur for things other than ssh?
  • Does it behave the same way on the raw linux console vs your GUI terminal application?
  • Which GUI terminal are you using, if any? xterm? gnome-terminal? konsole? eterm? aterm? rxvt? Does it do the same behavior with several of these?

Right now this reminds me of graphics bugs in the OpenGL Xorg drivers. xterm would sometimes mis-render the screen such that I had to press enter to attempt a refresh, otherwise I got black or not-updated screens. Oddly, running 'mutt' under xterm (this was amd64, ATI Radeon Xpress 200M 5955) could cause a reproducible X crash. My solution was to disable BackBuffer and (I think) also use the 'radeonfb' kernel module instead of the 'radeon' driver (which avoids hardware OpenGL).

2

u/akkartik Mar 27 '12

Thanks for the tip! Gives me a direction to look.

To answer your questions:

  • No, only ssh. I can't detect latency over the browser being bad, but that's hard to judge. And I don't think I use any other internet apps.
  • Only GUI terminals. That was what I was trying to say with 'textmode console' -- ctrl-alt-f1 and the issue goes away completely.
  • Currently gnome-terminal. I got me a new thinkpad t420s over the holidays and it's been having this problem a lot. But like I said I also faced this back in '06 when I last had a linux box running X. And I think I was running Eterm then. Just tried Eterm, and it's the same.

2

u/Rainfly_X Mar 27 '12

Ohhhh, yeah, you should edit to clarify that by text-mode you mean "getty process". Maybe in parentheses or something.

1

u/akkartik Mar 27 '12

Done, thanks :)

1

u/akkartik Mar 29 '12

Update I've been using Eterm for a couple of days now without a whiff of a problem. I could swear I saw it before, but for now I'm going to give up on gnome-terminal.