Closed Bug 1690164 Opened 5 years ago Closed 4 years ago

window protocol is reported as `wayland` (vs `wayland/drm`) despite dmabuf + vaapi working

Categories

(Core :: Widget: Gtk, defect, P3)

Firefox 85
defect

Tracking

()

RESOLVED DUPLICATE of bug 1696937

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".

Bugbug thinks this bug should belong to this component, but please revert this change in case of error.

Component: Untriaged → Widget: Gtk
Product: Firefox → Core

Is it possible this is an intentional change, or a bug just in the displaying of "window protocol"?

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.

Blocks: wayland
Priority: -- → P3

@stransky I suppose this was closed by bug 1696937?

Yes, Thanks.

Status: UNCONFIRMED → RESOLVED
Closed: 4 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.