Bug#1020903: pipewire-pulse: Is the conflict with pulseaudio necessary?
Daniel Vacek
Version: 0.3.58-1, 0.3.58-2
Severity: normal
X-Debbugs-Cc: nee...@gmail.com
Hello,
I was wondering, could both services (pulseaudio and pipewire-pulse) still be
co-installed at the same time?
That way it would be easy to stop one and start the other in case of any
issues.
Or it would be possible to have one system user (with pro-audio preference)
using pipewire-pulse by default and other users sticking to pulseaudio due to
additional features.
If the idea is about full migration to the new service, perhaps that should be
achieved using additional package? Any thoughts here?
Have a nice day,
Daniel
-- System Information:
Debian Release: bookworm/sid
APT prefers testing
APT policy: (500, 'testing'), (1, 'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 5.17.0-trunk-rt-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages pipewire-pulse depends on:
ii init-system-helpers 1.65.2
ii pipewire 0.3.57-1
pipewire-pulse recommends no packages.
Versions of packages pipewire-pulse suggests:
ii libspa-0.2-bluetooth 0.3.57-1
ii pulseaudio-utils 16.1+dfsg1-2
-- no debconf information
Dylan Aïssi
Le mer. 28 sept. 2022 à 12:03, Daniel Vacek <nee...@gmail.com> a écrit :
>
> I was wondering, could both services (pulseaudio and pipewire-pulse) still be
> co-installed at the same time?
conflicts can appear, this is why a conflict between both packages have been
added. But, having both packages in conflict seems to create more issues.
In case of conflicts, users can just remove pulseaudio, so I am thinking about
reverting the conflict and instead just recommending users to remove pulseaudio.
Dylan
[1] https://bugs.debian.org/1013276
Dylan Aïssi
From time to time upstream discussions arise concerning closed-source software
(mainly old games) which check if the /usr/bin/pulseaudio binary is available
otherwise they fail to output sound [1].
The solution is to create a symlink /usr/bin/pulseaudio to /usr/bin/true.
We might want to do the same and thus add back the conflict between pulseaudio
and pipewire-pulse.
Best,
Dylan
[1] https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/1514
alain
Followup-For: Bug #1020903
X-Debbugs-Cc: compte.per...@bbox.fr
Hello to all and sorry for the inconvenience.
yes the conflict between pulse audio and pipewire-pulse is still going on.
I just updated my sid.
so pipewire-pulse has been installed.
and on reboot my sound server was broken.
i read a lot of things .
including the need to install pipewire-audio-client-libraries.
I didn't understand this.
indeed, its setting required to copy and configure conf files that do not exist
under debian .
others ask to uninstall pulse audio.
I don't really want to do it.
I prefer, since it is the cause, to uninstall pipewire-pulse.
surprise : uninstalling pipewire-pulse also uninstalls pipewire-alsa .
I created a pipewire-pulse.pref file, it is active but apt doesn't seem to take
it into account during updates.
This makes pipewire-pulse systematically installed and break my sound server if
I don't remove it by hand.
amd64 and i386 .
looking forward to reading you ,
friendly,
alain .
Translated with www.DeepL.com/Translator (free version)
-- System Information:
Debian Release: bookworm/sid
APT policy: (500, 'unstable'), (100, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.0.0-3-amd64 (SMP w/24 CPU threads; PREEMPT)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set
Patrice Duroux
Regarding the pulseaudio / pipewire conflict, may I suggest some points to try
to deal with part of it, mainly the ALSA client side.
1. the root/global configuration.
It should be possible to manage alternative sets for the one or the other, both
regarding the udev rules (if there is a conflict there between pulseaudio and
pipewire) and the ALSA client setting.
For instance, handling a /etc/alsa/conf.d/99-default.conf link to the file
provided by alsa-plugins (which is compatible both with pulseaudio or pipewire-
pulse) or to the one provided by pipewire-alsa (pipewire).
2. the user/session configuration.
Providing a documentation or a small (Debian) script to facilitate user to setup
a configuration in the userland ($HOME) using the ~/.asoundrc if it is possible
regarding libasound to set more or less the equivalent of the 99-X-default.conf
Am I wrong?
Regards,
Patrice
Dylan Aïssi
Es tu le Alain de debian-facile, ici :
https://debian-facile.org/viewtopic.php?pid=388561#p388561
Le sam. 12 nov. 2022 à 10:03, alain <compte.per...@bbox.fr> a écrit :
>
> yes the conflict between pulse audio and pipewire-pulse is still going on.
> I just updated my sid.
> so pipewire-pulse has been installed.
> and on reboot my sound server was broken.
> i read a lot of things .
> including the need to install pipewire-audio-client-libraries.
> I didn't understand this.
> indeed, its setting required to copy and configure conf files that do not exist
> under debian .
> others ask to uninstall pulse audio.
> I don't really want to do it.
> I prefer, since it is the cause, to uninstall pipewire-pulse.
arrêter d'épingler des paquets au hasard? Je veux dire par là que si gnome-core
n'avais pas été épinglé alors il serait à jour et wireplumber serait installé.
Tu n'aurais donc pas de problème de son.
Tu dit que tu ne veux pas de pipewire et rester à pulseaudio, pourquoi ?
Debian Gnome est passé de pulseaudio à pipewire, en forçant le maintien de
pulseaudio, tu te retrouve dans une configuration non supporté donc ce n'est pas
sûr que tu puisse trouver de l'aide pour les conflits engendrés.
Pourrais-tu ouvrir ton propre rapport de bug la prochaine fois au lieu
de commenter
au hasard les bugs déjà ouvert, cela rend la tache plus facile pour résoudre
les différents bugs sans avoir du bruit parasite.
Merci
Dylan
alain
Thank you Dylan.
Indeed, as you have noticed, I have made some mistakes in the maintenance of my
sid.
When I broke my gnome desktop (with a full-upgrade) a few months ago, I
couldn't find a better solution than reinstalling the testing version.
It was blocking some of the updates.
phenomenon that you have highlighted very well.
I corrected it and (finally!) gnome is fully functional and up to date again.
I have nothing against pipewire . I have against the conflict that existed
until now with pulse audio .
I followed your advice, I rectified my big mistake and finally, not only, now
gnome is up to date but also, as you recommend, wireplumber and pipewire-pulse
are installed without worry.
Thanks for your comments and support.
you can close my intervention.
Translated with www.DeepL.com/Translator (free version)
merci Dylan .
en effet , comme tu l'as très bien remarqué , j'ai fait quelques erreurs dans
la maintenance de ma sid .
quand j'ai cassé mon bureau gnome (avec un full-upgrade) il y a quelque mois ,
je n'ai pas trouvé de meilleure solution que de réinstaller la version testing
.
cela bloquait pour partie les mises à jour .
phénomène que tu as très bien mis en évidence .
je l'ai rectifié et (enfin !) gnome est à nouveau pleinement fonctionnel et à
jour .
je n'ai rien contre pipewire . j' en ai par contre contre le conflit qui
existait jusqu'ici avec pulse audio .
j'ai suivi tes conseils , j'ai rectifié ma grosse erreur et enfin , non
seulement , maintenant gnome est à jour mais en plus , comme tu le recommandes
, wireplumber et pipewire-pulse sont installés sans souci .
merci pour tes remarques et ton soutien .
tu peux clore mon intervention .
alain@sid:~$ apt policy gnome-core wireplumber pipewire-pulse
gnome-core:
Installé : 1:42+8
Candidat : 1:42+8
Table de version :
*** 1:42+8 500
100 http://deb.debian.org/debian bookworm/main amd64 Packages
100 http://deb.debian.org/debian testing/main amd64 Packages
500 http://deb.debian.org/debian unstable/main amd64 Packages
100 /var/lib/dpkg/status
wireplumber:
Installé : 0.4.12-1+b1
Candidat : 0.4.12-1+b1
Table de version :
*** 0.4.12-1+b1 500
100 http://deb.debian.org/debian bookworm/main amd64 Packages
100 http://deb.debian.org/debian testing/main amd64 Packages
500 http://deb.debian.org/debian unstable/main amd64 Packages
100 /var/lib/dpkg/status
pipewire-pulse:
Installé : 0.3.60-2
Candidat : (aucun)
Table de version :
*** 0.3.60-2 -1
100 http://deb.debian.org/debian bookworm/main amd64 Packages
100 http://deb.debian.org/debian testing/main amd64 Packages
500 http://deb.debian.org/debian unstable/main amd64 Packages
100 /var/lib/dpkg/status
note : et oui , c'est bien moi sur debian-facile (tu m'as bien trouvé) .
pourquoi ?
-- System Information:
Debian Release: bookworm/sid
APT prefers unstable
APT policy: (500, 'unstable'), (100, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.0.0-4-amd64 (SMP w/24 CPU threads; PREEMPT)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages pipewire-pulse depends on:
ii init-system-helpers 1.65.2
ii pipewire 0.3.60-2
Versions of packages pipewire-pulse recommends:
ii pulseaudio-utils 16.1+dfsg1-2+b1
Versions of packages pipewire-pulse suggests:
ii libspa-0.2-bluetooth 0.3.60-2
-- no debconf information