Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Bug#1005067: pipewire-pulse/wireplumber breaks kde audio
400 views
Skip to first unread message
Eric Valette
Feb 6, 2022, 12:20:04 PM2/6/22
to
Package: pipewire-pulse
Version: 0.3.45-1
Severity: important
Today, wanted to liusten some music and discovered, I had no devices seen by kde
audio. Looked at the log.
got a bunch of:
1) /var/log/user.log.1:Feb 5 10:46:15 tri-yann4 pipewire-pulse[1824]: mod.protocol-pulse: client 0x557b90aba260 [kwin_killer_helper]: ERROR command:-1 (invalid) tag:106 error:25 (Input/output error)
2) /var/log/user.log.1:Feb 2 09:20:43 tri-yann4 pipewire-pulse[9372]: mod.rt: could not make thread 9380 realtime using RTKit: Permission denied
removed pipewire-pulse and rebooted. Got back my audio devices. Looked at debian page
for pipewire, reinstalled pipewire-pulse, wireplumber did the user space command to start
it via systemd, also rmove /etc/pipewire as suggested.
Rebooted. Still no audio.
aplay -L list the devices correctly but they are not acessible ...
-- System Information:
Debian Release: bookworm/sid
APT prefers stable-security
APT policy: (500, 'stable-security'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 5.10.96 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=fr_FR.UTF8, LC_CTYPE=fr_FR.UTF8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/bash
Init: systemd (via /run/systemd/system)
Versions of packages pipewire-pulse depends on:
ii init-system-helpers 1.61
ii pipewire 0.3.45-1
pipewire-pulse recommends no packages.
pipewire-pulse suggests no packages.
Version: 0.3.45-1
Severity: important
Today, wanted to liusten some music and discovered, I had no devices seen by kde
audio. Looked at the log.
got a bunch of:
1) /var/log/user.log.1:Feb 5 10:46:15 tri-yann4 pipewire-pulse[1824]: mod.protocol-pulse: client 0x557b90aba260 [kwin_killer_helper]: ERROR command:-1 (invalid) tag:106 error:25 (Input/output error)
2) /var/log/user.log.1:Feb 2 09:20:43 tri-yann4 pipewire-pulse[9372]: mod.rt: could not make thread 9380 realtime using RTKit: Permission denied
removed pipewire-pulse and rebooted. Got back my audio devices. Looked at debian page
for pipewire, reinstalled pipewire-pulse, wireplumber did the user space command to start
it via systemd, also rmove /etc/pipewire as suggested.
Rebooted. Still no audio.
aplay -L list the devices correctly but they are not acessible ...
-- System Information:
Debian Release: bookworm/sid
APT prefers stable-security
APT policy: (500, 'stable-security'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 5.10.96 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=fr_FR.UTF8, LC_CTYPE=fr_FR.UTF8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/bash
Init: systemd (via /run/systemd/system)
Versions of packages pipewire-pulse depends on:
ii init-system-helpers 1.61
ii pipewire 0.3.45-1
pipewire-pulse recommends no packages.
pipewire-pulse suggests no packages.
Eric Valette
Feb 6, 2022, 1:10:04 PM2/6/22
to
Did not downgrade to confirm as I need audio ATM.
-- eric
-- eric
Eric Valette
Feb 6, 2022, 4:40:03 PM2/6/22
to
sean dwyer
Feb 16, 2022, 1:10:04 AM2/16/22
to
I upgraded to wireplumber 0.4.8-2 today and it seems to be having the
same issue here. wireplumber could not see any devices at all, and
therefore there were no inputs/outputs for pipewire clients. The reason
I include it as part of this bug is that I resolved the issue by simply
installing pipewire-media-session which removes wireplumber and
rebooting. Now I have access to devices again. If the fix is indeed on
the alsa side well and good but perhaps wireplumber should not be so
dependent on proc filesystem niceties that it breaks the entire sound
infrastructure. I won't be too keen to return to it in any case.
--
I love deadlines. I love the whooshing noise they make as they go by.
same issue here. wireplumber could not see any devices at all, and
therefore there were no inputs/outputs for pipewire clients. The reason
I include it as part of this bug is that I resolved the issue by simply
installing pipewire-media-session which removes wireplumber and
rebooting. Now I have access to devices again. If the fix is indeed on
the alsa side well and good but perhaps wireplumber should not be so
dependent on proc filesystem niceties that it breaks the entire sound
infrastructure. I won't be too keen to return to it in any case.
--
I love deadlines. I love the whooshing noise they make as they go by.
Eric Valette
Feb 20, 2022, 12:50:03 PM2/20/22
to
On 17/02/2022 22:27, Debian Bug Tracking System wrote:
> This is an automatic notification regarding your Bug report
> which was filed against the pipewire-pulse package:
I confirm it WFM. Thanks.
-- eric
> This is an automatic notification regarding your Bug report
> which was filed against the pipewire-pulse package:
I confirm it WFM. Thanks.
-- eric
0 new messages