What | Removed | Added |
---|---|---|
Status | RESOLVED | REOPENED |
Resolution | FIXED | --- |
Ok, so, this bug is no longer consistently showing up after the update, but I seem to be able to reproduce it when I: - Switch users from my display manager - Awake the system after getting into stand-by Since pipewire is started for each specific user, it probably fails to reactivate at these points somehow. I have also seen cases where it does not play sound at one point and starts doing it a few minutes later.