Adding the mailing list back. The message was sent off-list by mistake,
so overquoting.
On 10/01/2025 19:15, Haines Brown wrote:
On Fri, Jan 10, 2025 at 10:01:57AM +0700, Max Nikulin wrote:
On 09/01/2025 21:15, Greg Wooledge wrote:
Moral of the story: NEVER EVER run "wpctl".
My guess is that it may be a consequence of "wireplumber" you executed
earlier. Having no notion what particular components of pipewire/pulse do, I
would avoid running random commands supposed to be started as services. They
may replace some sockets. On the other hand, wpctl sounds like a part CLI
*user* interface.
Frankly speaking, I am totally confused what Haines is trying to achieve and
what is their actual configuration. If the approach "read docs & read logs"
does not work, I would ask pipewire community.
Max, I want to thank you for the helpful reply. My impression was that
if wireplumber and pipewire are installed they just work. But I'm not
sure just what that means. Does it mean that they are installerd, if I
simply play a sound file, the sound comes will automatically come out
of the spakers?
Booting a live image should allow to inspect list of processes and services
in a working state. For pipewire it likely should be GNOME rather than KDE,
unsure concerning XFCE and others.
I'm down loading a live ISO as we speak, but I'm unsure the meaning of
what you suggest. How does GNOME or KDE help me see processes and
their state? I do not have a DE. My instinct is to $ ps ax | grep pipewire
and | grep wireplumber to kill the processes or better to purge and then
reinsall them.
In "full" configuration you can walk through preferences exposed to GUI
configuration dialogs. It should help to figure out if something is
missed in a stripped configuration or with alternative tools.
Besides process list ("ps axuwf" and I recommend to skim through output
before filtering by specific keywords) you may compare systemd units
(services, sockets), D-Bus services, sockets specific to audio stack.
apt list '(~npulseaudio|~npipewire|~nwireplumber)~i'
Listing... Done
libkpipewire5/stable,now 5.27.5-3 amd64 [installed,automatic]
...
Are you runing this command simply to find out what pulseaudio and
wireplumber dragged info your system. What do you do with this
information?
Maybe some packages are redundant (on the other hand, maybe some
important components were missed in the list), but I expect that
applications should be able to play sound when these applications are
installed.
I purged alsa-utils, pipewire and wireplumber. Then installed
pipewire, wireplumber and pipewire-pulse. What do I do next without
messing things up? Are the daemons running? Running $ systemctl | grep
daemon suggests they are not.
The last command is rather strange, I do not expect it may be helpful.
Some services are started with systemd user session on login, some are
activated on demand through systemd socket activation or in response to
D-Bus calls.
Which way you tried to play sound files and what actual issues you
noticed? If you need a mixer, I would try some specific to
pulseaudio/pipewire instead of alsa-mixer (I am unsure if it may cause a
conflict).
