Add Render Glitch Workwaround to DOCS.MD

[266-750Balloons]

Since VSCode/Codium 1.82.x, the Linux version, upon package updates, may open up to a mangled version of the interface missing text, making it completely unusable. This is an upstream Electron/Chromium issue with Mesa shaders (see microsoft/vscode#190437). A work-around suggested in that issue is to delete the GPU cache with the following command:

rm -rf ~/.config/VSCodium/GPUCache

In case other users come across the same issue, I think it would be a good idea to address this in VSCodium documentation. It could be removed once the aforementioned bugs are fixed.

[daiyam]

It's already in Troubleshooting

[daiyam]

Instead, we should add a link to the wiki page.

[266-750Balloons]

I'll make that revision to the patch when I have the time. In the meantime, I have to ask, why is there a separate DOCS.md from the the wiki?

[daiyam]

@266-750Balloons I've reused your text in the wiki since it make things clearer. Thx

For the DOCS.md, not sure. Maybe, we should merge them. And the docs/build.md, maybe, it should be renamed CONTRIBUTING.md.

[daiyam]

@GitMensch @PalinuroSec @paulcarroty Should the DOCS.md be moved to the Wiki?

[paulcarroty]

AFAIR Wiki access isn't flexible yet - rw access for all or only for maintainers, I don't like it.

[daiyam]

@paulcarroty Very true.

Like in the current case, @266-750Balloons doesn't get the credit for the text that I have copied from his PR.

Maybe, everything should be moved to the docs folder?

[paulcarroty]

everything should be moved to the docs folder

and then it's possible to generate a static doc website using something like mdBook.

[daiyam]

@266-750Balloons If you can update your PR and add your text to the file /docs/troubleshooting.md, we will merge it. Thx