Bug#1038627: general: Various applications log PipeWire-related errors on a Bookworm system using PulseAudio.
Package: general
Severity: minor
X-Debbugs-Cc: splashed_overbuilt840@simplelogin.com
Dear Maintainer,
After upgrade to Bookworm, due to certain limitations of the current
PipeWire implementation I had to switch to PulseAudio. The switch was
done by installing pulseaudio package, deleting all PipeWire packages and
finally enabling pulseaudio service on a user level.
After several reboots and usage of various applications I've noticed
strange errors (visible using journalctl -p 3 -xb) logged that looked as
follows:
"pw.conf: can't load default config client.conf: No such file or directory"
Primarily this error was logged by mpv and Telegram applications.
Investigation of several sources has shown that maybe creation of an empty
~/.config/pipewire/client.conf" file might fix the error.
And indeed it fixed the original error, but procreated a new type of errors:
that look as follows:
Jun 19 07:01:41 Yura-PC xdg-desktop-portal[1768]: pw.core: 0x55d8ca82c830: can't find protocol 'PipeWire:Protocol:Native': Operation not supp>
Jun 19 07:01:42 Yura-PC Telegram[1528]: pw.core: 0x7f78f6ff3d80: can't find protocol 'PipeWire:Protocol:Native': Operation not supported
Jun 19 08:48:37 Yura-PC mpv[4283]: pw.core: 0x5630b5b7c9f0: can't find protocol 'PipeWire:Protocol:Native': Operation not supported
Jun 19 08:51:12 Yura-PC mpv[3200]: pw.core: 0x56312d870420: can't find protocol 'PipeWire:Protocol:Native': Operation not supported
Jun 19 08:52:14 Yura-PC mpv[3200]: pw.core: 0x56312d7eff10: can't find protocol 'PipeWire:Protocol:Native': Operation not supported
Jun 19 08:55:55 Yura-PC mpv[3200]: pw.core: 0x56312d8549b0: can't find protocol 'PipeWire:Protocol:Native': Operation not supported
Jun 19 08:56:19 Yura-PC mpv[3200]: pw.core: 0x56312d8845d0: can't find protocol 'PipeWire:Protocol:Native': Operation not supported
Jun 19 09:00:53 Yura-PC mpv[3200]: pw.core: 0x56312d7cc000: can't find protocol 'PipeWire:Protocol:Native': Operation not supported
Jun 19 09:01:12 Yura-PC mpv[3200]: pw.core: 0x56312d883d40: can't find protocol 'PipeWire:Protocol:Native': Operation not supported
Jun 19 09:03:41 Yura-PC mpv[3200]: pw.core: 0x56312d865130: can't find protocol 'PipeWire:Protocol:Native': Operation not supported
Jun 19 09:05:15 Yura-PC mpv[3200]: pw.core: 0x56312d7fe5d0: can't find protocol 'PipeWire:Protocol:Native': Operation not supported
Jun 19 09:07:39 Yura-PC mpv[3200]: pw.core: 0x56312d857cf0: can't find protocol 'PipeWire:Protocol:Native': Operation not supported
Jun 19 09:09:31 Yura-PC mpv[3200]: pw.core: 0x56312d7f5740: can't find protocol 'PipeWire:Protocol:Native': Operation not supported
Jun 19 09:10:56 Yura-PC mpv[3200]: pw.core: 0x56312d85e1e0: can't find protocol 'PipeWire:Protocol:Native': Operation not supported
Jun 19 09:11:50 Yura-PC mpv[3200]: pw.core: 0x56312d8837c0: can't find protocol 'PipeWire:Protocol:Native': Operation not supported
Jun 19 09:15:30 Yura-PC mpv[3200]: pw.core: 0x56312d8656a0: can't find protocol 'PipeWire:Protocol:Native': Operation not supported
Jun 19 09:16:07 Yura-PC mpv[3200]: pw.core: 0x56312d802ab0: can't find protocol 'PipeWire:Protocol:Native': Operation not supported
Jun 19 09:18:11 Yura-PC mpv[3200]: pw.core: 0x56312d861820: can't find protocol 'PipeWire:Protocol:Native': Operation not supported
Jun 19 09:19:02 Yura-PC mpv[3200]: pw.core: 0x56312d85e270: can't find protocol 'PipeWire:Protocol:Native': Operation not supported
Jun 19 09:20:36 Yura-PC mpv[3200]: pw.core: 0x56312d8828a0: can't find protocol 'PipeWire:Protocol:Native': Operation not supported
Jun 19 09:22:40 Yura-PC mpv[3200]: pw.core: 0x56312d7f7e40: can't find protocol 'PipeWire:Protocol:Native': Operation not supported
Jun 19 09:32:29 Yura-PC mpv[3200]: pw.core: 0x56312d8851a0: can't find protocol 'PipeWire:Protocol:Native': Operation not supported
Jun 19 09:33:17 Yura-PC mpv[3200]: pw.core: 0x56312d8e0540: can't find protocol 'PipeWire:Protocol:Native': Operation not supported
So it seems these are PipeWire-related errors logged on a system that
doesn't use this audio subsystem.
The expectation is that such errors aren't logged.
It's worth noting that both input and output audio work fine, despite
the error being logged.
Best Regards,
Yura
Reply to: