Skip to content

[docs] Documenting Nvidia problems in Tauri #9394

Open

Description

@ImUrX

I'm making an issue so a document exists that includes problems seen in WebkitGTK2. I will be listing the errors I have found and fixes for them, and also problems that I find that are weird.

1. The most common one, not having nvidia_drm.modeset=1

This one is mostly needed in Nvidia versions that are < 545, I need to test but there is a new flag since then that is nvidia_drm.fbdev=1 which actually enables simpledrm once again, but I don't know if it works.

2. In newer WebkitGTK versions since WebGL2 was implemented, WebGL doesn't work

There a simple bypass for this, it's using Wayland, for some reason this actually only happens on X11. It really seems like a weird upstream error, but it's probably not gonna get fixed anytime soon as GNOME's efforts are mostly on Wayland nowadays


The next issues are more recent and require flags on the environment that make the behavior of WebkitGTK not use hardware acceleration or not DMABUF, I find this pretty bad tbh.

3. AcceleratedSurfaceDMABuf was unable to construct a complete framebuffer

Requires to have WEBKIT_DISABLE_DMABUF_RENDERER=1 in the environment, it seems to happen on X11

4. Gdk-Message: 23:55:52.007: Error 71 (Protocol error) dispatching to Wayland display.

Requires to have WEBKIT_DISABLE_DMABUF_RENDERER=1 in the environment, it seems to happen on Wayland

5. The webview just dies on resize, there is no weird error output

Requires to have WEBKIT_DISABLE_COMPOSITING_MODE=1 in the environment, if it's happening in Wayland, your Webview is running on X11


5 are weird as they both happen to me in EndeavourOS GNOME Wayland in latest version but when using an AppImage from Ubuntu 22.04 (Github Actions Image) and using Tauri 2 Beta 14.
If I use a development build with the libraries that Arch Linux ships, it runs on Wayland perfectly.
I don't know why, it probably needs to be another issue as it's a problem with the AppImage packaging not using Wayland

Activity

  1. tobico commented on Mar 23, 2025

    @tobico

    For the Error 71 (Protocol error) issue, an alternative workaround is setting __NV_DISABLE_EXPLICIT_SYNC=1.

  2. konyogony commented on Aug 13, 2025

    @konyogony

    For the Error 71 (Protocol error) issue, an alternative workaround is setting __NV_DISABLE_EXPLICIT_SYNC=1.

    This is the first fix which doesn't degrade the performance of my app heavily, thank you sir.

  3. ll931217 commented on Jan 24, 2026

    @ll931217

    Jean (https://github.com/coollabsio/jean) now implements automatic fixes for NVIDIA/GBM buffer errors on Linux (see #13493, #8254).

    Implementation:

    Manual Override Options:
    Users can still force Wayland/GPU acceleration via environment variables if needed (see troubleshooting guide).

  4. BinToss commented on Jan 24, 2026

    @BinToss

    Jean (https://github.com/coollabsio/jean) now implements automatic fixes for NVIDIA/GBM buffer errors on Linux (see #13493, #8254).

    Implementation:

    Manual Override Options:
    Users can still force Wayland/GPU acceleration via environment variables if needed (see troubleshooting guide).

    __NV_DISABLE_EXPLICIT_SYNC=1 has less/no performance cost. See the two replies before yours for reference.

  5. 19 remaining items

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions