Theme resets to default on relaunch

[wombatinua]

• Web Browser: Google Chrome Version 86.0.4240.111 (Official Build) (x86_64)
• Local OS: MacOS 10.15.7
• Remote OS: Ubuntu 20.04
• Remote Architecture: x86-64
• code-server --version: v3.6.1

After the latest update my selected theme resets to default Light+ after one or several consecutive client restarts.
It doesn't matter what theme is selected before. If I open settings.json on server I see the theme is correct, but in workbench it resets to default. When the theme resets and I open Preferences -> Color Theme then it also resets in settings.json to "workbench.colorTheme": "Default Light+". Very weird.

I attach small video for the sake of demonstration https://cloud.dmitriypavlov.com/s/9YoT5scWALkcyq9
(theme resets on 3 relaunch). Please advice.

[hurleyef]

Same issue here too.

[wombatinua]

The workaround is to change the default theme to used one in Settings.

[ZeeMoros]

Probably related to this:
I can't change appearance ex: I usually hide the Run button.
Toggle Word Wrap doesn't work ether (doesn't activate at all).

• Web Browser: Firefox 82.0 (64-bit)
• Local OS: Windows 10 (1909)
• Remote OS: Alpine 3.12.1
• Remote Arch: x86-64
• code-server: v3.6.1

[wombatinua]

Probably related to this:
I can't change appearance ex: I usually hide the Run button.
Toggle Word Wrap doesn't work ether (doesn't activate at all).

Have no issues like that: can turn off panels and wrapping works.

[benz0li]

@code-asher With code-server 3.6.1, settings in ~/.local/share/code-server/User/settings.json are set as Remote only whereas with code-server 3.6.0 they are set both as User and Remote:

---

---

Update (2020-11-03): Problem also exists with code server 3.6.2

[vnijs]

I noticed this as well. First, it seems like the settings.json file in code-server/User is being ignored. If I copy the file from code-server/User to code-server/, however, and use Preferences: Open Setting (JSON) it still shows me a different file but with the same path. Very odd.

Not the paths shown for the two settings.json files in the screenshots below. Same path, different content.

[code-asher]

Yeah I poked into it a little and it looks like the settings file on disk is now used for remote only (which won't be used at all for code-server since it can't run the remote extensions anyway) and the user settings are now stored in browser storage. But even though it's actually in browser storage it still shows a file path in the editor and there seem to be other bugs with it too. I haven't done any research yet to see if this is a known issue with VS Code web or if it's something caused by code-server, so I'll be checking on that as soon as possible.

[vnijs]

Thanks for checking on this @code-asher. Do you know if there is a way to update/change these user settings from the command line? I would usually just copy a settings.json file to the desired location. Not sure how that would work with a "file" in browser storage however.

[wombatinua]

Thanks for checking on this @code-asher. Do you know if there is a way to update/change these user settings from the command line? I would usually just copy a settings.json file to the desired location. Not sure how that would work with a "file" in browser storage however.

Hey I did my own research and found out that if I simply copy settings.json from /User (remote) to /code-server (local) it would have no effect at all as local settings seems to be virtual path and actually stored in browser Local Storage.

What I did is simply opened User preferences within code-server itself (cmd + shift + P, "settings") and pasted it's contents to local settings.json within code-server. Obviously when browser Local Storage resets this settings are lost.

Thanks all the devs for the commitment.

[code-asher]

Yeah I don't think there's an easy way to do this; copying manually like that seems like the only option. The whole situation seems a bit weird to me so assuming VS Code doesn't make some kind of improvement I think maybe we should patch it to use the file system again.