VSCode is sluggish and buggy on Fedora 37 with wayland + Nvidia drivers
See original GitHub issueDoes this issue occur when all extensions are disabled?: Yes
- VS Code Version: 1.74.1/Insider
- OS Version: Fedora 37
- Additional information
item | value |
---|---|
Processor | AMD Ryzen™ 5 5600X × 12 |
GPU | NVIDIA GeForce GTX 1660 Ti; Driver version 525.60.11 |
GNOME Version | 43 |
Windowing system | Wayland |
OS type | 64 bit |
Memory | 32 GB |
Similar issue #134255 (closed and didn’t solve my issue)
VSCode stable and insider versions are sometimes unresponsive and buggy on my system when I am using Wayland with NVIDIA drivers on Fedora OS. This happens usually when I am typing on a input fields or hovering over buttons. I have tried to find a solutions to this problem like:
- Enabling Vulkan (
--enable-features=Vulkan
) (doesn’t work) - Disabling GPU (
--disable-gpu
) (doesn’t work) - Switching temporarily to X11 (works)
- Edit: Adding Wayland window decorations (
--ozone-platform="wayland" --enable-features="WaylandWindowDecorations"
) (doesn’t work)
Full list of problems (What i have noticed so there might be more problems):
- VSCode window flickers sometimes (black)
- Buttons are not always responsive
- Typing on input fields is buggy
Errors (code --verbose
):
'[9130:1218/182922.095257:WARNING:bluez_dbus_manager.cc(248)] Floss manager not present, cannot set Floss enable/disable.
libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null)
MESA-LOADER: failed to retrieve device information
MESA-LOADER: failed to open nvidia-drm: /usr/lib64/dri/nvidia-drm_dri.so: cannot open shared object file: Permission denied (search paths /usr/lib64/dri, suffix _dri)
failed to load driver: nvidia-drm
MESA-LOADER: failed to open zink: /usr/lib64/dri/zink_dri.so: cannot open shared object file: Permission denied (search paths /usr/lib64/dri, suffix _dri)
failed to load driver: zink
MESA-LOADER: failed to open kms_swrast: /usr/lib64/dri/kms_swrast_dri.so: cannot open shared object file: Permission denied (search paths /usr/lib64/dri, suffix _dri)
failed to load driver: kms_swrast
MESA-LOADER: failed to open swrast: /usr/lib64/dri/swrast_dri.so: cannot open shared object file: Permission denied (search paths /usr/lib64/dri, suffix _dri)
failed to load swrast driver
All of those errors come on Wayland, not on X11.
Steps to Reproduce:
- Open VSCode 1.74.1 or VSCode Insider on Fedora 37 with Wayland/NVIDIA
Issue Analytics
- State:
- Created 9 months ago
- Reactions:3
- Comments:6 (1 by maintainers)
Top Results From Across the Web
Is Wayland Still Bad With Nvidia? : r/Fedora - Reddit
It's buggy in multiple ways. Text stutters when typing. Sometimes there are flickers. Some apps display as white screens. I recently replaced my ......
Read more >sitemap_1.xml - Ask Fedora
https://ask.fedoraproject.org/t/own-wallpaper-for-each-desktop/3568 ... ask.fedoraproject.org/t/slow-mouse-move-for-second-system-user-on-nvidia-driver/8271 ...
Read more >What's new in Fedora 33 Workstation
As far as I know, wayland is not properly supported by nvidia drivers (EGLStreams) and that's why it's bad as opposed to AMD...
Read more >Native Wayland support : JBR-3206 - YouTrack
My experience with IntelliJ with sway in a Fedora 31 on a HiDPI levnovo laptop got very much improved when I switched to...
Read more >Bug listing with status UNCONFIRMED as at 2023/01/02 03 ...
Microsoft® SQL Server® ODBC Driver 1.0 for Linux" status:UNCONFIRMED ... when using nvidia's tegra drivers" status:UNCONFIRMED resolution: severity:normal ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Yeah, it appears that the issue exist outside of VSCode and likely is related to Electron, which is why this issue has been labeled as an upstream issue.
I use Chromium as my primary web browser and it works just fine.