Add support for explicit sync (nvidia xwayland glitches)

[xiaomx32]

Describe the bug
Open visual studio code in wayfire, the screen flashes, tears, and artifacts crazily.
When moving the mouse to the blinking and unable to load area, the situation improved slightly.
When using wayfire normally, there may also be slight flickering, especially after opening multiple windows and switching to other desktops(Tab + Alt).

To Reproduce
Steps to reproduce the behavior:

1. wayfire
2. yay -S visual-studio-code-bin
3. code test.cpp

Expected behavior
the code window can display normally

Software version

pacman -Qi wayfire-lily-git 
Name            : wayfire-lily-git
Version         : 0.11.0.20251127.144214.g23a101a0-1
Description     : 3D wayland compositor (lilydjwg's version)
Architecture    : x86_64
URL             : https://github.com/lilydjwg/wayfire
Licenses        : MIT
Groups          : None
Provides        : wayfire  wayfire-git
Depends On      : wlroots-lily-git  cairo  pango  glm  libjpeg  yyjson  libyyjson.so=0-64
Optional Deps   : None
Required By     : None
Optional For    : None
Conflicts With  : wayfire  wayfire-git
Replaces        : None
Installed Size  : 8.71 MiB
Packager        : lilydjwg <lilydjwg@gmail.com>
Build Date      : Thu 27 Nov 2025 11:13:02 PM CST
Install Date    : Fri 28 Nov 2025 11:31:39 AM CST
Install Reason  : Explicitly installed
Install Script  : No
Validated By    : SHA-256 Sum  Signature

pacman -Qi wlroots-lily-git 
Name            : wlroots-lily-git
Version         : 0.19.2.20251104.031626-1
Description     : Modular Wayland compositor library (with patches)
Architecture    : x86_64
URL             : https://gitlab.freedesktop.org/lilydjwg/wlroots
Licenses        : MIT
Groups          : None
Provides        : libwlroots-0.19.so=libwlroots-0.19.so-64  wlroots0.19=0.19.2.20251104.031626
Depends On      : libdisplay-info.so=3-64  libglvnd  libinput  liblcms2.so=2-64  libliftoff.so=0-64  libpixman-1.so=0-64  libseat.so=1-64  libudev.so=1-64  libvulkan.so=1-64
                  libwayland-client.so=0-64  libwayland-server.so=0-64  libxcb  libxkbcommon.so=0-64  opengl-driver  xcb-util-errors  xcb-util-renderutil  xcb-util-wm
Optional Deps   : xorg-xwayland: Xwayland support [installed]
                  xorg-xwayland-lily: HiDPI Xwayland support, see https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/733
Required By     : wayfire-lily-git
Optional For    : None
Conflicts With  : None
Replaces        : None
Installed Size  : 1615.16 KiB
Packager        : lilydjwg <lilydjwg@gmail.com>
Build Date      : Tue 04 Nov 2025 11:16:33 AM CST
Install Date    : Wed 05 Nov 2025 04:35:11 PM CST
Install Reason  : Installed as a dependency for another package
Install Script  : No
Validated By    : SHA-256 Sum  Signature

code --version
1.107.0
618725e67565b290ba4da6fe2d29f8fa1d4e3622
x64

Strangely, these cannot be seen from the screenshot.
Could it be a problem with my graphics card itself?

[soreau]

Some graphics drivers have problems synchronizing since there isn't a true sync point for the compositor to tell the driver where to finish rendering before presenting the content on the screen. This is especially true with nvidia proprietary drivers. There is a workaround in Wayfire for these cases. See the wiki for more information.

Do you happen to know if this application is single or double buffered?
Is the application native wayland or is it legacy x11?
You might try diabling direct scanout with WAYFIRE_DISABLE_DIRECT_SCANOUT=1 before starting wayfire.
Have you tested the application in any other compositors? Preferably something that uses the same wlroots version as Wayfire.

[xiaomx32]

@soreau Thank you very much for your answer, but please let me express my grievances.
I have just tried it, export WAYFIRE_DISABLE_DIRECT_SCANOUT=1 has no effect.

And when I set the environment variable WLR_DRM_NO_MODIFIERS=1(ref: #1397), it freezes when I run wayfire.

journalctl | grep -i nvidia
Dec 15 13:03:16 myname kernel: nvidia: loading out-of-tree module taints kernel.
Dec 15 13:03:16 myname kernel: nvidia: module verification failed: signature and/or required key missing - tainting kernel
Dec 15 13:03:16 myname kernel: nvidia-nvlink: Nvlink Core is being initialized, major device number 236
Dec 15 13:03:16 myname kernel: nvidia 0000:01:00.0: vgaarb: VGA decodes changed: olddecodes=io+mem,decodes=none:owns=none
Dec 15 13:03:16 myname kernel: NVRM: loading NVIDIA UNIX Open Kernel Module for x86_64  580.105.08  Release Build  (root@)  
Dec 15 13:03:16 myname systemd-modules-load[681]: Inserted module 'nvidia_uvm'
Dec 15 13:03:16 myname kernel: nvidia-modeset: Loading NVIDIA UNIX Open Kernel Mode Setting Driver for x86_64  580.105.08  Release Build  (root@)  
Dec 15 13:03:16 myname kernel: [drm] [nvidia-drm] [GPU ID 0x00000100] Loading driver
Dec 15 13:03:17 myname kernel: input: HDA NVidia HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input15
Dec 15 13:03:17 myname kernel: input: HDA NVidia HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input16
Dec 15 13:03:17 myname kernel: input: HDA NVidia HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input17
Dec 15 13:03:17 myname kernel: input: HDA NVidia HDMI/DP,pcm=9 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input18
Dec 15 13:03:18 myname kernel: [drm] Initialized nvidia-drm 0.0.0 for 0000:01:00.0 on minor 1
Dec 15 13:03:18 myname kernel: nvidia 0000:01:00.0: vgaarb: deactivate vga console
Dec 15 13:03:18 myname kernel: fbcon: nvidia-drmdrmfb (fb0) is primary device
Dec 15 13:03:18 myname kernel: nvidia 0000:01:00.0: [drm] fb0:nvidia-drmdrmfb frame buffer device
Dec 15 13:12:29 myname kernel: nvidia-modeset: ERROR: Invalid request parameters, planePitch or rmObjectSizeInBytes, passed during surface registration
Dec 15 13:12:29 myname kernel: nvidia-modeset: ERROR: Invalid request parameters, planePitch or rmObjectSizeInBytes, passed during surface registration
Dec 15 13:12:29 myname kernel: nvidia-modeset: ERROR: Invalid request parameters, planePitch or rmObjectSizeInBytes, passed during surface registration
Dec 15 13:12:29 myname kernel: nvidia-modeset: ERROR: Invalid request parameters, planePitch or rmObjectSizeInBytes, passed during surface registration
Dec 15 13:12:29 myname kernel: nvidia-modeset: ERROR: Invalid request parameters, planePitch or rmObjectSizeInBytes, passed during surface registration
Dec 15 13:12:29 myname kernel: nvidia-modeset: ERROR: Invalid request parameters, planePitch or rmObjectSizeInBytes, passed during surface registration

[ammen99]

@xiaomx32 Did you try the force_frame_sync option soreau mentioned?

[xiaomx32]

@xiaomx32 Did you try the force_frame_sync option soreau mentioned?

I just set the force_frame_sync option according to the instructions on the wiki, but it still doesn't work.

plugins = \
  ... \
  workarounds \
  zoom \
  input-method-v1

[workarounds]
force_frame_sync = true

[ammen99]

I believe that the proprietary nvidia drivers require explicit sync for xwayland to work properly. At least, this used to be the case in the past. Wayfire does not have explicit sync yet, however, so it is possible that you are hitting these issues. As a side note, I am using wayfire+nvidia+vulkan but I use only wayland-native applications, and for these cases, the force_frame_sync workaround is enough.

[killown]

Describe the bug Open visual studio code in wayfire, the screen flashes, tears, and artifacts crazily. When moving the mouse to the blinking and unable to load area, the situation improved slightly. When using wayfire normally, there may also be slight flickering, especially after opening multiple windows and switching to other desktops(Tab + Alt).

To Reproduce Steps to reproduce the behavior:

1. `wayfire`

2. `yay -S visual-studio-code-bin`

3. `code test.cpp`

Expected behavior the code window can display normally

give it a try for wayland mode: code --enable-features=UseOzonePlatform --ozone-platform=wayland

[xiaomx32]

Describe the bug Open visual studio code in wayfire, the screen flashes, tears, and artifacts crazily. When moving the mouse to the blinking and unable to load area, the situation improved slightly. When using wayfire normally, there may also be slight flickering, especially after opening multiple windows and switching to other desktops(Tab + Alt).
To Reproduce Steps to reproduce the behavior:

1. `wayfire`

2. `yay -S visual-studio-code-bin`

3. `code test.cpp`

Expected behavior the code window can display normally

give it a try for wayland mode: code --enable-features=UseOzonePlatform --ozone-platform=wayland

Are you sure the code has this option？

code --enable-features=UseOzonePlagform --ozone-platform=wayland .
Warning: 'enable-features' is not in the list of known options, but still passed to Electron/Chromium.

[killown]

Describe the bug Open visual studio code in wayfire, the screen flashes, tears, and artifacts crazily. When moving the mouse to the blinking and unable to load area, the situation improved slightly. When using wayfire normally, there may also be slight flickering, especially after opening multiple windows and switching to other desktops(Tab + Alt).
To Reproduce Steps to reproduce the behavior:

1. `wayfire`

2. `yay -S visual-studio-code-bin`

3. `code test.cpp`

Expected behavior the code window can display normally

give it a try for wayland mode: code --enable-features=UseOzonePlatform --ozone-platform=wayland

Are you sure the code has this option？

code --enable-features=UseOzonePlagform --ozone-platform=wayland .
Warning: 'enable-features' is not in the list of known options, but still passed to Electron/Chromium.

microsoft/vscode#207033 check out the comments

[xiaomx32]

Describe the bug Open visual studio code in wayfire, the screen flashes, tears, and artifacts crazily. When moving the mouse to the blinking and unable to load area, the situation improved slightly. When using wayfire normally, there may also be slight flickering, especially after opening multiple windows and switching to other desktops(Tab + Alt).
To Reproduce Steps to reproduce the behavior:

1. `wayfire`

2. `yay -S visual-studio-code-bin`

3. `code test.cpp`

Expected behavior the code window can display normally

give it a try for wayland mode: code --enable-features=UseOzonePlatform --ozone-platform=wayland

Are you sure the code has this option？
code --enable-features=UseOzonePlagform --ozone-platform=wayland .
Warning: 'enable-features' is not in the list of known options, but still passed to Electron/Chromium.

microsoft/vscode#207033 check out the comments

Thank you very much for providing the link. After trying some methods, the code still flashes.

[killown]

Describe the bug Open visual studio code in wayfire, the screen flashes, tears, and artifacts crazily. When moving the mouse to the blinking and unable to load area, the situation improved slightly. When using wayfire normally, there may also be slight flickering, especially after opening multiple windows and switching to other desktops(Tab + Alt).
To Reproduce Steps to reproduce the behavior:

1. `wayfire`

2. `yay -S visual-studio-code-bin`

3. `code test.cpp`

Expected behavior the code window can display normally

give it a try for wayland mode: code --enable-features=UseOzonePlatform --ozone-platform=wayland

Are you sure the code has this option？
code --enable-features=UseOzonePlagform --ozone-platform=wayland .
Warning: 'enable-features' is not in the list of known options, but still passed to Electron/Chromium.

microsoft/vscode#207033 check out the comments

Thank you very much for providing the link. After trying some methods, the code still flashes.

Try to check if it's really wayland mode: xprop | grep -i class
if after click the vscode window you get something like this : WM_CLASS(STRING) = "Navigator", "vscode ..." <- then it's still in xwayland mode

[xiaomx32]

Describe the bug Open visual studio code in wayfire, the screen flashes, tears, and artifacts crazily. When moving the mouse to the blinking and unable to load area, the situation improved slightly. When using wayfire normally, there may also be slight flickering, especially after opening multiple windows and switching to other desktops(Tab + Alt).
To Reproduce Steps to reproduce the behavior:

1. `wayfire`

2. `yay -S visual-studio-code-bin`

3. `code test.cpp`

Expected behavior the code window can display normally

give it a try for wayland mode: code --enable-features=UseOzonePlatform --ozone-platform=wayland

Are you sure the code has this option？
code --enable-features=UseOzonePlagform --ozone-platform=wayland .
Warning: 'enable-features' is not in the list of known options, but still passed to Electron/Chromium.

microsoft/vscode#207033 check out the comments

Thank you very much for providing the link. After trying some methods, the code still flashes.

Try to check if it's really wayland mode: xprop | grep -i class if after click the vscode window you get something like this : WM_CLASS(STRING) = "Navigator", "vscode ..." <- then it's still in xwayland mode

Click on the window of vscode, this command does not display any output.