-
Notifications
You must be signed in to change notification settings - Fork 5.9k
Graphical artifacts on the terminal #7317
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Do you have screenshots? I am not seeing anything wrong in Chromium 135.0.7049.52. Do you have any settings that affect the terminal? If you launch a blank Codespaces project using the same browser, do you get the same issue? |
Thank you! Interesting. Does disabling GPU acceleration change anything? (You can find it in the settings, search for "terminal").
I mean going here: https://github.com/codespaces Codespaces also uses VS Code web, so if it reproduces there then we know it is a problem with VS Code itself rather than code-server, so it is a helpful debugging step. |
Thank you for testing! Sounds like a bug with the GPU acceleration feature in VS Code, in that case. The closest issue I found upstream was microsoft/vscode#69665 but it is not a perfect match, the image just looked similar. They recommend running the In the meantime, I will close this as an upstream issue since it will need to be fixed there! |
Is there an existing issue for this?
OS/Web Information
code-server --version
: 4.99.3 c36b2d3 with Code 1.99.3Steps to Reproduce
Expected
Terminal should be clearly displayed
Actual
Terminal is not readable
Logs
Screenshot/Video
Does this bug reproduce in native VS Code?
This cannot be tested in native VS Code
Does this bug reproduce in GitHub Codespaces?
This cannot be tested in GitHub Codespaces
Are you accessing code-server over a secure context?
Notes
No response
The text was updated successfully, but these errors were encountered: