I don't run PipeWire and I have intention doing so. You can and feel free to do so. Sadly, it looks like PipeWire is going to be mandatory soon.
Anyway, I've noticed that my log is being spammed every 5 seconds like so:
Dec 06 21:28:10 myhost plasmashell[2565]: pw.conf: can't load config client.conf: No such file or directory Dec 06 21:28:10 myhost plasmashell[2565]: pw.conf: can't load config client.conf: No such file or directory
Creating an empty ~/.config/pipewire/client.conf did not improve the situation:
Dec 06 21:08:55 myhost plasmashell[2565]: pw.context: 0x59fa956abea0: no modules loaded from context.modules Dec 06 21:08:55 myhost plasmashell[2565]: pw.core: 0x59fa93de67d0: can't find protocol 'PipeWire:Protocol:Native': Operation not supported
Fortunately(or unfortunately?) it's not necessary to create a fake PipeWire daemon with socket etc. It seems that one needs to apt-get install libpipewire-0.3-modules(because there are no modules and we need to load least one?) and create a minimalistic ~/.config/pipewire/client.conf like so:
context.modules = [
# The native communication protocol.
{ name = libpipewire-module-protocol-native }
# The portal module monitors the PID of the portal process
# and tags connections with the same PID as portal
# connections.
{ name = libpipewire-module-portal
flags = [ ifexists nofail ]
}
]
which is probably “fatter” than it needs to be. Also, my ~/.config/pipewire/client.conf actually is “fatter”(not by much), because I haven't tried to trim it down once plasmashell log spam stopped.
Other things which might be useful for Debian 12 Bookworm to Debian 13 Trixie migration are:
kbuildsycoca6 –noincremental which should fix broken KDE after upgrade. If not, check Debian wiki for additional steps and actions.systemctl –user enable gnome-keyring-daemon.service which enables Gnome keyring daemon.— Zdenek Styblik 2025/12/07 15:18