[Bug]: Terminal not showing up correct, and did not working at all after updating to 4.9.1 from 4.8.3

[Dionysos211]

Is there an existing issue for this?

• I have searched the existing issues

OS/Web Information

• Web Browser: Safari
• Local OS: MacOs
• Remote OS: CentOS
• Remote Architecture: amd64
• code-server --version: 4.9.1

Steps to Reproduce

1. update to 4.9.1
2. with extensions
3. just open Terminal Window -> bug
4. clean reinstalled 4.8.3
5. no extentions then with extentions
6. just open Terminal Window -> NO bug
7. clean reinstalled 4.9.1
8. no extentions
9. just open Terminal Window -> bug
10. installed 4.8.3 OVER 4.9.1 (download extract)
11. no extentions
12. just open Terminal Window -> NO bug

Expected

Terminal should work as normal something went wrong from 4.8.3 to 4.9.1

Actual

actually I stay at 4.8.3 because 4.9.1 not works for me

Logs

No response

Screenshot/Video

No response

Does this issue happen in VS Code or GitHub Codespaces?

• I cannot reproduce this in VS Code.
• I cannot reproduce this in GitHub Codespaces.

Are you accessing code-server over HTTPS?

• I am using HTTPS.

Notes

if needed I can go on 4.9.1 and make screenshots
beause i have to check this marks before I can send it... I checked it, nut not true...

I cannot reproduce this in VS Code. Guess u mean local...
I CAN reproduce this in GitHub Codespaces. Terminal also bugged.

[Dionysos211]

here an image from GitHub Codespaces. where the same error is..
black
no prompt
no typing possible
if I hit enter something happens (blinking)

[Dionysos211]

Also happens on other devices.. also error on GitHub Codespaces..

But on my resetted Server to 4.8.3 everything works fine..

[jsjoeio]

What happens if you open 4.9.1 in an incognito window?

[Dionysos211]

still the same behavior also in different Browsers and on different devices and different OS...
... with 4.9.1 and Codespaces

[code-asher]

If it happens in Codespaces we might benefit from reporting upstream.

[benz0li]

@Dionysos211 Can you reproduce this on my reference deployment?

1. Go to https://demo.jupyter.b-data.ch
2. Log in with your GitHub account
3. (Click "Start My Server")
4. Select image R (jupyterlab/r/verse:latest)
5. Open code-server
6. Terminal: Create New Terminal

👉 If the server does not start the first time, simply give it another try.

[benz0li]

@Dionysos211 What have you set "Terminal > Integrated: Gpu acceleration" (terminal.integrated.gpuAcceleration) to?

Maybe related to:

• Safari not properly rendering Terminal after page reload microsoft/vscode#160070
• Update to 1.71 #5535 (comment)

[Dionysos211]

@Dionysos211 Can you reproduce this on my reference deployment?

1. Go to https://demo.jupyter.b-data.ch
2. Log in with your GitHub account
3. (Click "Start My Server")
4. Select image R (jupyterlab/r/verse:latest)
5. Open code-server
6. Terminal: Create New Terminal

👉 If the server does not start the first time, simply give it another try.

Hi,
I have now tried this once.
Unfortunately, the same error picture appears.
The terminal shows up with artifacts and you don't have the possibility to enter anything.

I have posted a screenshot for comparison:

• Same system, same browser...
  Left: My server, where everything still works under version 4.8.3
  Middle: Your JupiterLab server, where the error occurs.
  Right: The GitHub Codespace server where the error also occurs.

[Dionysos211]

@Dionysos211 What have you set "Terminal > Integrated: Gpu acceleration" (terminal.integrated.gpuAcceleration) to?

Maybe related to:

• Safari not properly rendering Terminal after page reload microsoft/vscode#160070
• Update to 1.71 #5535 (comment)

Hi,
in all my test scenarios the setting of:
"Terminal > Integrated: Gpu acceleration".
was set to "Auto".

[Dionysos211]

mhm sorry @code-asher but, what do you mean with: "reporting upstream"