I checked Lucid alpha 3 and saw generally less issues with pulseaudio.
But I cannot confirm this bug as fixed. If everything works then I don't
care about misleading log messages. But I have no other means than the
syslog to justify if nice-level and realtime-priority are correctly
applied. What I found in Lucid alpha 3:
Using log-level = info still shows discrepancy between syslog and
~/.pulse/daemon.conf:
rtkit-daemon[2651]: Sucessfully made thread 13763 of process 13763 (n/a)
owned by '114' high priority at nice level -11.
rtkit-daemon[2651]: Supervising 4 threads of 2 processes of 2 users.
pulseaudio[13763]: core-util.c: Successfully gained nice level -11.
...
rtkit-daemon[2651]: Sucessfully made thread 13765 of process 13763 (n/a)
owned by '114' RT at priority 5.
rtkit-daemon[2651]: Supervising 6 threads of 2 processes of 2 users.
pulseaudio[13763]: core-util.c: Successfully enabled SCHED_RR scheduling for
thread, with priority 5.
Whereas "pulseaudio --dump-conf" shows:
### Read from configuration file: /home/ubuntu/.pulse//daemon.conf ###
daemonize = no
fail = yes
high-priority = yes
nice-level = -10
realtime-scheduling = yes
realtime-priority = 6
...
It looks like pulseaudio now ignores the values in ~/.pulse/ completely
and takes those from /etc/pulse/. But --dump-conf shows the values from
~/.pulse/ like 'man pulse-daemon.conf' promises.
Further there are (I guess wrong) syslog messages like this:
pulseaudio[12777]: main.c: setrlimit(RLIMIT_NICE, (31, 31)) failed:
Operation not permitted
pulseaudio[12777]: main.c: setrlimit(RLIMIT_RTPRIO, (9, 9)) failed:
Operation not permitted
So please consider setting this bug back to confirmed. I will try to
find or open a corresponding upstream report.
--
Configuring the process priorites of pulseaudio is buggy
https://bugs.launchpad.net/bugs/502493
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
