Open kevinushey opened 1 month ago
One way to simulate this, on macOS: open the file at ~/Library/Application Support/RStudio/config.json
, and change the zoomLevel parameter to a value like 100. Then, if you try to run RStudio from the command line:
$ /Applications/RStudio.app/Contents/MacOS/RStudio
[utils.ts] [createStandaloneErrorDialog] Error when creating Standalone Error Dialog: Error: application not set
at s (/Applications/RStudio.app/Contents/Resources/app-arm64/.webpack/main/index.js:8:337336)
at t.createStandaloneErrorDialog (/Applications/RStudio.app/Contents/Resources/app-arm64/.webpack/main/index.js:20:86492)
at Object.main (/Applications/RStudio.app/Contents/Resources/app-arm64/.webpack/main/index.js:20:40285)
Config schema violation: `view/zoomLevel` must be <= 5
This is still a bit curious though, since the error I'm seeing is slightly different than the one here, and the zoomLevel set in my configuration file was correct (so it must've been getting read elsewhere?)
I hit this as well. My repro steps:
I get that error, and ultimately have to kill the desktop process (and sometimes also the rsession process).
This scenario causes config.json
to be missing the zoomLevel
entry altogether.
Also, you need to have no "legacy" setting for zoomLevel (from having run pre-Electron desktop), otherwise, that will be used and this problem won't happen. The clean-rstudio
script also cleans that up, hence the above steps will hit the bug.
I'm not quite sure how I got into this state, but if some configuration setting we have fails the schema validation, we should just set a safe default instead of failing altogether.