Code-server: Can't see any text in terminal

[misaka00251]

• code-server version: 2.1523-vsc1.38.1
• OS Version: Debian 10

Description

No text in terminal:

When type htop:

Just black...but it is running.

    "workbench.colorCustomizations": {
        "terminal.foreground": "#37FF13",
        "terminal.background": "#2B2424"
    },

And above settings does not help.

Steps to Reproduce

1. Open terminal

[misaka00251]

It seems the latest Firefox & Brave browser has this issue.

[sr229]

Try refreshing if that helps.

[misaka00251]

No, that didn't help.

[Dj-jom2x]

this happens to me if I don't have enough access to tmp.. like I cant execute, when my temp is mounted read-only that happened xD

[sr229]

this happens to me if I don't have enough access to tmp.. like I cant execute, when my temp is mounted read-only that happened xD

That's weird. We'll investigate and see what happens, but I do know that VSCode does create tempfiles during its runtime.

[Dj-jom2x]

I wanted to say this before kindly keep putting files on tmp.. others restrict it because of whm or cyber panel web hosting panel.. you cant exec there most of the time. I don't care what folder ... or just keep them in one folder... so we can easily delete them ... or install on other jailed shell accounts. without having access to temp.

[sr229]

I wanted to say this before kindly keep putting files on tmp.. others restrict it because of whm or cyber panel web hosting panel.. you cant exec there most of the time. I don't care what folder ... or just keep them in one folder... so we can easily delete them ... or install on other jailed shell accounts. without having access to temp.

I don't think we have control over that, that's how Visual Studio Code was designed, we just wrap around its codebase to make a rather flexible Cloud IDE that everyone can use @Dj-jom2x.

[misaka00251]

I found a solution, add this line to settings.json will solve it.

"terminal.integrated.rendererType": "dom"

Still, I don't understand what cause it.

[sr229]

@misaka00251 I think your browser does not support HTML5 Canvas or the canvas support in it is buggy. I tried it on CrOS 77 and it seems to be consistent with your behavior when the Wayland server reboots.

[misaka00251]

That's it!