You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a fresh bluefin on my framework 13 laptop. I start vscode and it looks blurry. I checked web for the issue and found this closed one here: #1362
I followed the workaround to set ELECTRON_OZONE_PLATFORM_HINT=auto and then it works.
My request would be to set this out of the box for Framework laptops such that users dont have to check the web to find this issue and apply the workaround themselfes. Thanks :)
What did you expect to happen?
On fresh framework laptop, a non blurry VS Code :)
Output of rpm-ostree status
No response
Output of groups
No response
Extra information or context
No response
The text was updated successfully, but these errors were encountered:
Yeah we could override the code.desktop but we're hesitant to do this per app since there's almost always some unintended consequence or config that users might be doing.
For now we recommend copying /usr/share/applications/code.desktop into ~.local/share/applications and then making the change in that file and then that'll sort it.
This should also be solved by F41, which is about to go to beta, and then maybe we recommend :stable for framework from then on? Or someone does a PR, whichever comes first I guess, hah.
Describe the bug
I have a fresh bluefin on my framework 13 laptop. I start vscode and it looks blurry. I checked web for the issue and found this closed one here: #1362
I followed the workaround to set
ELECTRON_OZONE_PLATFORM_HINT=auto
and then it works.My request would be to set this out of the box for Framework laptops such that users dont have to check the web to find this issue and apply the workaround themselfes. Thanks :)
What did you expect to happen?
On fresh framework laptop, a non blurry VS Code :)
Output of
rpm-ostree status
No response
Output of
groups
No response
Extra information or context
No response
The text was updated successfully, but these errors were encountered: