As the title suggest, PipeWire Multimedia Service is significantly slowing down the logout process on Gnome 43, Ubuntu 22.10. It seems to start shutting down roughly 10 seconds after all the other processes have already ended. I've included the last log entries of a session shutdown below. As you can see, there is a 10 second gap before systemd starts killing PipeWire. Any idea how this can be fixed? I've included the relevant log entries below.
18:53:18 systemd: Reached target Exit the Session.
18:53:18 dbus-update-act: dbus-update-activation-environment: error: unable to connect to D-Bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
18:53:18 systemd: Stopped PipeWire Multimedia Service.
18:53:18 systemd: Stopped PipeWire Multimedia Service.
18:53:18 systemd: Stopping PipeWire Multimedia Service...
18:53:18 systemd: Stopped PipeWire Media Session Manager.
18:53:18 systemd: ssh-agent.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
18:53:18 systemd: Stopped GCR ssh-agent wrapper.
18:53:18 systemd: Stopping OpenSSH Agent...
18:53:18 systemd: Stopping PipeWire Media Session Manager...
18:53:18 systemd: Stopping GCR ssh-agent wrapper...
18:53:18 systemd: Stopped target Main User Target.
18:53:18 systemd: background.slice: Consumed 2.873s CPU time.
18:53:18 systemd: Removed slice User Background Tasks Slice.
18:53:18 systemd: app-org.gnome.Terminal.slice: Consumed 4.971s CPU time.
18:53:18 systemd: Removed slice Slice /app/org.gnome.Terminal.
18:53:18 systemd: app-gnome\x2dsession\x2dmanager.slice: Consumed 1.012s CPU time.
18:53:18 systemd: Removed slice Slice /app/gnome-session-manager.
18:53:18 systemd: Stopped Application launched by gnome-session-binary.
18:53:18 systemd: Activating special unit Exit the Session...
18:53:08 systemd: tracker-miner-fs-3.service: Consumed 2.780s CPU time.
18:53:08 pulseaudio: After module unload, module 'module-null-sink' was still loaded!
