From 8dcc41a54d2606bab2d0e950f4b67668b48d9750 Mon Sep 17 00:00:00 2001
From: Ivan Molodetskikh <yalterz@gmail.com>
Date: Sun, 22 Dec 2024 11:00:17 +0300
Subject: Initialize PipeWire lazily

This helps with:
- System setups starting PipeWire late (after niri startup, but before any
  screencast).
- Tests which don't even want to start PipeWire.
---
 src/dbus/mod.rs | 4 +---
 1 file changed, 1 insertion(+), 3 deletions(-)

(limited to 'src/dbus')

diff --git a/src/dbus/mod.rs b/src/dbus/mod.rs
index eab72ce7..a231a1d1 100644
--- a/src/dbus/mod.rs
+++ b/src/dbus/mod.rs
@@ -83,7 +83,7 @@ impl DBusServers {
             dbus.conn_introspect = try_start(introspect);
 
             #[cfg(feature = "xdp-gnome-screencast")]
-            if niri.pipewire.is_some() {
+            {
                 let (to_niri, from_screen_cast) = calloop::channel::channel();
                 niri.event_loop
                     .insert_source(from_screen_cast, {
@@ -95,8 +95,6 @@ impl DBusServers {
                     .unwrap();
                 let screen_cast = ScreenCast::new(backend.ipc_outputs(), to_niri);
                 dbus.conn_screen_cast = try_start(screen_cast);
-            } else {
-                warn!("disabling screencast support because we couldn't start PipeWire");
             }
         }
 
-- 
cgit