figaro
January 25, 2025, 11:43pm
10
1 year and a half later the issue is still prevalent. Following your advice, I found a way to mitigate this by adding specific flags for the applications to run natively in Wayland:
The solution is to disable 'xwayland-native-scaling'. The dconf experimental features entry should look just like this:
org.gnome.mutter experimental-features ['scale-monitor-framebuffer']
Then, in order to fix the blurriness of Electron based apps, you must run them natively in Wayland.
For the Chromium case:
Go to chrome://flags/
Search for the option Preferred Ozone platform
Change it from Default to Wayland.
For the VS Code case:
Open with a text editor the file /usr/share/applicatio…
However, by running natively in Wayland I faced with other issues related to the input of dead keys. I recently reported an issue to the vscode github page:
opened 10:00PM - 25 Jan 25 UTC
Does this issue occur when all extensions are disabled?: Yes/No
- VS Code Ver… sion: 1.96.4
```
$ code --version
1.96.4
cd4ee3b1c348a13bafd8f9ad8060705f6d4b9cba
x64
```
- OS Version: Fedora Linux 41
```
$ inxi -b
System:
Host: me Kernel: 6.12.8-200.fc41.x86_64 arch: x86_64 bits: 64
Desktop: GNOME v: 47.2 Distro: Fedora Linux 41 (Workstation Edition)
```
Steps to Reproduce:
1. Have a keyboard layout that supports dead keys. In my case, I'm interested in the dead circumflex or caret: "^"
<img src="https://github.com/user-attachments/assets/34385b85-d063-49dc-8513-69493804ccca" width="50%" height="50%" />
2. Dead circumflex is activated by pressing "Alt Gr" + "{" like this image shows:
<img src="https://github.com/user-attachments/assets/ac7ecb0d-08ff-47a7-ac8e-0f9b460d040f" width="50%" height="50%" />
3. Then press any other key (like "p") that doesn't trigger the circumflex.
Expected result:
In any other GNOME application, using the dead circumflex "^" and then "p" types "^p" as the following video shows
Obtained result:
In VSCode instead, doing this doesn't type anything:
Have you found any solution to this issue in this time?