VSCode WSL Weird Colors Issue - visual-studio-code

I am having the issue from these posts:
https://github.com/microsoft/vscode/issues/93356
https://dev.to/iamst0rm/fixing-vscode-color-bug-on-linux-185f
Here is a screenshot:
I tried the solutions, but they didn't do much for me.
In a desperate attempt to fix it, I updated my Ubuntu to version Ubuntu 20.04.2 LTS which kind of reduced the issue but I still have it.
I added "disable-hardware-acceleration": true as per this guide: https://code.visualstudio.com/updates/v1_40#_disable-gpu-acceleration
Is there anything else I can do, did someone else experience this issue?
Thanks so much!

I've had color issues, but not this severe graphical issue. I had tried to fix my color issues using the methods you linked. I found a solution that fixed it for me at least, you could give it a shot.
Go to this Google Docs document and follow the 5 steps under "Using colormgr from the command line". This fixed the issue on all Chromium-based applications by setting sRGB as the default color profile.
https://docs.google.com/document/d/1jMokB_OBkZVELu22li8vnHxAUoL1eGnLedP-1Gttv40/edit#heading=h.z8rbug83238e

Related

VSC Autocompletion and colorization of code not working (Extensions already installed)

I'am using VSC and started programming c++. But somehow the autocompletion and coloring of the code is not working properly. I have the latest version of VSC and already reinstalled the extensions. I have no clue what could cause the problem, I would be very grateful if you guys could help me. For example "x1", "x2" and "epsilon" in the body of the function should be colored blue and not white and I think this problem links or correlates to the autocompletion problem.
After hours of desperately searching for a solution, I've found this, which actually solved my problem.
Solution to my issue

Unity Editor does not fully render UI and is unresponsive on Windows 10

The editor window does not fully render and is unresponsive... I restored windows by completely reinstalling it, fresh install, all clean... and still same issue:
I checked Unity 2017.3, 2017.2 and 5.6, with DX9, 11 and 12... allways same issue.
I found 0 related issues on google, maybe I'm not using the correct wording for the search (Unresponsive Unity Editor Windows). On the Unity forums someone mentioned DX version being the issue, but I already forced all recent versions and it fails for all of them.
Ok, so the issue is with Unity not being dpi aware so I had to remove my 150% scaling on my main 4K window in order for it to work.
Unity programmers my encounter this issue too, and come here for help as I did... I don't see why that's wrong #Programmer

VS Code Debug Console Double Spacing

As the title says, the debug console in VS Code is double-spacing for me. I'm using the OSX edition. Seems to work fine for others from what I've seen. Have tried it with multiple programs and it always double spaces.
I can't seem to find any setting to change this behaviour. Anyone able to help?
Thanks.
JT
After searching and testing I came to github where I filed a bug for this. It seems that it was known already under a different issue ID already, see https://github.com/Microsoft/vscode/issues/17526 for details.

MATLAB help/documentation not displaying correctly

I'm having a problem with the built-in help/documentation within MATLAB 2013a (issue also present in 2012b).
Upon opening the help files the pages appear with no formatting, only plain text. Search results do appear correctly though.
I have found only one instance of someone else with this issue, on MATLAB central here. However, there are no responses to the author's question. The issue I'm having is exactly the same as described there.
I have tried removing the preference folder and relaunching MATLAB but this doesn't help.
I'm using Windows 8.1 and MATLAB 2013a.
Any help or suggestions on how to fix this would be very much appreciated.
Edit:
Thank you everyone for the feedback so far. I don't believe java to be the issue, I have the latest version installed (1.7.0_45) while MATLAB uses it's own version (1.6.0_17). Both of which co-exist on my machine.
Following horchler's thread led me to another semi-related bug report here. The following code is listed at the bottom of the workaround (the script attached to the workaround didn't fix anything unfortunately).
com.mathworks.mlwidgets.html.HtmlComponentFactory.setDefaultType('HTMLRENDERER');
This results in a degraded appearance of documentation pages and loss of some functionality but is still an improvement over the plain text and scrambled pages.
Hopefully from this new information we can work towards a solution!
One solution is to go back to IE-10, or to use the patch on http://www.mathworks.com/support/bugreports/989850
Which basically replaces the localnav.js at <MATLAB>/help/includes/product/scripts
The link to download!
This is an old post, but I had the same issue and have a fix (not downloading R2013b or java related). Just downgrade from IE 11 to 10: Go to System (or System & Security)->Windows Update->View Update History->Installed Updates -> Find IE11 and uninstall it. Your system should revert back to the prior installed version. This fixed the help issues.
The problem is related to Internet Explorer 11, which MATLAB uses to render its help files. I was experiencing this problem in Windows 7 and rolling back to IE 10 fixed it right up. Unfortunately, that's not an option with Windows 8.

How exactly do I fix my eclipse and not the bug?

I have this bug in my eclipse which causes the screen to go black when moving unfocused tab around, it's really annoying and I'm trying to figure out how do I apply the fix mentioned in the above link. I tried to understand this answer and I also saw this answer but these didn't help, and trying to google for it brings up either info about how to fix the bugs themselves, or how to create patches.
I just want to fix my eclipse, the bug has been already fixed and I want to apply that fix to my eclipse, any thorough and detailed answers are welcome,
thanks
Just upgrade your Eclipse installation to 4.3. The bug has been fixed in that version and that version was released in June 2013.