I also have started hearing occasional crackling in the last few months in debian sid. It was fine in Jan-Feb, and appeared maybe in March-April. My PW has always been running with RT prio, maybe this is a kernel regression?
Roman. On Mon, May 26, 2025 at 3:09 PM gigaqueen <deb...@4-science.com> wrote: > > Package: pipewire > Version: 1.4.2-1 > Severity: important > X-Debbugs-Cc: deb...@4-science.com > > Dear Maintainer, > There is a problem with Trixie's current Pipewire version. > > * What led up to the situation? > This issue began when I upgraded to Debian Trixie. It was not present > in Bookworm. > > * What exactly did you do (or not do) that was effective (or > ineffective)? > I attempted the following fixes: > > Made a file in /etc/security/limits.d/50-pw-rlimits.conf > File Contents: > @pipewire - rtprio 95 > @pipewire - nice -19 > @pipewire - memlock 4194304 > > * What was the outcome of this action? > The issue remained unaffected. > > * What outcome did you expect instead? > Not applicable - I was attempting to apply this fix > > > > -- System Information: > Debian Release: 13.0 > APT prefers testing > APT policy: (500, 'testing') > Architecture: amd64 (x86_64) > Foreign Architectures: i386 > > Kernel: Linux 6.12.27-amd64 (SMP w/12 CPU threads; PREEMPT) > Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, > TAINT_UNSIGNED_MODULE > Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), > LANGUAGE=en_AU: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 adduser 3.152 > ii init-system-helpers 1.68 > ii libpipewire-0.3-modules 1.4.2-1 > ii pipewire-bin 1.4.2-1 > > pipewire recommends no packages. > > pipewire suggests no packages. > > -- no debconf information >
