window protocol is reported as `wayland` (vs `wayland/drm`) despite dmabuf + vaapi working
Categories
(Core :: Widget: Gtk, defect, P3)
Tracking
()
People
(Reporter: cole.mickens, Unassigned)
References
(Blocks 1 open bug)
Details
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:85.0) Gecko/20100101 Firefox/85.0
Steps to reproduce:
I am working on NixOS's firefox packages and noticed they're all reporting wayland
instead of wayland/drm
now for Window Protocol
on the about:support
page.
However, when I use MOZ_LOG set to PlatformDecoderModule:5
or Dmabuf:5
then I am able to see the the GBM device is initialized AND vaapi appears to be working.
I've also read through the source code and believe I've met the conditions for window protocol to be set to WaylandDRM
and am rather confused as to what's going on.
Actual results:
about:support says Window Protocol is "wayland"
Expected results:
It should have said "wayland/drm".
Comment 1•5 years ago
|
||
Bugbug thinks this bug should belong to this component, but please revert this change in case of error.
Reporter | ||
Comment 2•5 years ago
|
||
Is it possible this is an intentional change, or a bug just in the displaying of "window protocol"?
Comment 3•5 years ago
|
||
That's set at GfxInfo::GetWindowProtocol(nsAString& aWindowProtocol)
at https://searchfox.org/mozilla-central/rev/927e525f481a93a8f63d27a78ae6201e42b1b1fb/widget/GfxInfoX11.cpp#919
I can confirm that bug.
Comment 4•4 years ago
|
||
@stransky I suppose this was closed by bug 1696937?
Comment 5•4 years ago
|
||
Yes, Thanks.
Description
•