dbus: Use ThreadPool instead of zbus blocking API

The `zbus` blocking API just wraps the async API with `block_on`, so we
may as well use our own executor.
This commit is contained in:
Ian Douglas Scott 2025-06-17 17:50:30 -07:00 committed by Ian Douglas Scott
parent 8455869439
commit 55401b1e53
5 changed files with 26 additions and 29 deletions

View file

@ -696,7 +696,9 @@ impl State {
);
let workspace_state = WorkspaceState::new(dh, client_not_sandboxed);
if let Err(err) = crate::dbus::init(&handle) {
let async_executor = ThreadPool::builder().pool_size(1).create().unwrap();
if let Err(err) = crate::dbus::init(&handle, &async_executor) {
tracing::warn!(?err, "Failed to initialize dbus handlers");
}
@ -712,7 +714,7 @@ impl State {
display_handle: dh.clone(),
event_loop_handle: handle,
event_loop_signal: signal,
async_executor: ThreadPool::builder().pool_size(1).create().unwrap(),
async_executor,
popups: PopupManager::default(),
shell,