Terminal: your 131072x1 screen size is bogus. expect trouble

[ghost]

• VSCode Version: Code 1.17.0 (be377c0, 2017-10-04T23:33:45.303Z)
• OS Version: Linux x64 4.13.4-200.fc26.x86_64

when I open the integrated terminal, I see this message:
your 131072x1 screen size is bogus. expect trouble

the image shows also bug #35794 with font isn't fitting in line.

[Tyriar]

I saw this happen on Fedora. Not sure what would be causing it but it seems harmless.

[andreiucm]

I have similar issue in ubutnu 16.04
#35773 (comment)

[mmclark]

I see it on my Fedora 26 installation as well. Beyond the error message, the font rendering seems off. Notice how the tops of the letters are clipped:

[rbakaou]

Got same letters clipped since Version 1.17.0. I'm on fedora 26 too.

[wbogocki]

Same here, also on Fedora 26 on VMware with disabled GPU acceleration.

I set the font to Droid Sans Mono as a temporary workaround. It still gets clipped, this time at the bottom and only barely so it's a lot better.

[ivan-brko]

Got the same issue, Fedora 26 with Version 1.17.0.

[hpossn]

Fedora 25, same issue

[rohel01]

• VSCode Version: Code 1.17.0 be377c0, 2017-10-04T23:33:45.303Z
• OS Version: Linux x64 4.13.4-200.fc26.x86_64
• Extensions: Extension|Author truncated |Version -|-|- better-toml|bun|0.3.1 python|don|0.7.0 plantuml|jeb|2.3.0 cpptools|ms-|0.13.1 vscode-code-outline|pat|0.0.11 rust|rus|0.3.1 vscode-lldb|vad|0.6.2

Same issue, Fedora 26

[vstoykov]

I have the same issue. Found this on the StackExchange https://unix.stackexchange.com/questions/259529/your-screen-size-is-bogus-expect-trouble

This message comes from (perhaps other places) procps, which does a quick check to determine the screen width for ps command's notion of width.

procps makes this check in set_screen_size, e.g., if the screen size is too small to print anything useful:

 if((screen_cols<9) || (screen_rows<2))
   fprintf(stderr,"Your %dx%d screen size is bogus. Expect trouble.\n",
     screen_cols, screen_rows
   );

You might see the same code (via cut/paste) in other programs, but this is the most likely one.

As to why the problem occurred: when starting a terminal emulator, it can be multiple processes which communicate, sharing the information about the pseudo-terminal connection. Sometimes, the information is not shared rapidly enough, causing (usually) minor errors in the terminal settings.

[mprahl]

I'm having the same problem on Fedora 26.

[Tyriar]

Nice find @vstoykov, looks like the terminal is set at 1 row initially which is causing the error.

[jstaf]

Some additional info - this happens only when you had the integrated terminal open the last time you closed VSCode. The display corruption (with the top of each line getting moved to the bottom of the line) appears to be new to the latest update.

[Tyriar]

I see layouts are occurring on start up with the rows at 1

[sherl0cks]

FYI this is duplicate of #35644 which was fixed in https://github.com/Microsoft/vscode/milestone/55?closed=1

[vstoykov]

@sherl0cks the issue that you mansions is not the issue that is discussed here.

[sagebind]

I see the same kind of issue when using Fish shell. If the terminal is already open when the window loads, I see this in the terminal:

This doesn't happen if the terminal is initially closed, and then you toggle it manually after the window loads. It seems that the terminal size is set to be very small initially while the window is loading.

I reasonable fix I think would be to not actually spawn any integrated terminal processes until the window finishes loading (and the size can actually be known).

[Barugon]

Same issue on Fedora 26.

[ezralalonde]

I am also seeing this.

• Fedora 26 (Workstation Edition)
  4.13.5-200.fc26.x86_64
• Code 1.17.1
  1e9d365.

If I launch after having exited with the terminal open, I see the following message:

your 131072x1 screen size is bogus. expect trouble
your 131072x1 screen size is bogus. expect trouble

It appears to be start fine if I launch after exiting with the terminal closed, or if I exit the terminal (with CTRL+D or exit) and then re-open it.

Thanks to jstaf for mentioning the workaround above, it helped me. And thanks to the entire vscode team for making such a wonderful product. I have tried many editors, and Code's the only one which has been able to take any mindshare from vim. I'm a very happy user. Thank you!

[FelikZ]

same 1.17.2

[Tyriar]

I think this is also causing this on Windows:

[guildeol]

Hi!
The clipping issue seems to occur if the fonts for vscode and the terminal are different. After I changed vscode to use the same font as my terminal, the clipping was gone (though the 'screen size is bogus' persists).