[destroyed object]: error 7: importing the supplied dmabufs failed about qutebrowser HOT 6 CLOSED

When/how does that happen? Just when starting? Could you try running the testbrowser script please?

from qutebrowser.

When/how does that happen? Just when starting?

Yes. At start. No issues in i3/x11.

$[~]$ qutebrowser
17:25:09 INFO: Run :adblock-update to get adblock lists.
libva error: vaGetDriverNames() failed with unknown libva error

Could you try running the testbrowser script please?

$[~]$ python run/testbrowser_webengine.py 
Using PyQt6
doh set to ""  --  SystemOnly
Loading started
Loading progress: 0%
[destroyed object]: error 7: importing the supplied dmabufs failed
The Wayland connection broke. Did the Wayland compositor die?

Nvidia issue ? Caz chrome also throws some dmabuf issue on VaapiDecoding, which currently fails.

from qutebrowser.

Closing this as an upstream issue in QtWebEngine.

I try to report bugs upstream when I can easily reproduce them, but unfortunately this wasn't the case here. Since I'll be unable to provide any follow-up information when being asked, could you please report the bug to the Qt Bugtracker yourself? Please use "Project: Qt (QTBUG)" and "Component: WebEngine" there. After reporting the bug, it'd be good if you could post the link to it here!

from qutebrowser.

Trying NVD_BACKEND=direct env var gives a different warning

[destroyed object]: error 7: importing the supplied dmabufs failed
17:50:23 WARNING: The Wayland connection experienced a fatal error: Protocol error

Protocol 'direct' does exist btw.
vainfo: Driver version: VA-API NVDEC driver [direct backend]

from qutebrowser.

Seems to be a nvidia issue. Related issues:

• https://gitlab.freedesktop.org/mstoeckl/waypipe/-/issues/50
• NVIDIA/egl-wayland#83

from qutebrowser.

@vimproved Tqvm for providing direction.

from qutebrowser.