Bug 1211716 - Pipewire-pulseaudio does not run as realtime process
Summary: Pipewire-pulseaudio does not run as realtime process
Status: NEW
Alias: None
Product: openSUSE Tumbleweed
Classification: openSUSE
Component: Sound (show other bugs)
Version: Current
Hardware: Other Other
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: Antonio Larrosa
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-05-25 10:08 UTC by Tamara Schmitz
Modified: 2023-06-05 11:17 UTC (History)
0 users

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Tamara Schmitz 2023-05-25 10:08:20 UTC
A fresh installation of opensuse Tumbleweed Snapshot20230522 Gnome role ships pipewire-pulse.
Yet neither pipewire nor pipewire-pulse seems to be running with a realtime priority, only an elevated niceness of -11. What gives?
The pipewire package explicitly requires rtkit. The pipewire module RT is responsible for configuring scheduling policies.

> # cat /proc/1469/sched
> pipewire (1469, #threads: 2)
> policy                                       :                    0
> prio                                         :                  109
> # cat /proc/1473/sched
> pipewire-pulse (1473, #threads: 2)
> policy                                       :                    0
> prio                                         :                  109

The logs of rtkit-daemon also indicates that a request for realtime priority was issued for children threads but those threads do not appear to stay around.

From all the documentation I have seen, pipewire *should* attempt to gain realtime priority. https://docs.pipewire.org/page_module_rt.html
Comment 1 Takashi Iwai 2023-06-05 11:17:10 UTC
Tossed to pipewire-* package maintainer.