Your message dated Fri, 16 Sep 2022 14:36:19 +0000
with message-id <[email protected]>
and subject line Bug#1011399: fixed in pipewire 0.3.58-1
has caused the Debian Bug report #1011399,
regarding pipewire: create pipewire group with rlimits for
rtprio/priority/memlock
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.)
--
1011399: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011399
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: pipewire
Version: 0.3.51-1
Severity: wishlist
Dear Maintainer,
During the investigation of a scheduler priority issue in WirePlumber,
Niklāvs Koļesņikovs lamented Debian's use of RTKit for setting
scheduling priority[1], rather than a group with increased rlimits as
recommended in the Pipewire wiki.[2] Niklāvs noted some of the
benefits:[3]
1. RTKit does not support Flatpak, whereas RLIMITs do work inside user
namespaces.
2. RTKit usually does not go above priority 19 (though it should be
noted that there's some level of disagreement in the pro audio
community on what the appropriate priority for audio daemons [and
applications] should be).
3. RTKit is known to sometimes think that its canary thread is
starving when the system exits S3 sleep state, this will cause
RTKit to revoke realtime from all clients until at least the
particular client restarts (possibly also RTKit restart but I'm
not immediately sure if it's that bad). The exact mechanism is
unknown but speculated to happen if the canary thread or the
watchdog ends up frozen at particular point making it perceive a
huge realtime scheduling delay.
4. RTKit is actually abandoned with no upstream being interested or
active in fixing bugs such as the previously described canary
starvation issue. Worst of all the same will likely be true if a
security issue is discovered.
Additionally:
5. It would allow raising the memlock rlimit, not handled by RTKit.
6. It would allow creating the WirePlumber GLib thread pool threads
at a nice level matching the main thread and avoiding the
"Failed to set scheduler settings: Operation not permitted"
currently printed by wireplumber on startup.[4]
Perhaps it would make sense for the pipewire package to create a
pipewire group, configure the suggested rlimit values in a
/etc/security/limits.d/ file, and document use of the group in
README.Debian?
Thanks for considering,
Kevin
[1]:
https://gitlab.freedesktop.org/pipewire/wireplumber/-/issues/255#note_1393924
[2]:
https://gitlab.freedesktop.org/pipewire/pipewire/-/wikis/Performance-tuning#rlimits
[3]:
https://gitlab.freedesktop.org/pipewire/wireplumber/-/issues/255#note_1394696
[4]: https://gitlab.freedesktop.org/pipewire/wireplumber/-/issues/255
-- System Information:
Debian Release: bookworm/sid
APT prefers testing-debug
APT policy: (990, 'testing-debug'), (990, 'testing'), (500,
'unstable-debug'), (500, 'stable-debug'), (500, 'unstable'), (101,
'experimental'), (1, 'experimental-debug')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.18.0-rc7 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
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.62
ii libpipewire-0.3-modules 0.3.51-1
ii pipewire-bin 0.3.51-1
pipewire recommends no packages.
pipewire suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Source: pipewire
Source-Version: 0.3.58-1
Done: Dylan Aïssi <[email protected]>
We believe that the bug you reported is fixed in the latest version of
pipewire, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Dylan Aïssi <[email protected]> (supplier of updated pipewire package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Fri, 16 Sep 2022 15:41:31 +0200
Source: pipewire
Architecture: source
Version: 0.3.58-1
Distribution: unstable
Urgency: medium
Maintainer: Utopia Maintenance Team
<[email protected]>
Changed-By: Dylan Aïssi <[email protected]>
Closes: 998220 1011035 1011399 1013276 1019888
Changes:
pipewire (0.3.58-1) unstable; urgency=medium
.
[ Dylan Aïssi ]
* New upstream release
- Fix crackling sound if pavucontrol is open (Closes: #1019888)
* Create a pipewire group and define real-time priority limits
(Closes: #1011399)
* Add suggestion to install wireplumber in pipewire.README.Debian
* Clarify relation between pipewire and libspa-0.2-bluetooth in
pipewire.README.Debian (Closes: #998220, #1011035)
* Remove reference to experimental status of pipewire for audio
.
[ Sebastien Bacher ]
* Let pipewire-pulse conflicts on pulseaudio
(Closes: #1013276, LP: #1975823)
Checksums-Sha1:
338eebbf123cfe55a6b16068d8ee7bed1f868d32 4026 pipewire_0.3.58-1.dsc
9615d799815444c80a62fbc9eab6b745ad2a2b15 1432337 pipewire_0.3.58.orig.tar.bz2
8408802cc8c4dc2617af5dc81cba2440ecbdbc46 21476 pipewire_0.3.58-1.debian.tar.xz
149f06dc6b1e272229cea4a1bd9753c74dd1cbc6 23057
pipewire_0.3.58-1_amd64.buildinfo
Checksums-Sha256:
3280a2553bed4b618f4c37e6f1c3e780e19e40f29b0ce2727008e5f6513da936 4026
pipewire_0.3.58-1.dsc
975437d1aa3dfb1c873713b3908a42bf78495c0fd1d83e4bcb063c5e6c850edf 1432337
pipewire_0.3.58.orig.tar.bz2
a7935e88d6d0d104d6f6fb99e06677d63b8f7c33b9ea3f5db43288e8c7991419 21476
pipewire_0.3.58-1.debian.tar.xz
7292c5a406adcf5322ba0d937a8f09782d683c7382e63abec5f25f965914c106 23057
pipewire_0.3.58-1_amd64.buildinfo
Files:
25fed034e86fa0602ee38a8ad1fcd48d 4026 libs optional pipewire_0.3.58-1.dsc
4a14fa6db732b00957f835b09d47c406 1432337 libs optional
pipewire_0.3.58.orig.tar.bz2
298c70e55c2ef4152cde35d6be71e442 21476 libs optional
pipewire_0.3.58-1.debian.tar.xz
5f11cdea66382a40b38be1124bb6fd79 23057 libs optional
pipewire_0.3.58-1_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEmjwHvQbeL0FugTpdYS7xYT4FD1QFAmMkfqIACgkQYS7xYT4F
D1QPGQ/+OcMHhQkPmtkct3+TLEJtw/ahOhS2neZYHnojWcX057sICdkfX2+gaQsg
6YvBQ0bP6f1lPOwC0IgV2rSVw/PWMFWIss1rffwkg0b5KTv7a5U2rDpsbGUd9X76
HhSPzcbzNL/u+GqmcHhcTWG+K+hB5dP4zZvfN+KoJaE/exmCtVSeSYFDgxLGooMS
St6BQapID7b3I+8oUSd0ql4FZZAqnwL2EAaOiSyAER8UzftONqF6xUEEkLFMKvz8
fx83Y3QY2Ex79tXKmxz4hAS7MK51mizuP5ZWVIn36zI9TXOvw15CIDjl9hipVyuD
8yvAtaCoceAT/iwXQE4OjrqejFbWuxk6XS4NNPkngu8Wv66JRV1v1SN0z02MFJKq
USJmE0WBWT6MYpGCqkV1XiQzUMCPFJ7AryzZh2V/raUwqnCw6tKO2+cbm6h3//Wg
2PSYIAIc75LZyxYotneQY4uXuMkPyWiGg2ilkDeoH2+PyZ1r7EMjb5l3H0P5vw2p
Ie8BM3HupJqk6OSoGDQny08jQnT39JWeS9pTIA+QWr9H4HB8Rx7Z+oE0c9yfviYa
Wgjo0QbHOZh6qzzapOjRQTG3PegEuyM+2O0IbNtRL9+dKLfuu+oQ0950aWyM+qoE
FShl1bV/pNeQ/sD+Y0G+pTYg+VQqsH6UD45UtJLTvMjgFXlBl14=
=cd8l
-----END PGP SIGNATURE-----
--- End Message ---
