Your message dated Fri, 4 Aug 2023 13:36:48 +0200
with message-id
<ca+6xhwtaqdge3zkxwe7mjnakz2eokljfyx_iqu5a_dkaswt...@mail.gmail.com>
and subject line pipewire: rtkit-daemon race condition causes realtime
scheduling and nice-level failure
has caused the Debian Bug report #995357,
regarding pipewire: rtkit-daemon race condition causes realtime scheduling and
nice-level failure
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
995357: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995357
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: pipewire
Version: 0.3.37-2
Severity: normal
X-Debbugs-Cc: [email protected]
Dear Maintainer,
on boot, pipewire.service and pipewire-pulse.service can be started by
systemd before rtkit-daemon.service, causing the following errors:
systemd[1302]: Started PipeWire PulseAudio.
pipewire-pulse[1410]: RTKit error: org.freedesktop.DBus.Error.AccessDenied
pipewire-pulse[1410]: could not set nice-level to -11: Permission denied
pipewire-pulse[1410]: RTKit error: org.freedesktop.DBus.Error.AccessDenied
pipewire-pulse[1410]: could not make thread realtime: Permission denied
systemd[1302]: Started Multimedia Service.
pipewire[1408]: RTKit error: org.freedesktop.DBus.Error.AccessDenied
pipewire[1408]: could not set nice-level to -11: Permission denied
pipewire[1408]: RTKit error: org.freedesktop.DBus.Error.AccessDenied
pipewire[1408]: could not make thread realtime: Permission denied
In my case, rtkit-daemon starts, on average, 80ms after the pipewire processes.
Restarting them while making sure rtkit-daemon was running was enough for a
temporary solution.
Perhaps due to the difference in the number of systemd units, I wasn't able to
reproduce the issue on a clean install, but from reading the unit files, it
doesn't look like pipewire needs to wait for multi-user.target to complete or
for rtkit-daemon.service to be started.
-- System Information:
Debian Release: bookworm/sid
APT prefers testing
APT policy: (990, 'testing'), (490, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.14.0-1-amd64 (SMP w/8 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages pipewire depends on:
ii init-system-helpers 1.60
ii libpipewire-0.3-modules 0.3.37-2
ii pipewire-bin 0.3.37-2
pipewire recommends no packages.
pipewire suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 0.3.76-1
As said in the upstream bug and because these messages are no longer
displayed, I mark this bug as fixed with 0.3.76-1. But previous versions may
also no longer be affected since there were different improvements around
rtkit across latest versions.
--- End Message ---
_______________________________________________
Pkg-utopia-maintainers mailing list
[email protected]
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-utopia-maintainers
