Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Hardware Decoding on Steam Deck no longer working for flatpak version of Chiaki #17

Closed
ranger149 opened this issue Apr 18, 2023 · 2 comments

Comments

@ranger149
Copy link

ranger149 commented Apr 18, 2023

Context

Flatpak version

1.12.4

What Linux distribution are you using?

5.13.0-valve36-1-neptune (SteamOS)

What architecture are you using?

x86_64

Actual Behavior

  1. Update all apps on the KDE Discover store and Install either Moonlight or Chiaka from the KDE discover store (such as Moonlight or Chiaki).
  2. Launch said app, and get a hardware decoding error, such as it not being detected or available.
    This issue only occurs with two flatpak apps that I know of, Moonlight and Chiaki. The Moonlight AppImage does not have this issue. This issue is widespread for Steam Deck users:

See:

For example:

  • Moonlight states: No functioning hardware accelerated video decoder was detected.

  • Chiaki says failed to initialize FFMPEG decoder.

Further Info

I tested the flatpak MPV app, and was able to confirm hardware decoding was working in other applications

@swsnr
Copy link
Collaborator

swsnr commented Apr 19, 2023

Hardware decoding is provided by the underlying KDE runtime; there's nothing we can do here I believe.

I'm closing this issue because it's not actionable here; please report an issue to the KDE flatpak runtime.

Even if it turns out to be an issue here, a fix will have to come as a pull request. I don't own a steam deck device and have no means to work on any issue specific to that device.

@swsnr swsnr closed this as not planned Won't fix, can't repro, duplicate, stale Apr 19, 2023
@ranger149
Copy link
Author

Thank you, It has since been reported and I believe a solution should be coming shortly. Take care.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants