From d46d1d3a5897cade51811b3848c7bf27969da625 Mon Sep 17 00:00:00 2001 From: V3n3RiX Date: Thu, 28 Dec 2023 07:37:55 +0000 Subject: gentoo auto-resync : 28:12:2023 - 07:37:55 --- ...st-prevent-crash-stopping-device-provider.patch | 34 ---------------------- .../0.3.77/0002-pulse-prevent-duplicates.patch | 28 ------------------ 2 files changed, 62 deletions(-) delete mode 100644 media-video/pipewire/files/0.3.77/0001-gst-prevent-crash-stopping-device-provider.patch delete mode 100644 media-video/pipewire/files/0.3.77/0002-pulse-prevent-duplicates.patch (limited to 'media-video/pipewire/files') diff --git a/media-video/pipewire/files/0.3.77/0001-gst-prevent-crash-stopping-device-provider.patch b/media-video/pipewire/files/0.3.77/0001-gst-prevent-crash-stopping-device-provider.patch deleted file mode 100644 index 9b6373da1390..000000000000 --- a/media-video/pipewire/files/0.3.77/0001-gst-prevent-crash-stopping-device-provider.patch +++ /dev/null @@ -1,34 +0,0 @@ -https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/140374d2071e6204fded4ca65645d4e9a3dd053e -https://bugs.webkit.org/show_bug.cgi?id=259735 - -From 140374d2071e6204fded4ca65645d4e9a3dd053e Mon Sep 17 00:00:00 2001 -From: Philippe Normand -Date: Fri, 4 Aug 2023 10:01:07 +0100 -Subject: [PATCH] gst: Prevent a crash when stopping device provider - -The provider might fail to connect to the PipeWire core when starting up, so -when stopping we need to check the core is valid before attempting to acquire a -mutex on its loop. ---- a/src/gst/gstpipewiredeviceprovider.c -+++ b/src/gst/gstpipewiredeviceprovider.c -@@ -665,11 +665,16 @@ gst_pipewire_device_provider_stop (GstDeviceProvider * provider) - { - GstPipeWireDeviceProvider *self = GST_PIPEWIRE_DEVICE_PROVIDER (provider); - -- pw_thread_loop_lock (self->core->loop); -+ /* core might be NULL if we failed to connect in _start. */ -+ if (self->core != NULL) { -+ pw_thread_loop_lock (self->core->loop); -+ } - GST_DEBUG_OBJECT (self, "stopping provider"); - - g_clear_pointer ((struct pw_proxy**)&self->registry, pw_proxy_destroy); -- pw_thread_loop_unlock (self->core->loop); -+ if (self->core != NULL) { -+ pw_thread_loop_unlock (self->core->loop); -+ } - g_clear_pointer (&self->core, gst_pipewire_core_release); - } - --- -GitLab diff --git a/media-video/pipewire/files/0.3.77/0002-pulse-prevent-duplicates.patch b/media-video/pipewire/files/0.3.77/0002-pulse-prevent-duplicates.patch deleted file mode 100644 index 5a0fcde67fed..000000000000 --- a/media-video/pipewire/files/0.3.77/0002-pulse-prevent-duplicates.patch +++ /dev/null @@ -1,28 +0,0 @@ -https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/820ca90705ae78124958f1b96de3bdc7889c2d1e -https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3414 - -From 820ca90705ae78124958f1b96de3bdc7889c2d1e Mon Sep 17 00:00:00 2001 -From: Wim Taymans -Date: Tue, 8 Aug 2023 13:01:30 +0200 -Subject: [PATCH] pulse-server: set all change_mask flags when removing - -So that the logic to emit events will select sink and source objects. - -Fixes #3414 ---- a/src/modules/module-protocol-pulse/manager.c -+++ b/src/modules/module-protocol-pulse/manager.c -@@ -641,9 +641,10 @@ static void registry_event_global_remove(void *data, uint32_t id) - - o->this.removing = true; - -- if (!o->this.creating) -+ if (!o->this.creating) { -+ o->this.change_mask = ~0; - manager_emit_removed(m, &o->this); -- -+ } - object_destroy(o); - } - --- -GitLab -- cgit v1.2.3