I want to share the exact timeline of how this bug behaves, as it provides a clear picture of its dependency on the PipeWire environment:
1.The Workaround Period: For a while, I had to run systemctl --user restart pipewire-pulse every single time before launching my games and OBS. This was the only way to prevent the crash. 2.The "Self-Healed" Period: After some time, the bug suddenly stopped manifesting on its own, even without running the restart command. I heavily tested this with several games (including Dying Light: The Beast and WUCHANG: Fallen Feathers), and the plugin worked perfectly fine with them for a period. 3.System Upgrades (No Impact): I update my system constantly as soon as new builds drop. I recently upgraded the kernel to Linux 7.2.6 and updated various other system components. None of these changes had any effect on the bug (it remained gone during this period), ruling out kernel-level scheduling or GPU/audio driver issues. 4.The Regressive Update: Recently, Ubuntu pushed a minor maintenance update to the current PipeWire package (not a major version bump, just minor downstream patches). Immediately after this update, the exact same deadlock issue returned. This confirms that the issue is highly sensitive to the internal timings and buffer sizes of the OS audio stack. Minor code adjustments by the OS maintainers broke the fragile stability we had, and now the dynamic stream creation triggers the bug again. I will go back to the launch order workaround for now. Thank you for your patience and insights! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2152817 Title: PipeWire/WirePlumber deadlock on Ubuntu 26.04 (Unity) when using Steam + MS Teams To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/2152817/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
