Wayland "Vaapi unable to open Wayland display."
Closed this issue · 6 comments
When running on AMD w/ Wayland (KWin compositor) I'm getting this:
[D 2021-12-18 19:35:28] stun4 = 52.86.26.213:3478
[D 2021-12-18 19:35:29] net = BUD|::ffff:192.168.7.27|21740
[E 2021-12-18 19:35:29] Vaapi unable to open Wayland display.
[D 2021-12-18 19:35:29] decoder = software
[D 2021-12-18 19:35:37] Decoder failure, queued_frames=38
The problematic thing seems to be this "Vaapi unable to open Wayland display" line.
This is caused by #7. The following results in a working Wayland session with hardware accelerated decoding:
flatpak run --env=LIBVA_DRIVER_NAME=radeonsi --socket=wayland com.parsecgaming.parsec
Thanks, I can confirm that this is working!
@SISheogorath Not sure what the issue in #7 was but it seems to be resolved, what do you think about reverting it?
Also as a local but permanent solution:
flatpak override --socket=wayland com.parsecgaming.parsec
The driver name argument seems unnecessary
Uhm, @jgillich have you also removed X permissions, because I just tested and if I don't remove the X socket, it will continue to use X. And if I do remove the X socket, parsec will no longer start.
I have not, and Parsec also uses XWayland on my machine. But hardware decoding is working.
Not entirely sure what is going on but it seems like VAAPI requires the Wayland socket?
Parsec doesn't support Wayland directly according to this comment and if I'm reading the changelog for fallback-x11 right, isn't this only for apps that support both X11 and Wayland? Meaning that using it under a Wayland session the X11 socket will not be added. I think using both wayland and x11 is the solution here.
Parsec on the Steam Deck in Gaming Mode (Wich uses Gamescope, so wayland) is also not able to use vaapi and defaults to Software.