Bug 2183691

Summary: pipewire-gstreamer missing gstreamer-device-provider
Product: [Fedora] Fedora Reporter: Jamie Murphy <hello>
Component: pipewireAssignee: Wim Taymans <wtaymans>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 38CC: brunovern.a, information, robert.mader, wtaymans
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: pipewire-0.3.68-1.fc39 Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-04-06 11:08:49 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Jamie Murphy 2023-04-01 06:20:10 UTC
Description of problem:

The pipewire-gstreamer package provided in Fedora is missing the `pipewiredeviceprovider` device provider. It seems that the specfile has it disabled, due to old bugs in Cheese and Pipewire


Version-Release number of selected component (if applicable):

All published versions from F33 onward


Expected results:

The pipewiredeviceprovider would be present in the pipewire-gstreamer plugin


Additional info:

At least one camera app in development, Snapshot, relies on this plugin to get multimedia devices. Currently, we have to use Flatpak to develop this app, as running the app on a Fedora host crashes.

Comment 1 Robert Mader 2023-04-03 14:08:09 UTC
I did a quick test and could not reproduce the main issue from bug 1884260. Would be good if we got a bit more testing here. Jamie, IIUC you're now using a COPR to work around the issue - can you confirm it does not result in any regressions in Cheese for you?

Comment 2 Jamie Murphy 2023-04-03 15:55:02 UTC
Correct, I have a copr at https://copr.fedorainfracloud.org/coprs/jamie/pipewire/ which enables the device producer. I can test for regressions later today or tomorrow, unless someone else wants to test earlier

Comment 3 Jamie Murphy 2023-04-05 05:23:56 UTC
Tested, am unable to reproduce the issue when using my copr version

Comment 4 Fedora Update System 2023-04-06 11:04:00 UTC
FEDORA-2023-dd324e4ef0 has been submitted as an update to Fedora 39. https://bodhi.fedoraproject.org/updates/FEDORA-2023-dd324e4ef0

Comment 5 Fedora Update System 2023-04-06 11:08:49 UTC
FEDORA-2023-dd324e4ef0 has been pushed to the Fedora 39 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 6 Robert Mader 2023-04-06 11:17:02 UTC
According to Wim this will also get fixed in Fedora 38, not 37/36 though.