[KRdp] [Bug 488858] New: Add option to force software H264 encoding even when a valid radeonsi device is present

Matt bugzilla_noreply at kde.org
Fri Jun 21 05:28:11 BST 2024


https://bugs.kde.org/show_bug.cgi?id=488858

            Bug ID: 488858
           Summary: Add option to force software H264 encoding even when a
                    valid radeonsi device is present
    Classification: Plasma
           Product: KRdp
           Version: 6.1.0
          Platform: Other
                OS: Linux
            Status: REPORTED
          Severity: minor
          Priority: NOR
         Component: general
          Assignee: unassigned-bugs at kde.org
          Reporter: m.mcnutt at gmail.com
                CC: ahiemstra at heimr.nl
  Target Milestone: ---

Distros such as Fedora Kinoite report hardware openh264 capability using
noopen264 package even tho it is not present. I am not fully across the
reasoning for it being this way, however krdpserver will attempt a session with
hardware encoding regardless and this results in a black screen on the client.

This can be worked around by adding a complex set of ostree overrides and
replaces, adding the rpmfusion repositories
(https://pagure.io/fedora-kde/SIG/issue/522). However if we could override
hardware encoding for software (knowing there is a performance hit), we could
use the krdp feature without having to pull apart our ostree. 

There may be other use cases for overriding hardware encoding (such as mesa
bugs https://github.com/stashapp/stash/issues/4701).

STEPS TO REPRODUCE
1. Run krdpserver on standard kinoite
2.  Connect via client get black screen


OBSERVED RESULT
Black screen

EXPECTED RESULT
Open264 video feed

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Fedora Kinoite 40 
(available in About System)
KDE Plasma Version: 6.1.0
KDE Frameworks Version: 6.3.0
Qt Version: 6.7.1

ADDITIONAL INFORMATION
Travier has stated adding openh264 to the base system remains problematic in
kinoite, this would get this feature into the hands of Kinoite users sooner

-- 
You are receiving this mail because:
You are the assignee for the bug.


More information about the Unassigned-bugs mailing list