Hello, here are the requested results.
Please note that I also experience this problem with Creative Pebble V3
Bluetooth speakers.
Regards.
systemctl --user status pipewire :
xxx@station:~$ systemctl --user status pipewire
● pipewire.service - PipeWire Multimedia Service
Loaded: loaded (/usr/lib/systemd/user/pipewire.service; enabled; preset:
enabled)
Active: active (running) since Sun 2025-11-09 12:34:01 CET; 4h 49min ago
Invocation: a66de08175964fdfb62ac21611fb223c
TriggeredBy: ● pipewire.socket
Main PID: 1952 (pipewire)
Tasks: 3 (limit: 38148)
Memory: 8.6M (peak: 11.5M)
CPU: 5.725s
CGroup:
/user.slice/user-1000.slice/[email protected]/session.slice/pipewire.service
└─1952 /usr/bin/pipewire
nov 09 12:34:01 station systemd[1928]: Started pipewire.service - PipeWire
Multimedia Service.
systemctl --user status pulseaudio :
xxx@station:~$ systemctl --user status pulseaudio
○ pulseaudio.service - Sound Service
Loaded: loaded (/usr/lib/systemd/user/pulseaudio.service; enabled; preset:
enabled)
Active: inactive (dead)
TriggeredBy: ○ pulseaudio.socket
> Le 27.09.2025 14:16 CEST, Fabio Fantoni <[email protected]> a écrit :
>
>
> On cinnamon packages was switched to have pipewire as default, gnome do
> it before.
>
> Checking my latest Sid installation with cinnamon there are both
> pipewire and pulseaudio installed by default (not good), but pipewire is
> running and pulseaudio not, so should be ok, unless some program checks
> properly and tries to use the inactive one, I have not verified the
> blueman code.
>
> From the test I did some time ago (I don't remember when) it only
> installed pipewire correctly, I suppose something has changed which now
> makes pulseaudio prevail as the first choice of blueman by installing
> that one too.
>
> I don't have bluetooth audio device to do test.
>
> For major of case pipewire and pipewire-pulse are more than fine FWIK,
> cases where pulseaudio is really needed should remove pipewire or at
> least make sure pulseaudio is really working.
>
> @phamiet: start to check what is really active (normaly must be only one):
>
> systemctl --user status pipewire
>
> systemctl --user status pulseaudio
>
> About check what blueman try to use and if try to use the one not active
> I don't know how to check.
>
>
> @Christopher Schramm: now that pipewire seems the default of major of
> cases (if I'm not wrong) probably is good to consider reversing the
> priority in the recommended, what do you think? (I mean
> pulseaudio-module-bluetooth | libspa-0.2-bluetooth ->
> libspa-0.2-bluetooth | pulseaudio-module-bluetooth)
>
>
> I tried a very fast check (not sure if complete) in cinnamon related
> packages:
>
> - cinnamon: libcanberra-pulse (recommends) that have dep. pipewire-pulse
> | pulseaudio
>
> - cinnamon-settings-daemon: recommends pipewire-pulse | pulseaudio
>
> and out of blueman (that is recommend in cinnamon) install pipewire as
> default but also allows the installation of pulseaudio (for users who
> need it) via the alternative.
>
> I don't know if it's just blueman or something else that causes
> pulseaudio to install, have recommends pulseaudio-module-bluetooth
> | libspa-0.2-bluetooth, pulseaudio-module-bluetooth have dep. pulseaudio
>
> I saw that gnome-core have dep. pipewire-audio with no alternative so
> force to pipewire and I'm not sure is good the same also in cinnamon
> that can still support also pulseaudio and few users want to use pulseaudio.
>
> From a fast look gnome don't have dep. or recommends that can install
> pulseaudio unlike cinnamon which at least has blueman.
>
> As a possible workaround in cinnamon I can think of adding as recommend
> libspa-0.2-bluetooth | pulseaudio-module-bluetooth but don't seems optimal.
