Thank you for the report, Bill.

Sound is having a tempestuous time, with several bugs about it; and uncertainty about how to package it.

OTOH after the latest Meta update, sound is working here. One known possible problem is that the wrong out device is defaulted. Please check in PulseAudio Volume Control, that Configuration shows the correct choice; and that the correct Output Device is shown [I have to reset this at each boot].

I am just running a big Cauldron update which includes several sound packages. Let's see what happens after that. I shall logout & restart X to be sure.

(In reply to Lewis Smith from comment #1)

> Sound is having a tempestuous time, with several bugs about it; and
> uncertainty about how to package it.

Thanks Lewis. I see Beta1 was just released.
Taking your info I'm gonna shut this bug down and start all over with my test installs. I'll regenerate this again if appropriate.

My golden install source is netinstall.

I'm gonna need a few days to reset myself here.
Hopefully I'll be back up by QA meeting on Thursday.

Beta1 just got released.
I'm gonna reset everything here.
Back in a few days.

Status: NEW => RESOLVED
Resolution: (none) => FIXED

Thanks for closing this, but...
After my comment 2, and the big update referred to, sound is now completely up the spout.
 $ rpm -qa | grep -E 'pulseaudio|pipewire|wireplumber' | sort
kpipewire-5.26.3-1.mga9
lib64alsa-plugins-pulseaudio-1.2.7.1-2.mga9
lib64kf5pulseaudioqt_2-1.2-3.mga8
lib64kf5pulseaudioqt_3-1.3-2.mga9
lib64kpipewire5-5.26.3-1.mga9
lib64kpipewirerecord5-5.26.3-1.mga9
lib64pipewire0.3_0-0.3.61-4.mga9
lib64pulseaudio0-16.1-7.mga9
lib64wireplumber0-0.4.12-2.mga9
pipewire-0.3.61-4.mga9
pulseaudio-16.1-7.mga9
pulseaudio-client-config-16.1-7.mga9
pulseaudio-module-bluetooth-16.1-7.mga9
pulseaudio-module-gsettings-16.1-7.mga9
pulseaudio-module-x11-16.1-7.mga9
pulseaudio-utils-16.1-7.mga9
task-pulseaudio-2018.0-3.mga9
wireplumber-0.4.12-2.mga9
xfce4-pulseaudio-plugin-0.4.5-1.mga9

I tried different soundtracks (that did not matter) with different audio applications. Some did not get going at all, stuck. Others seemed to play - progress bar - but no sound. The only one that *did* audibly play anything was Xine.

CC: (none) => lewyssmith

I've been trough similar issues and the thing it helped me was this comment:
https://bugs.mageia.org/show_bug.cgi?id=31087#c23

Basically swap "wireplumber" with "pipewire-media-session" or vice-versa.
Regards.

CC: (none) => arusanu

Sorry this found its way into M8 Beta1

:-(((

Reopening

Resolution: FIXED => (none)
Status: RESOLVED => REOPENED

Apparently beta1 is worse than alpha1. It seems messed up again. ;-)

I don't understand why we played with pipewire-alsa deps...; pipewire-alsa doesn't need to be installed to get either pipewire or pulseaudio working.

The minimal fix for wireplumber was this: https://svnweb.mageia.org/packages/cauldron/pipewire/current/SPECS/pipewire.spec?r1=1918081&r2=1918214

with that wireplumber won't crash anymore (but that's another bug).

But I don't understand why we explicitily added:

Conflicts:      pipewire-alsa < 0.3.61-3

Anyway, what's happens now it's that on upgrades everything tries to automatically migrate pulseaudio to pipewire. It won't work in that way. Pipewire is a user process started from systemd, and not globally, and you can't enable with global packages. Basically you end up with two sound daemon both running that are conflicting each other. Furthermore pulseaudio is not even started by systemd, but by xdg. Also other distro had several problems in this subject (manjaro, debian, etc.).

What we can do is install pipewire on a newer installation if we want it, but maintain pulseaudio on a older (from mga8) without forcing "enabling" pipewire (it can be installed but there is no need to enable it) together with PA.

CC: (none) => ghibomgx

*** Bug 31236 has been marked as a duplicate of this bug. ***

CC: (none) => brtians1

Assigning to tv as this is what Dave did for the duplicate bug; but do re-assign it if you wish, Thierry. Giuseppe & Jani have contributed to other sound bugs about wireplummer & pipewire[-media-session].

Summary: Cauldron seems to have lost all sound after meta-task update today => Cauldron sound is in a mess
Assignee: bugsquad => thierry.vignaud

solution: 
urpmi alsa-plugins-pulse-config # Sound now working for me on mageia9-beta1

CC: (none) => paul.blackburn

It's clear that pulseaudio and pipewire can not be running at the same time.

While task-pipewire has some conflicts ...
# urpmi task-pipewire
Some requested packages cannot be installed:
alsa-plugins-pulse-config-1.2.7.1-2.mga9.noarch (due to conflicts with pipewire-alsa-0.3.62-1.mga9.x86_64, due to conflicts with pipewire-alsa-0.3.62-1.mga9.x86_64, trying to promote alsa-plugins-pulseaudio, alsa-plugins-pulseaudio)
libalsa-plugins-pulseaudio-1.2.7.1-2.mga9.i586 (due to unsatisfied alsa-plugins-pulse-config, trying to promote alsa-plugins-pulseaudio)

pipewire itself only conflicts with pipewire-alsa, which I find strange given
that both rpm packages come from the same srpm.

pulseaudio is highly integrated into Mageia, including in draksound.

# urpmq --whatrequires pipewire|sort -u
gnome-remote-desktop
pipewire
pipewire-doc
pipewire-utils
task-pipewire
xdg-desktop-portal

As pipewire is new, then to get things going I propose removing the requires
for pipewire from gnome-remote-desktop and from xdg-desktop-portal so that
it will not get installed by default.

People who want to use pipewire will have to remove pulseaudio (all of it's
packages) using "rpm -e --nodeps", and then install task-pipewire.

In Mageia 10, pipewire can replace pulseaudio once it fully replaces the
integration of pulseaudio in the other pacakges such as draksound.

Until then pipewire has to be considered experimental.

CC: (none) => davidwhodgins

This bug is one of the ones that has now stopped qa testing of Mageia 9 beta1

Severity: normal => critical
Priority: Normal => release_blocker

Adding Neal to the cc list as the one who added the requires for pipewire
to xdg-desktop-portal, which I think is why it's getting installed by default

https://svnweb.mageia.org/packages/cauldron/xdg-desktop-portal/current/SPECS/xdg-desktop-portal.spec?r1=1400063&r2=1400067

Neal, please remove the pipewire requires from xdg-desktop-portal.

CC: (none) => ngompa13

(In reply to Dave Hodgins from comment #13)
> This bug is one of the ones that has now stopped qa testing of Mageia 9 beta1

Thank you Dave.

This morning I have put some considerable time into trying to get sound to work on M9. No success.

I went with the newest netinstall:
Mageia-Cauldron-netinstall-nonfree-x86_64.iso
12/8/22

blank 128GB SSD drive on an Intel laptop

and pointed that at my local repo that was updated this morning from mirrors.kernel.org.

clean install with a basic Plasma system but no sound :-(((

VLC Media player
mp3 & mp4 files

*** Bug 31243 has been marked as a duplicate of this bug. ***

CC: (none) => lovaren

Created attachment 13575 [details]
Patch to stop pipewire.socket if current sound profiles is pulse

Attached is a patch to fix the sound problem.
It adds a line to the Unit section of pulseaudio.socket to stop the socket
from triggering the starting of pipewire if pulseaudio is being used.
The line added is ...
ConditionPathExists=!/etc/sound/profiles/current/pulse

@Dave, why not just have pipewire.socket disabled by default. That can be done by removing it from /usr/lib/systemd/user-preset/90-default-user.preset, part of the mageia-release-common package.

It looks like someone has imported the presets from Fedora without considering whether they are suitable for Mageia.

CC: (none) => mageia

Created attachment 13576 [details]
Patch to disable pipewire and wireplumber in user preset

Attached is a tested patch to disable preset for pipewire and wireplumber.

Attachment 13575 is obsolete: 0 => 1

Changing assignment accordingly

Source RPM: (none) => systemd-252.3-1.mga9.src.rpm
Assignee: thierry.vignaud => tmb

wrong package...

Source RPM: systemd-252.3-1.mga9.src.rpm => mageia-release

Ah. Sorry. Looks like the enabling of pipewire by default was done in
https://svnweb.mageia.org/packages/cauldron/mageia-release/current/SOURCES/90-default-user.preset?r1=1700225&r2=1742463
Reassigning.

Assignee: tmb => ngompa13

Correcting myself.
https://svnweb.mageia.org/packages/cauldron/mageia-release/current/SOURCES/90-default-user.preset?revision=1700225&view=markup

Assignee: ngompa13 => jani.valimaa

Created attachment 13577 [details]
rpm -q --last

David, earlier today, I managed to correct my system so plasmashell and sound all work (still some other minor bug issues; but mostly working) -- just in time for a long video conference. Only by removing/adding packages; no reboot.  HTH

CC: (none) => pfortin

(In reply to Pierre Fortin from comment #24)
> I managed to correct my system so plasmashell and sound all work
> Only by removing/adding packages; no reboot
Glad the crisis is over.
Are you able to say exactly what pkgs you removed|added?

Keywords: (none) => FOR_ERRATA9

Changing assignment to all packagers since mageia-release does not have an
assigned maintainer.

Any packager, please rebuild mageia-release with the patch from comment 19
to fix cauldron sound.

Assignee: jani.valimaa => pkg-bugs

(In reply to Dave Hodgins from comment #26)
> Changing assignment to all packagers since mageia-release does not have an
> assigned maintainer.
> 
> Any packager, please rebuild mageia-release with the patch from comment 19
> to fix cauldron sound.

Aren't there two files to fix? Beyond 90-default-user.preset there is also file 90-default.preset (see https://svnweb.mageia.org/packages/cauldron/mageia-release/current/SOURCES/90-default.preset?revision=1884582&view=markup) which contains at bottom:

enable pipewire.socket
enable pipewire-pulseaudio.socket

I think we should revert that too, to situation previous to this fix: https://svnweb.mageia.org/packages/cauldron/mageia-release/current/SOURCES/90-default.preset?r1=1720090&r2=1790625

(In reply to Lewis Smith from comment #25)
> (In reply to Pierre Fortin from comment #24)
> > I managed to correct my system so plasmashell and sound all work
> > Only by removing/adding packages; no reboot
> Glad the crisis is over.
> Are you able to say exactly what pkgs you removed|added?

Removed: https://bugs.mageia.org/show_bug.cgi?id=31275#c19
Added: https://bugs.mageia.org/attachment.cgi?id=13577 (Dec 15 entries; some were extraneous to the issue, or just normal updates)

(In reply to Giuseppe Ghibò from comment #27)
> (In reply to Dave Hodgins from comment #26)
> > Changing assignment to all packagers since mageia-release does not have an
> > assigned maintainer.
> > 
> > Any packager, please rebuild mageia-release with the patch from comment 19
> > to fix cauldron sound.
> 
> Aren't there two files to fix? Beyond 90-default-user.preset there is also
> file 90-default.preset (see
> https://svnweb.mageia.org/packages/cauldron/mageia-release/current/SOURCES/
> 90-default.preset?revision=1884582&view=markup) which contains at bottom:
> 
> enable pipewire.socket
> enable pipewire-pulseaudio.socket
> 
> I think we should revert that too, to situation previous to this fix:
> https://svnweb.mageia.org/packages/cauldron/mageia-release/current/SOURCES/
> 90-default.preset?r1=1720090&r2=1790625

I expect that change will have to be backed out too. Please include a comment
referencing this bug that pulseaudio service and socket must not be enabled
by default until it has been tested and confirmed to work without interfering
with pulseaudio.

Otherwise we'll have to delay Mageia 9 until pulse is completely removed.

IMHO there is no need to wipeout completely PA even in mga10. We need just to append the support in draksound, to either choose one audio system or the other with a button. Actually we have in draksound:

[X] Enable PulseAudio
[X] Use glitch-free mode
[    Troubleshooting     ]

We would need to have something like:

[X] Enable PulseAudio
[ ] Enable Pipewire
[    Troubleshooting     ]

with the Pipewire and Pulseaudio button mutually exclusive. By clicking on [X] Pipewire button it would configure the pipewire by setting the right deps and configs in a more robust way-

Added fix in mageia-release-9-0.28.mga9.

When I tested using the patch from comment 19, it was working. With the changes
since then, including from comment 31, something is still causing it to start,
and still breaking sound.

Trying a netinstall right now to see if it's some leftover problem.

Looks like now wireplumber has to be disabled too.

After a netinstall
[dave@x9v ~]$ systemctl --user status pipewire.service pipewire.socket wireplumber.service |grep Loaded
     Loaded: loaded (/usr/lib/systemd/user/pipewire.service; disabled; preset: disabled)
     Loaded: loaded (/usr/lib/systemd/user/pipewire.socket; enabled; preset: enabled)
     Loaded: loaded (/usr/lib/systemd/user/wireplumber.service; enabled; preset: enabled)

Showing the status too
[dave@x9v ~]$ systemctl --user status pipewire.service pipewire.socket wireplumber.service |grep -e Loaded -e Active
     Loaded: loaded (/usr/lib/systemd/user/pipewire.service; disabled; preset: disabled)
     Active: active (running) since Sat 2022-12-17 15:07:59 EST; 13min ago
     Loaded: loaded (/usr/lib/systemd/user/pipewire.socket; enabled; preset: enabled)
     Active: active (running) since Sat 2022-12-17 15:07:54 EST; 13min ago
     Loaded: loaded (/usr/lib/systemd/user/wireplumber.service; enabled; preset: enabled)
     Active: active (running) since Sat 2022-12-17 15:07:59 EST; 13min ago

And sound is not working.

The presets are still showing as enabled. Did the mirror you installed from have the new version of mageia-release-common?

Ah. Sorry, still had mageia-release-common-9-0.27.mga9.
With mageia-release-common-9-0.28.mga9 now installed
[dave@x9v ~]$ systemctl --user status pipewire.service pipewire.socket wireplumber.service |grep -e Loaded -e Active
     Loaded: loaded (/usr/lib/systemd/user/pipewire.service; disabled; preset: disabled)
     Active: active (running) since Sat 2022-12-17 15:43:40 EST; 1min 4s ago
     Loaded: loaded (/usr/lib/systemd/user/pipewire.socket; enabled; preset: disabled)
     Active: active (running) since Sat 2022-12-17 15:43:37 EST; 1min 7s ago
     Loaded: loaded (/usr/lib/systemd/user/wireplumber.service; enabled; preset: disabled)
     Active: active (running) since Sat 2022-12-17 15:43:40 EST; 1min 4s ago

I don't see what's causing it to be enabled. I do not have a
.config/systemd/user/ directory, so no user level overrides in place.

Adding tv to the cc list. Currently pipewire and pulseaudio can not be
running at the same time. We are trying to stop pipewire from starting so
that Mageia 9 can be released some time this decade.

CC: (none) => thierry.vignaud

Presets are only applied when you install the package providing the service, not when you update it or update the presets. That's intentional, to avoid overriding user choices.

Ah. Thanks. After removing pipewire and wireplumber, then reinstalling them and
rebooting, sound is working although vb guests still have the problem from the
latest kernel where the volume has to be maxed out.

So workaround for others. As root
# rpm -e --nodeps pipewire wireplumber
# urpmi pipewire wireplumber
# systemctl reboot

Status: REOPENED => RESOLVED
Resolution: (none) => FIXED

Yaaayyyy!!!!

New Vbox client install using latest: Mageia-Cauldron-netinstall-nonfree-x86_64.iso
Repo is my local copy of mageia on mirrors.kernel.org ( updated just hours ago )
Clean install, no wrinkles
Basic apps install fine, NFS & http
mp3 file put in Music plays using VLC no problems
mp4 file put in Videos plays using VLC no problems
YouTube videos play just fine.

To complete the stuff and do a good job, we should add the "pipewire" button for enabling to draksound. The current code is here:

https://gitweb.mageia.org/software/drakx/tree/perl-install/harddrake/sound.pm#n110

While it can't be immediate, I think we should open a new bug report where to monitor the progress in this subject.

Before doing that, we need to ensure pulseaudio can be fully disabled and
actually does stop when enabling pipewire.

(In reply to Dave Hodgins from comment #40)
> Ah. Thanks. After removing pipewire and wireplumber, then reinstalling them
> and
> rebooting, sound is working although vb guests still have the problem from
> the
> latest kernel where the volume has to be maxed out.
> 
> So workaround for others. As root
> # rpm -e --nodeps pipewire wireplumber
> # urpmi pipewire wireplumber
> # systemctl reboot

I did these commands, rebooted and I still can't get Firefox to play Youtube videos if I don't switch between the sound profiles.

(In reply to Kristoffer Grundström from comment #44)
> (In reply to Dave Hodgins from comment #40)
> > Ah. Thanks. After removing pipewire and wireplumber, then reinstalling them
> > and
> > rebooting, sound is working although vb guests still have the problem from
> > the
> > latest kernel where the volume has to be maxed out.
> > 
> > So workaround for others. As root
> > # rpm -e --nodeps pipewire wireplumber
> > # urpmi pipewire wireplumber
> > # systemctl reboot
> 
> I did these commands, rebooted and I still can't get Firefox to play Youtube
> videos if I don't switch between the sound profiles.

This works for me on Plasma.  However, I think the key is that the "rpm -e" has to actually remove these packages (i. e. they have to be installed already) so that the "urpmi" goes through installing them again, per comment#39 .

CC: (none) => ftg

(In reply to Kristoffer Grundström from comment #44)
> (In reply to Dave Hodgins from comment #40)
> > Ah. Thanks. After removing pipewire and wireplumber, then reinstalling them
> > and
> > rebooting, sound is working although vb guests still have the problem from
> > the
> > latest kernel where the volume has to be maxed out.
> > 
> > So workaround for others. As root
> > # rpm -e --nodeps pipewire wireplumber
> > # urpmi pipewire wireplumber
> > # systemctl reboot
> 
> I did these commands, rebooted and I still can't get Firefox to play Youtube
> videos if I don't switch between the sound profiles.

The need to switch sound profiles is a long standing bug that only affects
some hardware. This bug is about pipewire being enabled causing pulseaudio
to stop working.

If there is nothing about this to be noted in errata, please remove FOR_ERRATA9.

If somenting more could be solved maybe issue a new bug.

If there is a general problem not suitable for a bug, maybe a wiki page.

CC: (none) => fri

At the moment, I question whether it is really resolved. Not for me since that update which messed up not just sound, but video. I applied Dave's fix comment 40; it did not resolve anything. But Bill's comment 41 is good evidence that it *is* fixed.
I have had for some time a hopeless situation where all multi-media does not work properly, generally not at all; which I have previously noted in related bug 31087, bug 30997; which also have a lot of comment like this one.

I have re-experimented with comparison to Mageia 8 (where everything works), noting here just the non-pulseaudio differences because that is the same in both; and that lib64kf5pulseaudioqt_ has advanced from 2 to 3:
M8
$ rpm -qa | grep -E 'pulseaudio|wireplummer|pipewire' | sort
lib64pipewire0.3_0-0.3.19-1.mga8		=

M9
$ rpm -qa | grep -E 'pulseaudio|wireplummer|pipewire' | sort
kpipewire-5.26.4-1.mga9                         + (yet to try removing)
lib64kpipewire5-5.26.4-1.mga9			+ removed nodeps
lib64kpipewirerecord5-5.26.4-1.mga9		+ removed nodeps
lib64pipewire0.3_0-0.3.63-2.mga9.tainted	=
pipewire-0.3.63-2.mga9.tainted			+ (yet to try removing)

My earlier comment 
https://bugs.mageia.org/show_bug.cgi?id=30997#c44
 lib64pipewire0.3_0-0.3.59-2.mga9         ******
said that in earlier Cauldron days when things worked, this is the only pkg of the group that was present. Again, I have to try reducing to just that.
This may be a private problem, so again removing M9 errata.

See Also: (none) => https://bugs.mageia.org/show_bug.cgi?id=30997, https://bugs.mageia.org/show_bug.cgi?id=31087

Removing other pkgs one at a time down to just lib64pipewire0.3_0 changed nothing here. Except I noticed I misspelt wireplumber (so it never showed, & was never removed)! What a waste of time.. Give up, will juggle in silence.

At last spelling things correctly, following comment 40 (and having deleted everything but what was left):
 $ rpm -qa | grep -E 'wireplumber|pipewire' | sort
 lib64pipewire0.3_0-0.3.63-2.mga9.tainted
 lib64wireplumber0-0.4.13-1.mga9
 pipewire-0.3.63-2.mga9.tainted
 wireplumber-0.4.13-1.mga9
*everything* suddenly works! Hats off to Dave.

Keywords: FOR_ERRATA9 => (none)

Clean net installs should be ok now.

The problem was introduced around 2 weeks ago with a change to pipewire such
that it can no longer be enabled as a user level systemd service by default
without breaking sound due to hardware conflicts with pulseaudio. The fix was
to ensure it is no longer enabled.

For existing cauldron testers with the problem, after updating to
mageia-release-common-9-0.28.mga9, the pipewire package must be uninstalled
using "rpm -e --nodeps pipewire", and then reinstalled, for the preset
changes from mageia-release-common to take effect.

To confirm the pipewire fix is working check ...
$ systemctl --user status pipewire.service pipewire.socket
○ pipewire.service - PipeWire Multimedia Service
     Loaded: loaded (/usr/lib/systemd/user/pipewire.service; disabled; preset: disabled)
     Active: inactive (dead)
TriggeredBy: ○ pipewire.socket

○ pipewire.socket - PipeWire Multimedia System Socket
     Loaded: loaded (/usr/lib/systemd/user/pipewire.socket; disabled; preset: disabled)
     Active: inactive (dead)
   Triggers: ● pipewire.service
     Listen: /run/user/1000/pipewire-0 (Stream)

The Active: line must show dead for both the socket and the service.
Any other sound/video problems are not related to this bug and should be
reported in new bug reports. Changing the subject of this bug accordingly

Summary: Cauldron sound is in a mess => pipewire stops sound from working due to hardware conflicts with pulseaudio

Confirm the systemctl output shown above.

(In reply to Dave Hodgins from comment #51)

> Clean net installs should be ok now.

What I am doing here now is almost daily I am doing netinstalls
to a Vbox Client using the latest either:

Mageia-Cauldron-netinstall-nonfree-i586.iso
or
Mageia-Cauldron-netinstall-nonfree-x86_64.iso

I've rsync'd my local repo to: distrib-coffee.ipsl.jussieu.fr
and do the rsync, twice, just before I do the net install.
That process ensures a stable, unmoving, repo.

For i586 I use Xfce, for x86_64 I use Plasma.

Since the fix was put in, I think a few days ago, my netinstalls have been
successful and both versions have had sound (mp3) and video sound (mp4) using VLC.
Also Firefox plays YouTube videos, with sound.

My new Intel NUC is blazeingly fast. Start netinstall to working desktop
takes less then 10-minutes. :-))

If forgot about wireplumber
$ systemctl --user status wireplumber.service
○ wireplumber.service - Multimedia Service Session Manager
     Loaded: loaded (/usr/lib/systemd/user/wireplumber.service; disabled; preset: disabled)
     Active: inactive (dead)

It too must be dead.

For the wrong device being chosen when there are both hdmi and sound card
outputs, see bug 30997. As mentioned on that bug, for Mageia 8, I have to
select the headphones on the soundcard for the speakers on the external
amplifier to work.

Confirm the 'systemctl --user status wireplumber.service' cmd O/P.

CC: lewyssmith => (none)

So does this mean that Mageia 9 will be released with an obsolete pulseaudio, after all sound package testing over the last 8 months o so has been done using pipewire?

Surely a non working pipewire should be a release blocker.

pulseeffects is no longer maintained other than for security bugs, having been replaced by easyeffects for pipewire.

FWIW my regularly updated cauldron is still using pipewire without problems:

[baz@localhost ~]$ pactl info
Server String: /run/user/1000/pulse/native
Library Protocol Version: 35
Server Protocol Version: 35
Is Local: yes
Client Index: 69
Tile Size: 65472
User Name: baz
Host Name: localhost
Server Name: PulseAudio (on PipeWire 0.3.63)        <<<<<<<<<<<<<<<<<<<<<<<<
Server Version: 15.0.0
Default Sample Specification: float32le 2ch 48000Hz
Default Channel Map: front-left,front-right
Default Sink: alsa_output.pci-0000_00_1b.0.analog-stereo
Default Source: alsa_input.pci-0000_00_1b.0.analog-stereo
Cookie: ae25:f587

CC: (none) => zen25000

Barry, what do you get for
$ systemctl --user status pipewire.service pipewire.socket wireplumber.service

Also, note that prior to the change in early Dec. to enable the user level
presets for pipewire, that it was pulseaudio, not pipewire, that was
handling audio.

All the fix did was put pipewire enabling back to the state it was for the
Mageia 9 alpha iso images.

There's a lot more work to do before pipewire can entirely replace pulseaudio
in Mageia, due to integration with other packages.

In order to get Mageia 9 released reasonably soon, such a major change will
be put off until Mageia 10.

The pipewire package will still be available for users to try, but will not
be running by default as it requires pulseaudio to be fully disabled (services
and sockets masked at system/user level).

(In reply to Dave Hodgins from comment #57)
> Barry, what do you get for
> $ systemctl --user status pipewire.service pipewire.socket
> wireplumber.service

[baz@localhost ~]$ systemctl --user status pipewire.service pipewire.socket wireplumber.service
● pipewire.service - PipeWire Multimedia Service
     Loaded: loaded (/usr/lib/systemd/user/pipewire.service; enabled; preset: disabled)
     Active: active (running) since Thu 2022-12-22 13:29:14 GMT; 1min 56s ago
TriggeredBy: ● pipewire.socket
   Main PID: 33833 (pipewire)
      Tasks: 2 (limit: 9395)
     Memory: 4.4M
        CPU: 40ms
     CGroup: /user.slice/user-1000.slice/user@1000.service/session.slice/pipewire.service
             └─33833 /usr/bin/pipewire

Dec 22 13:29:14 localhost systemd[33822]: Started pipewire.service.
Dec 22 13:29:14 localhost pipewire[33833]: mod.rt: Can't find xdg-portal: (null)
Dec 22 13:29:14 localhost pipewire[33833]: mod.rt: found session bus but no portal
Dec 22 13:29:15 localhost pipewire[33833]: mod.rt: RTKit error: org.freedesktop.DBus.Error.AccessDenied
Dec 22 13:29:15 localhost pipewire[33833]: mod.rt: could not set nice-level to -11: Permission denied
Dec 22 13:29:15 localhost pipewire[33833]: mod.rt: RTKit error: org.freedesktop.DBus.Error.AccessDenied
Dec 22 13:29:15 localhost pipewire[33833]: mod.rt: could not make thread 33889 realtime using RTKit: Permission denied

● pipewire.socket - PipeWire Multimedia System Socket
     Loaded: loaded (/usr/lib/systemd/user/pipewire.socket; enabled; preset: disabled)
     Active: active (running) since Thu 2022-12-22 13:29:14 GMT; 1min 57s ago
      Until: Thu 2022-12-22 13:29:14 GMT; 1min 57s ago
   Triggers: ● pipewire.service
     Listen: /run/user/1000/pipewire-0 (Stream)
     CGroup: /user.slice/user-1000.slice/user@1000.service/app.slice/pipewire.socket

Dec 22 13:29:14 localhost systemd[33822]: Listening on pipewire.socket.

● wireplumber.service - Multimedia Service Session Manager
[baz@localhost ~]$ systemctl --user status pipewire.service pipewire.socket wireplumber.service
● pipewire.service - PipeWire Multimedia Service
     Loaded: loaded (/usr/lib/systemd/user/pipewire.service; enabled; preset: disabled)
     Active: active (running) since Thu 2022-12-22 13:29:14 GMT; 4min 28s ago
TriggeredBy: ● pipewire.socket
   Main PID: 33833 (pipewire)
      Tasks: 2 (limit: 9395)
     Memory: 4.4M
        CPU: 40ms
     CGroup: /user.slice/user-1000.slice/user@1000.service/session.slice/pipewire.service
             └─33833 /usr/bin/pipewire

Dec 22 13:29:14 localhost systemd[33822]: Started pipewire.service.
Dec 22 13:29:14 localhost pipewire[33833]: mod.rt: Can't find xdg-portal: (null)
Dec 22 13:29:14 localhost pipewire[33833]: mod.rt: found session bus but no portal
Dec 22 13:29:15 localhost pipewire[33833]: mod.rt: RTKit error: org.freedesktop.DBus.Error.AccessDenied
Dec 22 13:29:15 localhost pipewire[33833]: mod.rt: could not set nice-level to -11: Permission denied
Dec 22 13:29:15 localhost pipewire[33833]: mod.rt: RTKit error: org.freedesktop.DBus.Error.AccessDenied
Dec 22 13:29:15 localhost pipewire[33833]: mod.rt: could not make thread 33889 realtime using RTKit: Permission denied

● pipewire.socket - PipeWire Multimedia System Socket
     Loaded: loaded (/usr/lib/systemd/user/pipewire.socket; enabled; preset: disabled)
     Active: active (running) since Thu 2022-12-22 13:29:14 GMT; 4min 28s ago
      Until: Thu 2022-12-22 13:29:14 GMT; 4min 28s ago
   Triggers: ● pipewire.service
     Listen: /run/user/1000/pipewire-0 (Stream)
     CGroup: /user.slice/user-1000.slice/user@1000.service/app.slice/pipewire.socket

Dec 22 13:29:14 localhost systemd[33822]: Listening on pipewire.socket.

● wireplumber.service - Multimedia Service Session Manager
     Loaded: loaded (/usr/lib/systemd/user/wireplumber.service; enabled; preset: disabled)
     Active: active (running) since Thu 2022-12-22 13:29:14 GMT; 4min 28s ago
   Main PID: 33834 (wireplumber)
      Tasks: 7 (limit: 9395)
     Memory: 13.6M
        CPU: 200ms
     CGroup: /user.slice/user-1000.slice/user@1000.service/session.slice/wireplumber.service
             └─33834 /usr/bin/wireplumber

Dec 22 13:29:14 localhost systemd[33822]: Started wireplumber.service.
Dec 22 13:29:14 localhost wireplumber[33834]: Can't find xdg-portal: (null)
Dec 22 13:29:14 localhost wireplumber[33834]: found session bus but no portal
Dec 22 13:29:15 localhost wireplumber[33834]: RTKit error: org.freedesktop.DBus.Error.AccessDenied
Dec 22 13:29:15 localhost wireplumber[33834]: could not set nice-level to -11: Permission denied
Dec 22 13:29:15 localhost wireplumber[33834]: RTKit error: org.freedesktop.DBus.Error.AccessDenied
Dec 22 13:29:15 localhost wireplumber[33834]: could not make thread 33888 realtime using RTKit: Permission denied
Dec 22 13:29:17 localhost wireplumber[33834]: [0:05:06.917861317] [33834]  WARN IPAManager ipa_manager.cpp:154 No IPA found in '/usr/>
Dec 22 13:29:17 localhost wireplumber[33834]: [0:05:06.917931730] [33834]  INFO Camera camera_manager.cpp:299 libcamera v0.0.2
Dec 22 13:29:17 localhost wireplumber[33834]: GetManagedObjects() failed: org.freedesktop.DBus.Error.NameHasNoOwner

[baz@localhost ~]$ rpm -qa|grep -E '(pulse|pipew|plumb)'|sort
alsa-plugins-pulse-config-1.2.7.1-2.mga9
gstreamer1.0-pulse-1.20.4-1.mga9
kpipewire-5.26.4-1.mga9
lib64alsa-plugins-pulseaudio-1.2.7.1-2.mga9
lib64kpipewire5-5.26.4-1.mga9
lib64kpipewirerecord5-5.26.4-1.mga9
lib64pipewire0.3_0-0.3.63-2.mga9.tainted
lib64pulseaudio0-16.1-8.mga9
lib64pulsecommon16.1-16.1-8.mga9
lib64pulseglib20-16.1-8.mga9
lib64wireplumber0-0.4.13-1.mga9
pipewire-0.3.63-2.mga9.tainted
pipewire-pulseaudio-0.3.63-2.mga9.tainted
pipewire-utils-0.3.63-2.mga9.tainted
pulseaudio-client-config-16.1-8.mga9
pulseaudio-utils-16.1-8.mga9
pulseeffects-4.8.7-1.mga9
task-pipewire-2018.0-2.mga9
vlc-plugin-pulse-3.0.18-1.mga9.tainted
wireplumber-0.4.13-1.mga9
xfce4-pulseaudio-plugin-0.4.5-1.mga9

Note that this system does not have the pulseaudio package installed nor task-pulseaudio. It does have pipewire-pulseaudio installed and task-pipewire.

If I recall correctly I switched to pipewire originally by simply installing pipewire-pulseaudio.

Trying to do the same in a current cauldron has so far failed.

The Dbus and rtkit errors logged above are also the subject of unresolved ubuntu bugs that I have seen.

However other fedora and ubuntu have new releases using pipewire.

(In reply to Dave Hodgins from comment #58)
> Also, note that prior to the change in early Dec. to enable the user level
> presets for pipewire, that it was pulseaudio, not pipewire, that was
> handling audio.

I installed task-pipewire in April and have been using it since Thierry got it working shortly after.

> 
> All the fix did was put pipewire enabling back to the state it was for the
> Mageia 9 alpha iso images.

I have not had time to try any images.

> 
> There's a lot more work to do before pipewire can entirely replace pulseaudio
> in Mageia, due to integration with other packages.
> 

I have not had any sound issues in cauldron at all until I tried a net-install. All my packages that involve sound are tested and working just fine with the above setup.

> In order to get Mageia 9 released reasonably soon, such a major change will
> be put off until Mageia 10.

I really thought that the 'major change' was completed back in April. :(

> 
> The pipewire package will still be available for users to try, but will not
> be running by default as it requires pulseaudio to be fully disabled
> (services and sockets masked at system/user level).

I think the pipewire-pulseaudio package has/had the necessary conflicts/requires to deal with those at install time.
 
However this mess is so confusing that I really don't understand enough to do more than state what is and has been working just fine for me all these months.

The problem was that mageia-release-common was changed to enable both
pulseaudio and pipewire user level deamons and or sockets.

pulseaudio can not be removed without using --nodeps. If that is done, it
breaks draksound, and possibly other packages.

As per comment 58, prior to mageia-release-common being fixed the only workaround
was user level masking of the pipewire services, in order to allow pulseaudio
to work, or removal using rpm -e --nodeps of the pipewire and wireplumber packages.

I didn't try using pipewire only. Do to pulseaudio being required on a default
install and being integrated into draksound, I don't consider pipewire ready
to replace pulseaudio, so haven't tested using pipewire only.

The mageia-release-common change stopped sound from working in the beta live
iso images, hence testing of those stopped until it was fixed. Given the
high volume of ongoing development, such as kde plasma, the choice was made
to keep the testing paused. I expect production and testing of the beta iso
images to resume mid next week, after Christmas.

(In reply to Dave Hodgins from comment #62)
> The problem was that mageia-release-common was changed to enable both
> pulseaudio and pipewire user level deamons and or sockets.

Pipewire still uses some pulseaudio libs but the daemon is not used so the main 
'pulseaudio' rpm is not needed.

> pulseaudio can not be removed without using --nodeps. If that is done, it
> breaks draksound, and possibly other packages.

Isn't that a draksound bug?

> 
> As per comment 58, prior to mageia-release-common being fixed the only
> workaround
> was user level masking of the pipewire services, in order to allow pulseaudio
> to work, or removal using rpm -e --nodeps of the pipewire and wireplumber
> packages.

We don't need pulseaudio to work.

> 
> I didn't try using pipewire only. Do to pulseaudio being required on a
> default
> install and being integrated into draksound, I don't consider pipewire ready
> to replace pulseaudio, so haven't tested using pipewire only.

This sounds like an installer and draksound issue, not whether pipewire is ready. Every report I read from other distros seem more than happy with it.

> 
> The mageia-release-common change stopped sound from working in the beta live
> iso images, hence testing of those stopped until it was fixed.

Fixing it by reverting to pulseaudio and breaking a working pipewire seems the wrong approach,
however I can see the logic if we don't have the resources to sort this - looks like it's going to be another grub legacy scenario where everyone else moved to grub2 years before Mageia did.

Anyway, have a great Christmas!

(In reply to Barry Jackson from comment #63)
> This sounds like an installer and draksound issue, not whether pipewire is
> ready. Every report I read from other distros seem more than happy with it.

That's because other distros have people willing to do the work needed to make the change.

Sadly we have nobody actively maintaining and improving the Mageia tools. At best we fix critical bugs.

I don't run cauldron and have no experience with pipewire, so I wasn't prepared to take the job on. Nobody else stepped up.

> > The mageia-release-common change stopped sound from working in the beta live
> > iso images, hence testing of those stopped until it was fixed.
> 
> Fixing it by reverting to pulseaudio and breaking a working pipewire seems
> the wrong approach,

But it wasn't working for new installs (and probably not for upgrades either).

> however I can see the logic if we don't have the resources to sort this -
> looks like it's going to be another grub legacy scenario where everyone else
> moved to grub2 years before Mageia did.

Which is a good example. IIRC, we made the switch to GRUB2 during the beta release stage of Mageia 5, and that caused a lengthy delay and many iterations of the ISOs. Dave's solution is the safe one if we want to release Mageia 9 quickly.

Thanks to all for great work on this difficult problem.

Reopened

This has become a serious problem and IMO a release blocker for M9

Best way for me to demonstrate this issue

M9, Plasma, x86_64
Intel, NUC11, RNUC11PAHi50001, 16GB DRAM, 4TB HD

Booting to a working desktop works every time.
Sound ok

Open a Vbox Client of any type, close client
From that moment on there is no sound on either the Host M9 install or any Vbox client

A warm reboot fixes the problem for the host and Vbox client(s)

Status: RESOLVED => REOPENED
Resolution: FIXED => (none)

Not seeing this in my latest Cauldron host install, but I have far different hardware.

Host: HP Pavilion 15, AMD A8-4555M APU, 16GB RAM, AMD HD 7600 graphics, AMD FCH Azalia audio controller, using the snd_hda_intel driver. Tiny speakers on this laptop have never had much volume unless system is set to "raise maximum volume." Cauldron-64 Plasma guest, created by an upgrade of mga8-64 using the beta1 Round 6 CI on a usb stick. Host is set up to use the distrib-coffee mirror to get updates.

Guests tested include a new mga9-64 Plasma created from the same iso as the host, and a mga8-64 Plasma guest created when this was a mga8 system. No problems with sound on either, allowing for the limitations of the speakers.

CC: (none) => andrewsfarm

Does installing "alsa-firmware" change something?

CC: (none) => linux

(In reply to Thomas Andrews from comment #67)
> Not seeing this in my latest Cauldron host install, but I have far different
> hardware.

This is the 3rd day in a row where everything here M9 has booted to a working desktop with sound. And that includes both real hardware and Vbox clients.

One more day and I'd say this is probably behind us.

In my Mageia 9/cauldron up-to-date system, running in QEMU/KVM VM, if I enable pipewire and disable pulseaudio sound does not work. Sound only works if pipewire is disable and pulseaudio is enabled.

You need to properly enable pipewire using the utils attached from bug #31507.

I think this is resolved. Default for upgrade is keepen in pulseaudio, and switching config to pipewire is achievable in current draksound utils.

Yes it seems calm

Status: REOPENED => RESOLVED
Resolution: (none) => FIXED