Now that we have a good support with openh264 & ffmpeg in Fedora, adding a media player by default should let user play a good chunk of media easily.
Extracted from https://pagure.io/fedora-kde/SIG/issue/13#comment-857211
On Kinoite it will be included as a Flatpak, on the Spin as an RPM.
Metadata Update from @siosm: - Issue tagged with: kinoite
Metadata Update from @siosm: - Issue tagged with: meeting
Comps PR: https://pagure.io/fedora-comps/pull-request/844
Edit: Whoops, wrong issue.
I have a prototype for the flatpak, but without a runtime extension or the like for openh264, I'm not sure how useful it will be.
No decision so far. We need to compare functionality / codec support between Dragon Player & Haruna.
Metadata Update from @siosm: - Issue untagged with: meeting
I have used both and while not extensively my preference is for Haruna.
Verified on a virtual machine that Haruna can play H264 out of the box. Dragon instead currently fails (!) with
** Message: 23:12:06.241: PackageKit: xid = 0 ** Message: 23:12:06.241: PackageKit: desktop_id = (null) ** Message: 23:12:06.241: PackageKit: Codec nice name: H.264 (High Profile) decoder ** Message: 23:12:06.241: PackageKit: ignoring field named level ** Message: 23:12:06.241: PackageKit: ignoring field named profile ** Message: 23:12:06.241: PackageKit: ignoring field named coded-picture-structure ** Message: 23:12:06.241: PackageKit: ignoring field named chroma-format ** Message: 23:12:06.241: PackageKit: ignoring field named bit-depth-luma ** Message: 23:12:06.241: PackageKit: ignoring field named bit-depth-chroma ** Message: 23:12:06.241: PackageKit: structure: gstreamer1(decoder-video/x-h264)()(64bit) ** Message: 23:12:06.246: PackageKit: Did not install codec: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name is not activatable
I don't think auto-installation of codecs works with Plasma Discover at all right now.
mmmh i'm not sure where would Discover be involved at all?
Discover is the frontend for PackageKit. In order for package installation to work with PackageKit, the frontend needs to be able to handle the signal and do something with it.
The failure to install gstreamer1-plugin-openh264 was caused by the request not being able to be handled by Discover.
gstreamer1-plugin-openh264
Eh? Doesn't make sense to me. PackageKit is completely indipendent of Discover. Requests go from clients to PackageKit through dbus, then PackageKit runs libdnf.
In facts the error would indicate that pk-gstreamer-install fails to find org.freedesktop.PackageKit on the bus
pk-gstreamer-install
org.freedesktop.PackageKit
Apparently something is supposed to implement a session version of packagekit implementing org.freedesktop.PackageKit.Modify? Oh well; i don't know.
org.freedesktop.PackageKit.Modify
That's supposed to be Plasma Discover. GNOME Software does it for GNOME.
Update from the meeting: If Haruna is preinstalled, it won't pull in the weak dependency on openh264 so it wouldn't be able to play h264 video.
This is held off until openh264 can be installed from an initial setup wizard
-- side note, at the moment installing Haruna would also not pull openh264 because it is a weak dependency of libavcodec and that is itself preinstalled as a dependency of Plasma. openh264 needs to be added as an mpv weak dependency.
Note that the openh264 can not be included in any of our images (KDE Spin our Kinoite) by default for licensing reasons: https://fedoraproject.org/wiki/OpenH264
openh264
This is why Neal created https://fedoraproject.org/wiki/Changes/AutoFirstBootServices
Adding that as a page in plasma-welcome is indeed a good option.
See: https://pagure.io/fedora-kde/SIG/issue/295
https://bodhi.fedoraproject.org/updates/FEDORA-FLATPAK-2023-c1141e751c
Log in to comment on this ticket.