How to reproduce:

1. Fresh boot machine
2. See expected realtime parameters
ps -e -o pri,ni,comm | grep wire
 30 -11 pipewire
 19   0 pipewire
 30 -11 wireplumber
 30 -11 pipewire-pulse
3. Restart the services
 systemctl --user restart pipewire wireplumber pipewire-pulse
4. See unexpected realtime parameters
ps -e -o pri,ni,comm | grep wire
 19   0 pipewire
 19   0 pipewire
 19   0 wireplumber
 19   0 pipewire-pulse

I could only reproduce on 25.04, the bug isn't reproducible in questing
or 24.04 for me interestingly. I suspected the culprit was xdg-desktop-
portal after seeing https://github.com/flatpak/xdg-desktop-
portal/issues/1653 - but that fix isn't on noble or questing anyway. The
only difference between plucky and questing's xdg-desktop-portal is a
rebuild for fuse3. It may also be a kernel behaviour. There's hasn't
been much excitement in the git log relating to module-rt.c in pipewire
across the versions from noble to questing...

** Bug watch added: github.com/flatpak/xdg-desktop-portal/issues #1653
   https://github.com/flatpak/xdg-desktop-portal/issues/1653

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2107340

Title:
  Pipewire fails to reacquire a realtime priority when restarted

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/2107340/+subscriptions


-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to