[Bug]: Hardware video acceleration on Wayland

[zestygrass]

Guidelines

• I have encountered this bug in the latest release of FreeTube.
• I have encountered this bug in the official downloads of FreeTube.
• I have searched the issue tracker for open and closed issues that are similar to the bug report I want to file, without success.
• I have searched the documentation for information that matches the description of the bug I want to file, without success.
• This issue contains only one bug.

Describe the bug

I'm using freetube nightly build 3821, I wanted to try out the newly merged hardware video acceleration on Linux #4532.
It works as intended, if I'm using freetube on xwayland but does not work if freetube is running under wayland natively.

I used the following flags to use the hardware video acceleration on linux when using it under xwayland:

--enable-features=VaapiVideoDecodeLinuxGL

Run it natively on wayland I added the following flags:

--enable-features=WaylandWindowDecorations --ozone-platform-hint=auto --enable-features=VaapiVideoDecodeLinuxGL --gpu-context=wayland

Expected Behavior

Hardware video acceleration should work as intended on wayland.

Issue Labels

inconsistent behavior

FreeTube Version

v0.19.1-nightly-3821

Operating System Version

Fedora Linux 39

Installation Method

.rpm

Primary API used

Local API

Last Known Working FreeTube Version (If Any)

No response

Additional Information

Operating System: Fedora Linux 39
KDE Plasma Version: 5.27.10
KDE Frameworks Version: 5.111.0
Qt Version: 5.15.11
Kernel Version: 6.6.9-200.fc39.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 16 × 12th Gen Intel® Core™ i5-1240P
Memory: 31.1 GiB of RAM
Graphics Processor: Mesa Intel® Graphics
Manufacturer: Framework
Product Name: Laptop (12th Gen Intel Core)
System Version: A4

I have checked my drivers, I have the intel-media-drivers, Libva and Libva-utils installed.

Nightly Build

• I have encountered this bug in the latest nightly build.

[efb4f5ff-1298-471a-8973-3d47447115dc]

That PR was never meant for wayland, so that means wayland not working is intended behavior. Therefore this is not a bug and a feature request should be opened instead