Hello, In the Message; Subject : Re: root cannot play sound ??? Message-ID : <20220207133656.GV4604@wahoo.no-ip.org> Date & Time: Mon, 7 Feb 2022 08:36:56 -0500 [PS] == Patrick Shanahan has written: PS> * Patrick Shanahan [02-07-22 05:53]: PS> > PS> > root no longer has access to sound devices, wft ???? PS> play FAIL formats: can't open output file `default': can not open audio PS> device: Connection refused If the sound server is pulseaudio, this is a normal result. If you install the pipewire packages onto the pulseaudio system, you can get ssounds at the root. Reagrds, and Good Night. --- ┏━━┓彡 Masaru Nomiya mail-to: nomiya @ galaxy.dti.ne.jp ┃＼／彡 ┗━━┛ "In a mobile phone metadata dataset of more than 40k people, it correctly identifies 52% of individuals based on their 2-hop interaction graph. We further show that the profiles learned by our method are stable over time and that 24% of people are still identifiable after 20 weeks. " -- 「Interaction data are identifiable even across long periods of time」 --

Hello, In the Message; Subject : Re: root cannot play sound ??? Message-ID : <20220207155709.GZ4604@wahoo.no-ip.org> Date & Time: Mon, 7 Feb 2022 10:57:09 -0500 [PS] == Patrick Shanahan has written: PS> * Masaru Nomiya [02-07-22 09:26]: PS> > Hello, PS> > MN> > In the Message; MN> > Subject : Re: root cannot play sound ??? MN> > Message-ID : <20220207133656.GV4604@wahoo.no-ip.org> MN> > Date & Time: Mon, 7 Feb 2022 08:36:56 -0500 [...] MN> > If you install the pipewire packages onto the pulseaudio system, you MN> > can get ssounds at the root. PS> tks but: PS> ~ # rpm -qa *pipewire* *pulseaudio* PS> pipewire-modules-0_3-0.3.45-1.1.x86_64 PS> gstreamer-plugin-pipewire-0.3.45-1.1.x86_64 PS> pipewire-spa-tools-0.3.45-1.1.x86_64 PS> pipewire-alsa-0.3.45-1.1.x86_64 PS> pipewire-libjack-0_3-0.3.45-1.1.x86_64 PS> pulseaudio-utils-15.0-9.1.x86_64 PS> pipewire-0.3.45-1.1.x86_64 PS> pipewire-tools-0.3.45-1.1.x86_64 PS> pipewire-spa-plugins-0_2-0.3.45-1.1.x86_64 PS> pipewire-pulseaudio-0.3.45-1.1.x86_64 PS> pulseaudio-bash-completion-15.0-9.1.x86_64 PS> pipewire-aptx-0.3.45-1.1.x86_64 PS> pulseaudio-setup-15.0-9.1.x86_64 PS> libpipewire-0_3-0-0.3.45-1.1.x86_64 PS> tumbleweed was updated from pulseaudio to pipewire always using dup. and PS> I have 4 tumbleweed system exhibiting the same problem. There are 2 reasons; 1. missing 1 package pipewire-media-session 2. host isn't running Please do, 1. $ systemctl --user daemon-reload 2. $ systemctl --user start pipewire.service pipewire-pulseaudio.service pipewire-media-session.service then, check if the volume is not zero by alsamixer. Regards, --- ┏━━┓彡 Masaru Nomiya mail-to: nomiya @ galaxy.dti.ne.jp ┃＼／彡 ┗━━┛ "Tim Cook, the C.E.O. of Apple, said earlier this year that he would not let his nephew join social networks. Bill Gates banned cellphone until his children were teenagers, and Melinda Gates wrote that she wished they had waited even longer. Steve Jobs would not let his young children near iPads." -- The New York Times --

* Masaru Nomiya [02-07-22 21:05]:

Hello,

In the Message;

Subject : Re: root cannot play sound ??? Message-ID : <87sfsu898g.wl-nomiya@galaxy.dti.ne.jp> Date & Time: Tue, 08 Feb 2022 09:58:39 +0900

[MN] == Masaru Nomiya has written:

MN> Hello,

MN> In the Message;

MN> Subject : Re: root cannot play sound ??? MN> Message-ID : <20220207155709.GZ4604@wahoo.no-ip.org> MN> Date & Time: Mon, 7 Feb 2022 10:57:09 -0500

MN> [PS] == Patrick Shanahan has written:

PS> * Masaru Nomiya [02-07-22 09:26]: PS> > Hello, PS> > MN> > In the Message;

MN> > Subject : Re: root cannot play sound ??? MN> > Message-ID : <20220207133656.GV4604@wahoo.no-ip.org> MN> > Date & Time: Mon, 7 Feb 2022 08:36:56 -0500 MN> [...] MN> > If you install the pipewire packages onto the pulseaudio system, you MN> > can get ssounds at the root.

PS> tks but: PS> ~ # rpm -qa *pipewire* *pulseaudio* PS> pipewire-modules-0_3-0.3.45-1.1.x86_64 PS> gstreamer-plugin-pipewire-0.3.45-1.1.x86_64 PS> pipewire-spa-tools-0.3.45-1.1.x86_64 PS> pipewire-alsa-0.3.45-1.1.x86_64 PS> pipewire-libjack-0_3-0.3.45-1.1.x86_64 PS> pulseaudio-utils-15.0-9.1.x86_64 PS> pipewire-0.3.45-1.1.x86_64 PS> pipewire-tools-0.3.45-1.1.x86_64 PS> pipewire-spa-plugins-0_2-0.3.45-1.1.x86_64 PS> pipewire-pulseaudio-0.3.45-1.1.x86_64 PS> pulseaudio-bash-completion-15.0-9.1.x86_64 PS> pipewire-aptx-0.3.45-1.1.x86_64 PS> pulseaudio-setup-15.0-9.1.x86_64 PS> libpipewire-0_3-0-0.3.45-1.1.x86_64

PS> tumbleweed was updated from pulseaudio to pipewire always using dup. and PS> I have 4 tumbleweed system exhibiting the same problem.

MN> There are 2 reasons;

MN> 1. missing 1 package

MN> pipewire-media-session

MN> 2. host isn't running

MN> Please do,

MN> 1. $ systemctl --user daemon-reload MN> 2. $ systemctl --user start pipewire.service pipewire-pulseaudio.service pipewire-media-session.service

MN> then, check if the volume is not zero by alsamixer.

You may have installed wireplumber instead of pipewire-media-session;

wireplumber-audio-0.4.5-lp153.8.1.x86_64 wireplumber-devel-0.4.5-lp153.8.1.x86_64 wireplumber-0.4.5-lp153.8.1.x86_64

In that case, please change

$ systemctl --user start pipewire.service pipewire-pulseaudio.service pipewire-media-session.service

to

$ systemctl --user start pipewire.service pipewire-pulseaudio.service wireplumber.service

there is no pipewire-media.service for Tumbleweed and: USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND paka 4468 0.5 0.0 117008 18004 ? Shttp://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet oftc What sort of day was it? A day like all days, filled with those events that alter and illuminate our times...

* Masaru Nomiya [02-07-22 22:45]:

Hello,

In the Message;

Subject : Re: root cannot play sound ??? Message-ID : <20220208032051.GH4604@wahoo.no-ip.org> Date & Time: Mon, 7 Feb 2022 22:20:51 -0500

[PS] == Patrick Shanahan has written:

[...] PS> > MN> 2. host isn't running PS> > PS> > MN> Please do, PS> > PS> > MN> 1. $ systemctl --user daemon-reload PS> > MN> 2. $ systemctl --user start pipewire.service pipewire-pulseaudio.service pipewire-media-session.service PS> > PS> > MN> then, check if the volume is not zero by alsamixer. PS> > PS> > You may have installed wireplumber instead of pipewire-media-session; PS> > PS> > wireplumber-audio-0.4.5-lp153.8.1.x86_64 PS> > wireplumber-devel-0.4.5-lp153.8.1.x86_64 PS> > wireplumber-0.4.5-lp153.8.1.x86_64 PS> > PS> > In that case, please change PS> > PS> > $ systemctl --user start pipewire.service pipewire-pulseaudio.service pipewire-media-session.service PS> > PS> > to PS> > PS> > $ systemctl --user start pipewire.service pipewire-pulseaudio.service wireplumber.service PS> >

PS> there is no pipewire-media.service for Tumbleweed and: PS> USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND PS> paka 4468 0.5 0.0 117008 18004 ? S paka 4470 1.5 0.1 68244 52160 ? S root 25078 0.0 0.0 42280 10784 ? S paka 4469 0.0 0.0 330884 16944 ? Ssl Feb04 0:18 \_ /usr/bin/wireplumber PS> root 25079 0.0 0.0 329644 18136 ? Ssl Feb06 0:08 \_ /usr/bin/wireplumber

If you have either wireplumber or pipewire-media-session, you're good to go.

Then,

$ systemctl --user daemon-reload

$ systemctl --user start pipewire.service pipewire-pulseaudio.service wireplumber.service

and, check if the volume is not zero by alsamixer.

11:04 crash:~ > systemctl --user daemon-reload 11:04 crash:~ > systemctl --user start pipewire.service pipewire-pulseaudio.service wireplumber.service Failed to start pipewire-pulseaudio.service: Unit pipewire-pulseaudio.service not found. 11:05 crash:~ > rpm -qa pipewire-pulseaudio pipewire-pulseaudio-0.3.45-1.1.x86_64 11:05 crash:~ > rpm -ql pipewire-pulseaudio /usr/bin/pipewire-pulse /usr/lib/systemd/user/pipewire-pulse.service /usr/lib/systemd/user/pipewire-pulse.socket /usr/share/man/man1/pipewire-pulse.1.gz /usr/share/pipewire/pipewire-pulse.conf /var/lib/pipewire/pipewire-pulseaudio_post_workaround 11:05 crash:~ > rpm -qv pipewire-pulseaudio pipewire-pulseaudio-0.3.45-1.1.x86_64 11:05 crash:~ > l /var/lib/pipewire/pipewire-pulseaudio_post_workaround ls: cannot access '/var/lib/pipewire/pipewire-pulseaudio_post_workaround': No such file or directory -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet oftc What sort of day was it? A day like all days, filled with those events that alter and illuminate our times...

* Masaru Nomiya [02-08-22 18:54]:

Hello,

In the Message;

Subject : Re: root cannot play sound ??? Message-ID : <20220208160724.GL4604@wahoo.no-ip.org> Date & Time: Tue, 8 Feb 2022 11:07:24 -0500

[PS] == Patrick Shanahan has written:

[...] PS> > If you have either wireplumber or pipewire-media-session, you're good to go. PS> > PS> > Then, PS> > PS> > $ systemctl --user daemon-reload PS> > PS> > $ systemctl --user start pipewire.service pipewire-pulseaudio.service wireplumber.service PS> > PS> > and, check if the volume is not zero by alsamixer.

PS> 11:04 crash:~ > systemctl --user daemon-reload PS> 11:04 crash:~ > systemctl --user start pipewire.service pipewire-pulseaudio.service wireplumber.service PS> Failed to start pipewire-pulseaudio.service: Unit pipewire-pulseaudio.service not found. PS> 11:05 crash:~ > rpm -qa pipewire-pulseaudio PS> pipewire-pulseaudio-0.3.45-1.1.x86_64 PS> 11:05 crash:~ > rpm -ql pipewire-pulseaudio PS> /usr/bin/pipewire-pulse PS> /usr/lib/systemd/user/pipewire-pulse.service PS> /usr/lib/systemd/user/pipewire-pulse.socket PS> /usr/share/man/man1/pipewire-pulse.1.gz PS> /usr/share/pipewire/pipewire-pulse.conf PS> /var/lib/pipewire/pipewire-pulseaudio_post_workaround PS> 11:05 crash:~ > rpm -qv pipewire-pulseaudio PS> pipewire-pulseaudio-0.3.45-1.1.x86_64 PS> 11:05 crash:~ > l /var/lib/pipewire/pipewire-pulseaudio_post_workaround PS> ls: cannot access '/var/lib/pipewire/pipewire-pulseaudio_post_workaround': No such file or directory

Have a look;

https://www.reddit.com/r/openSUSE/comments/re5akg/pipewirepulseaudio_broken_...

tks for your help and research I do not use root that much except for admin and in that mind only loose system sounds. I assume that someone else will have the same or similar problems and perhaps find a solution. for the concern it is causing me, I see little to warrant more effort. tks -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet oftc What sort of day was it? A day like all days, filled with those events that alter and illuminate our times...

On 2022-02-09 09:01, Per Jessen wrote:

Patrick Shanahan wrote:

...

I assume that someone else will have the same or similar problems and perhaps find a solution.

Didn't Carlos run into the very same problem, a couple of weeks back? He was looking to play a sound from a script. IIRC, his issue was most easily solved by sudo'ing to a user to play a sound, but maybe that thread explains what was changed (to cause $SUBJ).

Yes, but there is a difference: I was using pulseaudio, and this problem is using pipewire. -- Cheers / Saludos, Carlos E. R. (from 15.3 x86_64 at Telcontar)

Hello, Sorry for typo. In the Message; Subject : Re: root cannot play sound ??? Message-ID : <8735kscvs9.wl-nomiya@galaxy.dti.ne.jp> Date & Time: Wed, 09 Feb 2022 17:02:30 +0900 [MN] == Masaru Nomiya has written: [...] MN> If so, please try this; MN> $ sudo systemctl --user --global unmask pipewire-pulse.socket pipewire-pulse.servic This one. $ sudo systemctl --user --global unmask pipewire-pulse.socket pipewire-pulse.service Regards. --- ┏━━┓彡 Masaru Nomiya mail-to: nomiya @ galaxy.dti.ne.jp ┃＼／彡 ┗━━┛ "Three young men died for Rationalization. Yet, Margaret Bloody Thatcher LIVES!" 'Brassed Off'

* Masaru Nomiya [02-09-22 03:03]:

Hello,

Sorry for late reply.

In the Message;

Subject : Re: root cannot play sound ??? Message-ID : <20220209032444.GM4604@wahoo.no-ip.org> Date & Time: Tue, 8 Feb 2022 22:24:44 -0500

[PS] == Patrick Shanahan has written:

[...] MN> > Have a look;

MN> > https://www.reddit.com/r/openSUSE/comments/re5akg/pipewirepulseaudio_broken_...

PS> tks for your help and research PS> I do not use root that much except for admin and in that mind only loose PS> system sounds.

I think so, too.

This is my sound environment;

$ pactl info

Server String: /run/user/1000/pulse/native Library Protocol Version: 35 Server Protocol Version: 35 Is Local: yes Client Index: 65 Tile Size: 65472 User Name: masaru Host Name: linux-egwc Server Name: PulseAudio (on PipeWire 0.3.45) Server Version: 15.0.0 Default Sample Specification: float32le 2ch 192000Hz Default Channel Map: front-left,front-right Default Sink: alsa_output.usb-D___M_Holdings_Inc._HD-DAC1-00.analog-stereo Default Source: alsa_input.usb-Sony_Corporation_UAB-80-00.mono-fallback Cookie: c81d:1fe6

The pipewire + Maranz HD DAC1 creates a truly stunning soundscape that immerses me in classical music appreciation. In my environment, it can play high-resolution music, but it can also play music ripped from CDs. It's a sound I've never experienced in my nearly 60 years of audio experience, and I listen to it every day, wondering why. It is with this in mind that I am helping you.

Anyway, I'm thinking that the problem you're encountering is due to the fact that piewire-pulseaudio,service is masked.

Please check

$ systemctl list-unit-files .. pipewire-pulseaudio.service masked <-- How about this? ..

there is no existance of pipewire-pulseaudio.service systemctl list-unit-files | grep pulseaudio output is blank from previous: rpm -ql pipewire-pulseaudio /usr/bin/pipewire-pulse /usr/lib/systemd/user/pipewire-pulse.service /usr/lib/systemd/user/pipewire-pulse.socket /usr/share/man/man1/pipewire-pulse.1.gz /usr/share/pipewire/pipewire-pulse.conf /var/lib/pipewire/pipewire-pulseaudio_post_workaround ls -la /var/lib/pipewire/pipewire-pulseaudio_post_workaround ls: cannot access '/var/lib/pipewire/pipewire-pulseaudio_post_workaround': No such file or directory -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet oftc What sort of day was it? A day like all days, filled with those events that alter and illuminate our times...

Hello, Sorry fot too many typo. In the Message; Subject : Re: root cannot play sound ??? Message-ID : <87a6ezelpj.wl-nomiya@galaxy.dti.ne.jp> Date & Time: Thu, 10 Feb 2022 07:09:28 +0900 [MN] == Masaru Nomiya has written: [...] MN> 2 questions; MN> 1. please show the output of; MN> $ pcctl info This one. $ pactl info Regards. --- ┏━━┓彡 野宮 賢 mail-to: nomiya @ galaxy.dti.ne.jp ┃＼／彡 ┗━━┛ 「eメールや携帯電話に縛られた社会は、自分自身と向き合ったり、 空想にふけったりする自由を奪う。」 -- M. Crichton --

* Masaru Nomiya [02-09-22 17:10]:

Hello,

In the Message;

Subject : Re: root cannot play sound ??? Message-ID : <20220209162240.GU4604@wahoo.no-ip.org> Date & Time: Wed, 9 Feb 2022 11:22:40 -0500

[PS] == Patrick Shanahan has written:

MN> > Please check

MN> > $ systemctl list-unit-files PS> > .. PS> > pipewire-pulseaudio.service masked <-- How about this? PS> > ..

PS> there is no existance of pipewire-pulseaudio.service

PS> systemctl list-unit-files | grep pulseaudio PS> output is blank

Sorry for my mistake.

$ systemctl --user list-unit-files

pipewire-pulse.service masked <-- How about this?

In the Message;

Subject : Re: root cannot play sound ??? Message-ID : <20220209162721.GV4604@wahoo.no-ip.org> Date & Time: Wed, 9 Feb 2022 11:27:21 -0500

[PS] == Patrick Shanahan has written:

MN> > $ sudo systemctl --user --global unmask pipewire-pulse.socket pipewire-pulse.service

PS> yields no output, playing sound as root still fails

Maybe, pipewire isn't still running.

but it is

With this,

# pw-play [sound file]

pw-play /usr/share/sounds/Oxygen-Window-All-Desktops.ogg plays sound as root:# pw-play /usr/share/sounds/Oxygen-Window-All-Desktops.ogg error: pw_context_connect() failed: Host is down

you get the message;

error: pw_context_connect() failed: Host is down

don't you?

2 questions;

1. please show the output of;

$ pcctl info

I have no "pcctl" and http://software.openssue.org/search provides no package

2. after this;

$ sudo systemctl --user --global unmask pipewire-pulse.socket pipewire-pulse.service

19:22 crash:~ > sudo systemctl --user --global unmask pipewire-pulse.socket pipewire-pulse.service [sudo] password for root: 19:22 crash:~ >

did you do the following?

$ systemctl --user daemon-reload $ systemctl --user pipewire.service pipewire-pulse.service wireplumber.service

yes

Check for non-zero volume with alsamixser.

yes

If you did, please show the output of;

1. systemctl --user status pipewire.service

19:22 crash:~ > systemctl --user status pipewire.service ● pipewire.service - PipeWire Multimedia Service Loaded: loaded (/usr/lib/systemd/user/pipewire.service; disabled; vendor preset: disabled) Active: active (running) since Tue 2022-02-08 10:49:33 EST; 1 day 8h ago TriggeredBy: ● pipewire.socket Main PID: 2919 (pipewire) Tasks: 2 (limit: 4915) Memory: 13.5M CPU: 3min 9.900s CGroup: /user.slice/user-1000.slice/user@1000.service/session.slice/pipewire.service └─2919 /usr/bin/pipewire Feb 08 10:49:33 crash systemd[2246]: Started PipeWire Multimedia Service.

2. systemctl --user status pipewire-pulse.service

● pipewire-pulse.service - PipeWire PulseAudio Loaded: loaded (/usr/lib/systemd/user/pipewire-pulse.service; disabled; vendor preset: disabled) Active: active (running) since Tue 2022-02-08 10:49:33 EST; 1 day 8h ago TriggeredBy: ● pipewire-pulse.socket Main PID: 2921 (pipewire-pulse) Tasks: 2 (limit: 4915) Memory: 32.7M CPU: 8min 29.921s CGroup: /user.slice/user-1000.slice/user@1000.service/session.slice/pipewire-pulse.service └─2921 /usr/bin/pipewire-pulse Feb 08 10:49:33 crash systemd[2246]: Started PipeWire PulseAudio. Feb 08 10:49:35 crash pipewire-pulse[2921]: mod.protocol-pulse: client 0x55998c8fabd0 [SoX]: ERROR command:-1 (invalid) tag:2 error:25 (Input/output error) Feb 08 12:47:21 crash pipewire-pulse[2921]: mod.protocol-pulse: client 0x55998c9173e0: send channel:4294967295 20, error -32: Broken pipe

3. systemctl --user status wireplumber.service

● wireplumber.service - Multimedia Service Session Manager Loaded: loaded (/usr/lib/systemd/user/wireplumber.service; enabled; vendor preset: enabled) Active: active (running) since Tue 2022-02-08 10:49:33 EST; 1 day 8h ago Main PID: 2920 (wireplumber) Tasks: 4 (limit: 4915) Memory: 9.9M CPU: 2.795s CGroup: /user.slice/user-1000.slice/user@1000.service/session.slice/wireplumber.service └─2920 /usr/bin/wireplumber Feb 08 10:49:33 crash systemd[2246]: Started Multimedia Service Session Manager.

4. message with this operation;

# pw-play [sound file]

# pw-play /usr/share/sounds/Oxygen-Window-All-Desktops.ogg error: pw_context_connect() failed: Host is down -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet oftc What sort of day was it? A day like all days, filled with those events that alter and illuminate our times...

* Masaru Nomiya [02-09-22 21:17]:

Hello,

In the Message;

Subject : Re: root cannot play sound ??? Message-ID : <20220210002907.GI1071@wahoo.no-ip.org> Date & Time: Wed, 9 Feb 2022 19:29:07 -0500

[PS] == Patrick Shanahan has written:

Thanks.

[...] PS> > 2. systemctl --user status pipewire-pulse.service

PS> ● pipewire-pulse.service - PipeWire PulseAudio PS> Loaded: loaded (/usr/lib/systemd/user/pipewire-pulse.service; disabled; vendor preset: disabled) PS> Active: active (running) since Tue 2022-02-08 10:49:33 EST; 1 day 8h ago PS> TriggeredBy: ● pipewire-pulse.socket PS> Main PID: 2921 (pipewire-pulse) PS> Tasks: 2 (limit: 4915) PS> Memory: 32.7M PS> CPU: 8min 29.921s PS> CGroup: /user.slice/user-1000.slice/user@1000.service/session.slice/pipewire-pulse.service PS> └─2921 /usr/bin/pipewire-pulse

PS> Feb 08 10:49:33 crash systemd[2246]: Started PipeWire PulseAudio. PS> Feb 08 10:49:35 crash pipewire-pulse[2921]: mod.protocol-pulse: client 0x55998c8fabd0 [SoX]: ERROR command:-1 (invalid) tag:2 error:25 (Input/output error) PS> Feb 08 12:47:21 crash pipewire-pulse[2921]: mod.protocol-pulse: client 0x55998c9173e0: send channel:4294967295 20, error -32: Broken pipe

That's it!

The pipewire-pulse.service has got conflict with the pulseaudio.service!

Sorry, I missed the file pulseaudio-setupw-15.0-9.1.x86_64.

Please try;

# rpm -e pulseaudio-setup

I did this

this will solve your issue.

Also do this, just in case;

$ systemctl --user mask pulseaudio.service

and I did this

Maybe, this will return the message;

Unit pulseaudio.service does not exist, proceeding anyway. Created symlink /home/masaru/.config/systemd/user/pulseaudio.service -> /dev/null.

and it did

If this is done, you will see that there is no "error 32: Broken pipe" message in the output of "systemctl --user status pipewire-pulse.service"

Then, proceed as follows;

$ systemctl --user restart pipewire.service pipewire-pulse.service wireplumber.service

and this

and make sure with

$ ps aux | grep -i pulse

ps aux | grep -i pulse paka 28803 0.1 0.0 34660 12560 ? S

that PA is dead for good while all that happening.

1. check the volume 2. run for test

# pw-play [sound file]

pw-play will now provide audio for root, but ... /usr/bin/play from sox-14.4.2-7.100.x86_64 will not tks, -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet oftc What sort of day was it? A day like all days, filled with those events that alter and illuminate our times...

Hello, In the Message; Subject : ALMOST SOLVED: root cannot play sound ??? Message-ID : <20220210024155.GK1071@wahoo.no-ip.org> Date & Time: Wed, 9 Feb 2022 21:41:55 -0500 [PS] == Patrick Shanahan has written: Thanks. [...] PS> pw-play will now provide audio for root, but ... PS> /usr/bin/play from sox-14.4.2-7.100.x86_64 PS> will not In the Message; Subject : Re: ALMOST SOLVED: root cannot play sound ??? Message-ID : <20220210024512.GL1071@wahoo.no-ip.org> Date & Time: Wed, 9 Feb 2022 21:45:12 -0500 [PS] == Patrick Shanahan has written: [...] PS> nor will xine play sound as root These arn't pipewire's issue. Please install the libpulse0. HTH. Regards. --- ┏━━┓彡 Masaru Nomiya mail-to: nomiya @ galaxy.dti.ne.jp ┃＼／彡 ┗━━┛ "Three young men died for Rationalization. Yet, Margaret Bloody Thatcher LIVES!" 'Brassed Off'

* Patrick Shanahan [02-09-22 22:40]:

* Masaru Nomiya [02-09-22 22:16]:

...

Hello,

In the Message;

Subject : ALMOST SOLVED: root cannot play sound ??? Message-ID : <20220210024155.GK1071@wahoo.no-ip.org> Date & Time: Wed, 9 Feb 2022 21:41:55 -0500

[PS] == Patrick Shanahan has written:

Thanks.

[...] PS> pw-play will now provide audio for root, but ... PS> /usr/bin/play from sox-14.4.2-7.100.x86_64 PS> will not

maybe was toooo quickkk, play now works as root but I don't know why. I left the keyboard, took a shower came back. maybe play thought I was tooo dirty :) let's consider it solved, tks -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet oftc What sort of day was it? A day like all days, filled with those events that alter and illuminate our times...

* Masaru Nomiya [02-09-22 23:49]:

Hello,

In the Message;

Subject : Re: ALMOST SOLVED: root cannot play sound ??? Message-ID : <20220210033918.GM1071@wahoo.no-ip.org> Date & Time: Wed, 9 Feb 2022 22:39:18 -0500

[PS] == Patrick Shanahan has written:

[...] MN> > Please install the libpulse0.

PS> :(

PS> rpm -q libpulse0 PS> libpulse0-15.0-9.1.x86_64

PS> Install Date: Mon Jan 17 08:49:38 2022

Both play and xine have nothing to do with pipewire.

Don't all pulseaudio related apps show the same behaviour?

Isn't the pulseaudio daemon still running?

ps aux | grep -i pulse paka 21404 0.0 0.0 6660 2384 pts/9 S+ 08:37 0:00 grep --color=auto -i pulse paka 28803 0.0 0.0 34660 16496 ? S

Does the

# pidof pulseaudio

return null?

yes and root again: 08:39 crash: ~ # play /usr/share/sounds/Oxygen-Window-All-Desktops.ogg Floating point exception (core dumped) 08:39 crash: ~ # pw-play /usr/share/sounds/Oxygen-Window-All-Desktops.ogg error: pw_context_connect() failed: Host is down and root could play both ways 10 hours ago. no system changes during that period. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet oftc What sort of day was it? A day like all days, filled with those events that alter and illuminate our times...

* Masaru Nomiya [02-10-22 17:06]:

Hello,

There's something wrong with your PC and/or Tumbleweed, something that doesn't happen in Leap 15.3!!!

it happens on *all* my Tumbleweed systems

In the Message;

Subject : Re: ALMOST SOLVED: root cannot play sound ??? Message-ID : <20220210134229.GO1071@wahoo.no-ip.org> Date & Time: Thu, 10 Feb 2022 08:42:29 -0500

[PS] == Patrick Shanahan has written:

[...] PS> and root again: PS> 08:39 crash: ~ # play /usr/share/sounds/Oxygen-Window-All-Desktops.ogg PS> Floating point exception (core dumped)

PS> 08:39 crash: ~ # pw-play /usr/share/sounds/Oxygen-Window-All-Desktops.ogg PS> error: pw_context_connect() failed: Host is down

PS> and root could play both ways 10 hours ago. no system changes during that PS> period.

This means that the pipewire.service is inactive, at the moment.

But, why ...... (_ _?

Have you done this, yesterday?

$ systemctl --user daemon-reload

Anyway, you can fix it by;

$ systemctl --user start pipewire.service

17:07 crash:~ > systemctl --user status pipewire.service ● pipewire.service - PipeWire Multimedia Service Loaded: loaded (/usr/lib/systemd/user/pipewire.service; disabled; vendor preset: disabled) Active: active (running) since Wed 2022-02-09 21:36:39 EST; 19h ago TriggeredBy: ● pipewire.socket Main PID: 28801 (pipewire) Tasks: 2 (limit: 4915) Memory: 7.6M CPU: 354ms CGroup: /user.slice/user-1000.slice/user@1000.service/session.slice/pipewire.service └─28801 /usr/bin/pipewire Feb 09 21:36:39 crash systemd[2246]: Started PipeWire Multimedia Service. 17:07 crash:~ > systemctl --user start pipewire.service 17:08 crash:~ > systemctl --user status pipewire.service ● pipewire.service - PipeWire Multimedia Service Loaded: loaded (/usr/lib/systemd/user/pipewire.service; disabled; vendor preset: disabled) Active: active (running) since Wed 2022-02-09 21:36:39 EST; 19h ago TriggeredBy: ● pipewire.socket Main PID: 28801 (pipewire) Tasks: 2 (limit: 4915) Memory: 7.6M CPU: 354ms CGroup: /user.slice/user-1000.slice/user@1000.service/session.slice/pipewire.service └─28801 /usr/bin/pipewire Feb 09 21:36:39 crash systemd[2246]: Started PipeWire Multimedia Service. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet oftc What sort of day was it? A day like all days, filled with those events that alter and illuminate our times...

* Masaru Nomiya [02-10-22 17:47]:

Hello,

In the Message;

Subject : Re: ALMOST SOLVED: root cannot play sound ??? Message-ID : <20220210221026.GA1071@wahoo.no-ip.org> Date & Time: Thu, 10 Feb 2022 17:10:26 -0500

[PS] == Patrick Shanahan has written:

PS> * Masaru Nomiya [02-10-22 17:06]: PS> > Hello, PS> > PS> > There's something wrong with your PC and/or Tumbleweed, something that PS> > doesn't happen in Leap 15.3!!!

PS> it happens on *all* my Tumbleweed systems

Are they?

MN> > Have you done this, yesterday?

How about this?

What do you grt by;

$ pidof pipewire

17:53 crash:~ > pidof pipewire 28801 8023

PS> > $ systemctl --user daemon-reload PS> > PS> > Anyway, you can fix it by; PS> > PS> > $ systemctl --user start pipewire.service

PS> 17:07 crash:~ > systemctl --user status pipewire.service [...] PS> └─28801 /usr/bin/pipewire

PS> Feb 09 21:36:39 crash systemd[2246]: Started PipeWire Multimedia Service.

THanks.

How about this?

$ systemctl --user start pipewire-pulse.service

17:53 crash:~ > systemctl --user start pipewire-pulse.service 17:54 crash:~ > systemctl --user status pipewire-pulse.service ● pipewire-pulse.service - PipeWire PulseAudio Loaded: loaded (/usr/lib/systemd/user/pipewire-pulse.service; disabled; vendor preset: disabled) Active: active (running) since Wed 2022-02-09 21:36:39 EST; 20h ago TriggeredBy: ● pipewire-pulse.socket Main PID: 28803 (pipewire-pulse) Tasks: 2 (limit: 4915) Memory: 17.3M CPU: 1.102s CGroup: /user.slice/user-1000.slice/user@1000.service/session.slice/pipewire-pulse.service └─28803 /usr/bin/pipewire-pulse Feb 09 21:36:39 crash systemd[2246]: Started PipeWire PulseAudio. 17:55 crash: ~ # play /usr/share/sounds/Oxygen-Window-All-Desktops.ogg Floating point exception (core dumped) 17:55 crash: ~ # pw-play /usr/share/sounds/Oxygen-Window-All-Desktops.ogg error: pw_context_connect() failed: Host is down -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet oftc What sort of day was it? A day like all days, filled with those events that alter and illuminate our times...

* Masaru Nomiya [02-10-22 18:20]:

Hello,

In the Message;

Subject : Re: ALMOST SOLVED: root cannot play sound ??? Message-ID : <20220210225658.GC1071@wahoo.no-ip.org> Date & Time: Thu, 10 Feb 2022 17:56:58 -0500

[PS] == Patrick Shanahan has written:

Thanks.

[...] PS> 17:53 crash:~ > pidof pipewire PS> 28801 8023

Why 2 processes?

Please show the output of;

$ ps aux | grep pipe

one owned by root

Then, all related pocesses;

$ kill -9 8023 $ kill -9 28801

Afterwards,

then the user version of pipewire and pipewire-pulse automagically restart.

$ systemctl --user daemon-reload

$ systemctl --user pipewire.service pipewire-pulse.service wireplumber.service

I assume you mean "systemctl --user start ... " the same pid's are present for the automagically restarted pipewire and pipewire-pluse instances

And then, please show the output of;

$ ps aux | grep pipe

paka 30774 0.0 0.0 21872 7952 ? Shttp://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet oftc What sort of day was it? A day like all days, filled with those events that alter and illuminate our times...

* Masaru Nomiya [02-10-22 22:28]:

Hello,

In the Message;

Subject : Re: ALMOST SOLVED: root cannot play sound ??? Message-ID : <20220211025011.GE1071@wahoo.no-ip.org> Date & Time: Thu, 10 Feb 2022 21:50:11 -0500

[PS] == Patrick Shanahan has written:

[...] MN> > Please show the output of;

MN> > $ ps aux | grep pipe

PS> one owned by root

It's strange.

In may case,

# pidof pipewire 5323

$ pidof pipewire 5323

Just same.

Please show the result of;

$ ls -al /etc/systemd/usr

22:40 crash:~ > ll -la /etc/systemd/user/ 22:40 crash:~ > ll -la /etc/systemd/user/sockets.target.wants/ total 8 drwxr-xr-x 2 root root 4096 Aug 19 12:42 . drwxr-xr-x 3 root root 4096 Feb 7 09:53 .. lrwxrwxrwx 1 root root 43 Aug 19 12:42 pipewire-pulse.socket -> /usr/lib/systemd/user/pipewire-pulse.socket lrwxrwxrwx 1 root root 37 Jul 26 2020 pipewire.socket -> /usr/lib/systemd/user/pipewire.socket -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet oftc What sort of day was it? A day like all days, filled with those events that alter and illuminate our times...

* Masaru Nomiya [02-10-22 23:17]:

Hello,

In the Message;

Subject : Re: ALMOST SOLVED: root cannot play sound ??? Message-ID : <20220211034247.GF1071@wahoo.no-ip.org> Date & Time: Thu, 10 Feb 2022 22:42:47 -0500

[PS] == Patrick Shanahan has written:

[...] MN> > Please show the result of;

MN> > $ ls -al /etc/systemd/usr

PS> 22:40 crash:~ > ll -la /etc/systemd/user/ PS> 22:40 crash:~ > ll -la /etc/systemd/user/sockets.target.wants/ PS> total 8 PS> drwxr-xr-x 2 root root 4096 Aug 19 12:42 . PS> drwxr-xr-x 3 root root 4096 Feb 7 09:53 .. PS> lrwxrwxrwx 1 root root 43 Aug 19 12:42 pipewire-pulse.socket -> /usr/lib/systemd/user/pipewire-pulse.socket PS> lrwxrwxrwx 1 root root 37 Jul 26 2020 pipewire.socket -> /usr/lib/systemd/user/pipewire.socket

Thanks.

How about this?

$ ps -ef | grep defunct

08:58 crash:~ > ps -ef |grep defunct paka 31591 31558 0 08:58 pts/10 00:00:00 grep --color=auto defunct are we down to looking for straws :) tks, -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet oftc What sort of day was it? A day like all days, filled with those events that alter and illuminate our times...

* Masaru Nomiya [02-11-22 18:30]:

Hello,

In the Message;

Subject : Re: ALMOST SOLVED: root cannot play sound ??? Message-ID : <20220211135914.GJ1071@wahoo.no-ip.org> Date & Time: Fri, 11 Feb 2022 08:59:14 -0500

[PS] == Patrick Shanahan has written:

[...] PS> > How about this? PS> > PS> > $ ps -ef | grep defunct

PS> 08:58 crash:~ > ps -ef |grep defunct PS> paka 31591 31558 0 08:58 pts/10 00:00:00 grep --color=auto defunct

Thanks.

Come to think of it, it doesn't matter if zombie is running ... .

PS> are we down to looking for straws :)

Yes, that's it!

I've reread this;

https://www.reddit.com/r/openSUSE/comments/re5akg/pipewirepulseaudio_broken_...

and I don't see any reports like yours ...

How about a reboot already? The only thing I can say is....

I have done that several times during our exchange but does not seem to help this situation. I will reboot again in the next day or two and advise. tks -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet oftc What sort of day was it? A day like all days, filled with those events that alter and illuminate our times...

* Masaru Nomiya [02-12-22 00:53]:

Hello,

In the Message;

Subject : Re: ALMOST SOLVED: root cannot play sound ??? Message-ID : <20220212033906.GA1071@wahoo.no-ip.org> Date & Time: Fri, 11 Feb 2022 22:39:06 -0500

[PS] == Patrick Shanahan has written:

[...] MN> > How about a reboot already? The only thing I can say is....

PS> I have done that several times during our exchange but does not seem to PS> help this situation. I will reboot again in the next day or two and PS> advise.

That's what I thought...

I compiled pipewire-0.3.45-1.1.src.rpm (<-- Tumbleweed's source file), then installed. As I expected, it works fine.

So, I'm thinking that Tumbleweed may be the problem.

In the Message;

Subject : SOLVED: root cannot play sound ??? Message-ID : <20220210034852.GN1071@wahoo.no-ip.org> Date & Time: Wed, 9 Feb 2022 22:48:52 -0500

[PS] == Patrick Shanahan has written:

[...] PS> maybe was toooo quickkk, play now works as root PS> but I don't know why. I left the keyboard, took a shower came back. PS> maybe play thought I was tooo dirty :)

I just can't figure this out.

And.

In the Message;

Subject : Re: ALMOST SOLVED: root cannot play sound ??? Message-ID : <20220210225658.GC1071@wahoo.no-ip.org> Date & Time: Thu, 10 Feb 2022 17:56:58 -0500

[PS] == Patrick Shanahan has written:

[...] PS> 17:53 crash:~ > pidof pipewire PS> 28801 8023

This seems to be happening more often than not.

yes, when ever root has a sound instance, a pipewire instance is initiated.

pidof pipewire 32068 30775

In this;

https://www.linuxquestions.org/questions/slackware-14/daemon-a-small-and-powerful-daemon-supervisor-with-e-logind-support-for-babysitting-our-pipewire's-user-target-daemons-testing-wanted-4175691414/page3.html

it says,

...

3. pipewire-pulse could be started by daemon --bind rather than by pipewire (as suggested by 0XBF/LuckyCyborg) [...] Option 3 is probably the quickest and easiest approach that should get both the pipewire and pipewire-pulse processes terminated cleanly.

But I don't know the details.

BTW, is everything in /etc/pipewire/pipewire.conf's context.exec commented out?

yes, /usr/share/pipewire/pipewire.conf there is no /etc/pipewire on my tumbleweed systems tks -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet oftc What sort of day was it? A day like all days, filled with those events that alter and illuminate our times...

* Masaru Nomiya [02-12-22 18:44]:

Hello,

In the Message;

Subject : Re: ALMOST SOLVED: root cannot play sound ??? Message-ID : <20220212140815.GG1071@wahoo.no-ip.org> Date & Time: Sat, 12 Feb 2022 09:08:15 -0500

[PS] == Patrick Shanahan has written:

[...] PS>>> 17:53 crash:~ > pidof pipewire PS>>> 28801 8023

MN> > This seems to be happening more often than not.

PS> yes, when ever root has a sound instance, a pipewire instance is PS> initiated.

PS> > pidof pipewire PS> 32068 30775

[...] MN> > BTW, is everything in /etc/pipewire/pipewire.conf's context.exec MN> > commented out?

PS> yes, /usr/share/pipewire/pipewire.conf PS> there is no /etc/pipewire on my tumbleweed systems

If you are not using a sound card with a sampling rate other than 44100Hz, that's fine.

Anyway, I was not convinced, so I installed Tumbleweed (openSUSE-Tumbleweed-DVD-x86_64-Snapshot20220210)on another PC and checked it out.

Immediately after installation,

$ pactl info

returned;

Server String: /run/user/1000/pulse/native Library Protocol Version: 35 Server Protocol Version: 35 Is Local: yes Client Index: 62 Tile Size: 65472 User Name: masaru Host Name: linux-frlp Server Name: PulseAudio Server Version: 15.0.0 Default Sample Specification: float32le 2ch 44100Hz [...]

As you see, puseaudio system is working.

Just fo fun, I tried

# pw-play /usr/share/sounds/Oxygen-Sys-Log-In.ogg

To my surprise, it returned the message;

error: pw_context_connect() failed: Host is down

I thought, user can accept that this is a problem with pipewire.

try a second time and see if you get a different answer. remember that my system fails the first instance but plays after and there is no instance of pipewire (pid) belonging to root until after the failed attempt.

Carlos, a Leap 15.3 user, thinks the same way. In other words, I believe that the installation media he used is the same configuration as the Tumbleweed I used.

Anyway, when I started YaST2 and instructed it to install pipewire-pulseaudio, it showed me other necessary pipewire files and also told me to remove some pulseaudio related files. But since pulseaudio-setup was still there, I added it to the list of files to be removed and let it do its job.

Then. I did;

$ pactl info

returned the same message as above;

Server String: /run/user/1000/pulse/native Library Protocol Version: 35 Server Protocol Version: 35 Is Local: yes Client Index: 62 Tile Size: 65472 User Name: masaru Host Name: linux-frlp Server Name: PulseAudio Server Version: 15.0.0 Default Sample Specification: float32le 2ch 44100Hz [...]

So, I rebooted, and did;

$ pactl info

returens

Server String: /run/user/1000/pulse/native Library Protocol Version: 35 Server Protocol Version: 35 Is Local: yes Client Index: 62 Tile Size: 65472 User Name: masaru Host Name: linux-frlp Server Name: PulseAudio (on PipeWire 0.3.45) Server Version: 15.0.0 Default Sample Specification: float16le 2ch 44100Hz [...]

I couldn't go any further. That is, somehow, I couldn't configure the sound card in YaST2. But ... I think I got a hint.

Patrick, please show the resultss of;

1. $ cat /proc/asound/cards

2. $ aplay -L

18:45 crash:~ > cat /proc/asound/cards 0 [Intel ]: HDA-Intel - HDA Intel HDA Intel at 0xf4000000 irq 46 1 [NVidia ]: HDA-Intel - HDA NVidia HDA NVidia at 0xd2000000 irq 17 18:45 crash:~ > aplay -L null Discard all samples (playback) or generate zero samples (capture) speexrate Rate Converter Plugin Using Speex Resampler pipewire PipeWire Sound Server upmix Plugin for channel upmix (4,6,8) default Default ALSA Output (currently PipeWire Media Server) sysdefault:CARD=Intel HDA Intel, ALC892 Analog Default Audio Device front:CARD=Intel,DEV=0 HDA Intel, ALC892 Analog Front output / input surround21:CARD=Intel,DEV=0 HDA Intel, ALC892 Analog 2.1 Surround output to Front and Subwoofer speakers surround40:CARD=Intel,DEV=0 HDA Intel, ALC892 Analog 4.0 Surround output to Front and Rear speakers surround41:CARD=Intel,DEV=0 HDA Intel, ALC892 Analog 4.1 Surround output to Front, Rear and Subwoofer speakers surround50:CARD=Intel,DEV=0 HDA Intel, ALC892 Analog 5.0 Surround output to Front, Center and Rear speakers surround51:CARD=Intel,DEV=0 HDA Intel, ALC892 Analog 5.1 Surround output to Front, Center, Rear and Subwoofer speakers surround71:CARD=Intel,DEV=0 HDA Intel, ALC892 Analog 7.1 Surround output to Front, Center, Side, Rear and Woofer speakers iec958:CARD=Intel,DEV=0 HDA Intel, ALC892 Digital IEC958 (S/PDIF) Digital Audio Output hdmi:CARD=NVidia,DEV=0 HDA NVidia, HDMI 0 HDMI Audio Output hdmi:CARD=NVidia,DEV=1 HDA NVidia, HDMI 0 HDMI Audio Output hdmi:CARD=NVidia,DEV=2 HDA NVidia, HDMI 0 HDMI Audio Output hdmi:CARD=NVidia,DEV=3 HDA NVidia, HDMI 0 HDMI Audio Output tks, -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet oftc What sort of day was it? A day like all days, filled with those events that alter and illuminate our times...

* Masaru Nomiya [02-12-22 19:48]:

Hello,

In the Message;

Subject : Re: ALMOST SOLVED: root cannot play sound ??? Message-ID : <20220212235404.GT1071@wahoo.no-ip.org> Date & Time: Sat, 12 Feb 2022 18:54:04 -0500

[PS] == Patrick Shanahan has written:

[...] MN> > Patrick, please show the resultss of;

MN> > 1. $ cat /proc/asound/cards MN> > MN> > 2. $ aplay -L

PS> 18:45 crash:~ > cat /proc/asound/cards PS> 0 [Intel ]: HDA-Intel - HDA Intel PS> HDA Intel at 0xf4000000 irq 46 PS> 1 [NVidia ]: HDA-Intel - HDA NVidia PS> HDA NVidia at 0xd2000000 irq 17

I supposed so!!!

These two sound cards are probably the cause of the problem.

Both are trying to use the same module driver, snd_hda_intel, and are battling with each other. This is the reason for the strange behavior on your system.

So we need to specify the priority of the device in alsa.conf, like this;

　options snd-hda-intel index=0,1 vid=[vender0 id],[vender1 id]　

I looked at editing /usr/share/alsa/alsa.conf but the format does not appear to provide a place for "options sn..." how, where and what do I edit? copy of alsa.conf http://wahoo.no-ip.org/~paka/alsa.conf

You can get the vender id;

# lspci -nn | grep Audio

The Vender ID of the card you are using should be written as [vender0 id] and the Vender ID of the other card should be written as [vender1 id].

(Ex.)

# lspci -nn | grep Audio 　00:14.2 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 Azalia (Intel HDA) [1002:4383] (rev 40) 　01:00.1 Audio device [0403]: NVIDIA Corporation GK208 HDMI/DP Audio Controller [10de:0e0f] (rev a1)

In this example, the upper card's vender id is 1002, the lower card's vender id is 10de.

I get: # lspci -nn |grep Audio 00:1b.0 Audio device [0403]: Intel Corporation 82801JI (ICH10 Family) HD Audio Controller [8086:3a3e] 03:00.1 Audio device [0403]: NVIDIA Corporation GF106 High Definition Audio Controller [10de:0be9] (rev a1)

Then, reboot.

wonder why I did not have this problem three months ago tks -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet oftc What sort of day was it? A day like all days, filled with those events that alter and illuminate our times...

Hello, Sorry, I just remembered. In the Message; Subject : Re: ALMOST SOLVED: root cannot play sound ??? Message-ID : <87r187h233.wl-nomiya@galaxy.dti.ne.jp> Date & Time: Sun, 13 Feb 2022 12:34:08 +0900 [MN] == Masaru Nomiya has written: [...] PS> > So we need to specify the priority of the device in alsa.conf, like PS> > this; PS> > PS> > 　options snd-hda-intel index=0,1 vid=[vender0 id],[vender1 id]　 PS> I looked at editing /usr/share/alsa/alsa.conf PS> but the format does not appear to provide a place for "options sn..." PS> how, where and what do I edit? PS> copy of alsa.conf PS> http://wahoo.no-ip.org/~paka/alsa.conf MN> In that case, you can create /etc/asound.conf as shown below. The way to do this in opensuse is to specify it in /etc/modprobe.d/50-sound.conf. If you use the card0, add these line to 50-sound.conf -------------------------------------------------------------------- options snd-hda-intel model=[NAME] enable=1 index=0 # alias snd-card-0 snd-hda-intel -------------------------------------------------------------------- where you can get the model name by; 1. # cat /proc/aound/card0/codec#0 <-- Maybe, you will use the card0 as default; then you get the codec name like this; Codec: FOOBAR ALC883 with this codec name (in this case ALC883), you can get the model name from; /usr/src/linux-[KERNE_VERSION]/Documentation/sound/hd-audio/models.rst You may have problems with /etc/asound.conf. Maybe you have 50-sound.conf saved as 50-sound.conf.YaST2save when it was working fine. Regards. --- ┏━━┓彡 野宮 賢 mail-to: nomiya @ galaxy.dti.ne.jp ┃＼／彡 ┗━━┛ "Bill! You married with Computer. Not with Me!" "No..., with money."

Hello, Sorry for late reply. In the Message; Subject : Re: SOLVED: root cannot play sound ??? Message-ID : <20220213174742.GD1071@wahoo.no-ip.org> Date & Time: Sun, 13 Feb 2022 12:47:42 -0500 [PS] == Patrick Shanahan has written: PS> * Masaru Nomiya [02-13-22 00:08]: [...] MN> > with this codec name (in this case ALC883), you can get the model name MN> > from; MN> > MN> > /usr/src/linux-[KERNE_VERSION]/Documentation/sound/hd-audio/models.rst PS> there is no /usr/src/linux-5.16.50-1/Documentation/sound directory 5.16.50 is a strange version number. There doesn't exist such a source file. Besides, model.rst is an important file... MN> > You may have problems with /etc/asound.conf. MN> > Maybe you have 50-sound.conf saved as 50-sound.conf.YaST2save when it MN> > was working fine. PS> ok, I removed /etc/asound.conf as I alread had PS> /etc/modprobe.d/50-sound.conf (but no 50-sound.conf.YaST2save), installed PS> yast2-sound and configured both cards in yast. and I now have: PS> options snd slots=snd-hda-intel,snd-hda-intel PS> # u1Nb.WMbVFcSAoD3:82801JI (ICH10 Family) HD Audio Controller PS> alias snd-card-0 snd-hda-intel PS> # kEn8.Nn1lwzNp6rB:GF106 High Definition Audio Controller PS> alias snd-card-1 snd-hda-intel I think it is more reliable to set it this way. options snd slots=snd-hda-intel,snd-hda-intel enable=1 index=0 # u1Nb.WMbVFcSAoD3:82801JI (ICH10 Family) HD Audio Controller alias snd-card-0 snd-hda-intel enable=0 index=1 # kEn8.Nn1lwzNp6rB:GF106 High Definition Audio Controller alias snd-card-1 snd-hda-intel PS> previous: PS> options snd slots=snd-hda-intel PS> # u1Nb.WMbVFcSAoD3:82801JI (ICH10 Family) HD Audio Controller PS> alias snd-card-0 snd-hda-intel Were you using a different video card at this time? And, did you have any sound problems then? [...] PS> have access to root sound bites PS> didn't check for root pipewire instance before trying to play sound but PS> now: PS> USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND PS> paka 4218 0.0 0.0 111052 14292 ? S paka 4220 0.0 0.0 29396 11500 ? S root 10728 0.0 0.0 108816 12520 ? S still cannot understand why I had root sound previously and lost it, PS> probably with the change to pipewire from pulseaudio. This is what I wondered. It's usually said that pulseadio can't do it, but pipewire can, but I've been told the opposite. Anyway, how about this? $ rm -rf ~/.config/pulse PS> **and** only one sound card was configured, u1Nb.WMbVFcSAoD3:82801JI Yes, this is also a mystery　..... Regards. --- ┏━━┓彡 Masaru Nomiya mail-to: nomiya @ galaxy.dti.ne.jp ┃＼／彡 ┗━━┛ "Tim Cook, the C.E.O. of Apple, said earlier this year that he would not let his nephew join social networks. Bill Gates banned cellphone until his children were teenagers, and Melinda Gates wrote that she wished they had waited even longer. Steve Jobs would not let his young children near iPads." -- The New York Times --

Hello, In the Message; Subject : Re: SOLVED: root cannot play sound ??? Message-ID : <20220214145142.GW1071@wahoo.no-ip.org> Date & Time: Mon, 14 Feb 2022 09:51:42 -0500 [PS] == Patrick Shanahan has written: [...] MN> > What do you get by doing this? MN> > MN> > $ rpm -q --whatrequires pipewire MN> > rpm -q --whatrequires pipewire PS> pipewire-aptx-0.3.45-1.1.x86_64 PS> pipewire-pulseaudio-0.3.45-1.1.x86_64 PS> plasma5-session-wayland-5.24.0-1.2.x86_64 PS> wireplumber-0.4.8-2.1.x86_64 Mine is like this; $ rpm -q --whatrequires pipewire wireplumber-0.4.8-lp153.27.3.x86_64 pipewire-spa-plugins-0_2-0.3.45-lp153.30.17.x86_64 pipewire-modules-0.3.45-lp153.30.17.x86_64 pipewire-lang-0.3.45-lp153.30.17.noarch You can see that plasam5 is the one that is running the daemon now. You are using KDE4, arn't you. BTW, as you see, your system doesn't include 2 importanrt files; 1. pipewire-spa-plugins 2. pipewire-modules It's hard to imagine, that they haven't dependency with pipewire? The package pipewire-modules plays an important role in recognizing the sound card. One more question; pipewire-aptx-0.3.45-1.1.x86_64 This was replaced by pipewire-spa-plugins a long time ago and should be gone now. Another question; MN> > rpm -q --whatrequires pipewire [...]4 PS> pipewire-pulseaudio-0.3.45-1.1.x86_64 that is, pipewire-pulseaudio doesn't depend on pipewire.... (_ _? Anyway, please install; 1. pipewire-spa-plugins 2. pipewire-modules and remove, pipewire-aptx-0.3.45-1.1.x86_64 [...] PS> did: systemctl --user daemon-reload PS> systemctl --user restart pipewire.service pipewire-pulseaudio.service wireplumber.service PS> there is no pipewire-pulseaudio.service Wouldn't it be like this? $ systemctl --user status pipewire-pulseaudio.service [...] * pipewire-pulseaudio.service Loaded: masked (Reason: Unit pipewire-pulseaudio.service is masked.) For now, reboot and see what happens. Regards. --- ┏━━┓彡 Masaru Nomiya mail-to: nomiya @ galaxy.dti.ne.jp ┃＼／彡 ┗━━┛ "In a mobile phone metadata dataset of more than 40k people, it correctly identifies 52% of individuals based on their 2-hop interaction graph. We further show that the profiles learned by our method are stable over time and that 24% of people are still identifiable after 20 weeks. " -- 「Interaction data are identifiable even across long periods of time」 --

Hello, In the Message; Subject : Re: SOLVED: root cannot play sound ??? Message-ID : <20220215031655.GC1071@wahoo.no-ip.org> Date & Time: Mon, 14 Feb 2022 22:16:55 -0500 [PS] == Patrick Shanahan has written: [...] MN> > BTW, as you see, your system doesn't include 2 importanrt files; MN> > 1. pipewire-spa-plugins MN> > 2. pipewire-modules PS> # zypper se -sx pipewire-spa-plugins pipewire-modules PS> Loading repository data... PS> Reading installed packages... PS> No matching items found. I misunderstood, but I thought you had it installed. In the Message; Subject : Re: root cannot play sound ??? Message-ID : <20220207155709.GZ4604@wahoo.no-ip.org> Date & Time: Mon, 7 Feb 2022 10:57:09 -0500 [PS] == Patrick Shanahan has written: [...] PS> tks but: PS> ~ # rpm -qa *pipewire* *pulseaudio* PS> pipewire-modules-0_3-0.3.45-1.1.x86_64 PS> gstreamer-plugin-pipewire-0.3.45-1.1.x86_64 PS> pipewire-spa-tools-0.3.45-1.1.x86_64 PS> pipewire-alsa-0.3.45-1.1.x86_64 PS> pipewire-libjack-0_3-0.3.45-1.1.x86_64 PS> pulseaudio-utils-15.0-9.1.x86_64 PS> pipewire-0.3.45-1.1.x86_64 PS> pipewire-tools-0.3.45-1.1.x86_64 PS> pipewire-spa-plugins-0_2-0.3.45-1.1.x86_64 PS> pipewire-pulseaudio-0.3.45-1.1.x86_64 PS> pulseaudio-bash-completion-15.0-9.1.x86_64 PS> pipewire-aptx-0.3.45-1.1.x86_64 PS> pulseaudio-setup-15.0-9.1.x86_64 PS> libpipewire-0_3-0-0.3.45-1.1.x86_64 [...] [...] PS> # zypper -v rm pipewire-pulseaudio [...] PS> 6 packages to remove. PS> After the operation, 1.4 MiB will be freed. PS> Continue? [y/n/v/...? shows all options] (y): n I did not tell you to uninstall pipewire-pulseaudio. Rather, I said that it was strange that; 1. pipewire-spa-plugins 2. pipewire-modules didn't demand for pipewire. These are important files. [...] PS> reinstalled pipewire-pulseaudio which brough pulseaudio-setup, but PS> systemctl --user status pipewire-pulseaudio.service PS> Unit pipewire-pulseaudio.service could not be found. PS> systemctl --user restart pipewire.service pipewire-pulseaudio.service wireplumber.service PS> Failed to restart pipewire-pulseaudio.service: Unit pipewire-pulseaudio.service not found. This is because you installed pulseaudio-setup. Recall; In the Message; Subject : ALMOST SOLVED: root cannot play sound ??? Message-ID : <20220210024155.GK1071@wahoo.no-ip.org> Date & Time: Wed, 9 Feb 2022 21:41:55 -0500 [PS] == Patrick Shanahan has written: [...] MN> > Sorry, I missed the file pulseaudio-setupw-15.0-9.1.x86_64. MN> > Please try; MN> > MN> > # rpm -e pulseaudio-setup PS> I did this MN> > this will solve your issue. MN> > Also do this, just in case; MN> > $ systemctl --user mask pulseaudio.service PS> and I did this MN> > Maybe, this will return the message; MN> > Unit pulseaudio.service does not exist, proceeding anyway. MN> > Created symlink /home/masaru/.config/systemd/user/pulseaudio.service -> /dev/null. PS> and it did [...] MN> > Then, proceed as follows; MN> > $ systemctl --user restart pipewire.service pipewire-pulse.service wireplumber.service PS> and this MN> > and make sure with MN> > $ ps aux | grep -i pulse MN> > ps aux | grep -i pulse PS> paka 28803 0.1 0.0 34660 12560 ? S paka 28980 0.0 0.0 6660 2452 pts/65 S+ 21:38 0:00 grep --color=auto -i pulse PS> > that PA is dead for good while all that happening. PS> > PS> > 1. check the volume PS> > 2. run for test PS> > PS> > # pw-play [sound file] PS> pw-play will now provide audio for root, but ... PS> /usr/bin/play from sox-14.4.2-7.100.x86_64 PS> will not The current problem is that 1. pipewire-spa-plugins 2. pipewire-modules do not appear with rpm -q --whatrequires. In my case; $ rpm -q --whatrequires pipewire-modules pipewire-0.3.45-lp153.30.17.x86_64 I wonder ..... (_ _? Regards. --- ┏━━┓彡 Masaru Nomiya mail-to: nomiya @ galaxy.dti.ne.jp ┃＼／彡 ┗━━┛ "Bill! You married with Computer. Not with Me!" "No..., with money."

Hello, Sorry for the very late reply. Since I had time, I checked the pipewire on my Tumbleweed machine, and it works fine. That's all I did; 1. copy of 50-sound.conf to /etc/modprobe.p from usb memory 2. $ systemctl --user daemon-reload 3. $ systemctp --user start pipewire pipewire-pulseaudio wireplumber where; $ cat /etc/modprobe.d/50-sound.conf options snd slots=snd-usb-audio # uniq.unknownkey0:USB Audio alias snd-card-0 snd-usb-audio and, cat /proc/asound/cards0 0 [PCH ]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0xf7210000 irq 28 1 [NVidia ]: HDA-Intel - HDA NVidia HDA NVidia at 0xf7080000 irq 17 2 [HDDAC1 ]: USB-Audio - HD-DAC1 D & M Holdings Inc. HD-DAC1 at usb-0000:00:14.0-9, high speed I didn't make any settings for HDA-Intel, and witout pulseaudio-setup package. In your case, the same phenomenon appears on all four Tumbleweed machines, so I'm thinking it's a driver problem. I'm sorry, but I don't know anything more about it. Regards. --- ┏━━┓彡 Masaru Nomiya mail-to: nomiya @ galaxy.dti.ne.jp ┃＼／彡 ┗━━┛ "Tim Cook, the C.E.O. of Apple, said earlier this year that he would not let his nephew join social networks. Bill Gates banned cellphone until his children were teenagers, and Melinda Gates wrote that she wished they had waited even longer. Steve Jobs would not let his young children near iPads." -- The New York Times --

* Masaru Nomiya [02-23-22 19:38]:

Hello,

In the Message;

Subject : Re: SOLVED: root cannot play sound ??? Message-ID : <878ru217jj.wl-nomiya@galaxy.dti.ne.jp> Date & Time: Wed, 23 Feb 2022 14:22:24 +0900

[MN] == Masaru Nomiya has written:

[...] MN> In your case, the same phenomenon appears on all four Tumbleweed MN> machines, so I'm thinking it's a driver problem.

Patrik, please show the output of;

$ grep “10de” /etc/udev/rules.d/*

the *only* file below /etc/udev/rules.d/ is 70-persistent-net.rules which is empty, zero bytes. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet oftc What sort of day was it? A day like all days, filled with those events that alter and illuminate our times...

* Masaru Nomiya [02-24-22 02:57]:

Hello,

In the Message;

Subject : Re: Once More (Was: Re: SOLVED: root cannot play sound ???) Message-ID : <20220224034155.GB1071@wahoo.no-ip.org> Date & Time: Wed, 23 Feb 2022 22:41:56 -0500

[PS] == Patrick Shanahan has written:

[...] MN> > $ grep “10de” /etc/udev/rules.d/*

PS> the *only* file below /etc/udev/rules.d/ PS> is 70-persistent-net.rules PS> which is empty, zero bytes.

empty?

You didn't set up the Network via YaST2, did you?

no

Anyway, I remembered that my display has built-in speakers, so I hooked up the Tumbleweed machine again and checked it out.

my second display has built in speakers

As I wrote before, the sound environment on it is;

0 [PCH ]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0xf7210000 irq 28 1 [NVidia ]: HDA-Intel - HDA NVidia HDA NVidia at 0xf7080000 irq 17

So, I edited 50-sound.sond as follows;

options snd slots=snd-hda-intel,snd-hda.intel # Intel HD Audio Controller alias snd-card-0 snd-hda-intel enable=1 # NVIDIA High Definition Audio Controller alias snd-card-1 snd-hda-intel enable=0

and put it in /etc/modprobe.d.

Then, I did;

$ systemctl --user daemon-reload $ systemctl --user restart pipewire piewire-pulse wireplumber

After this, I did, as an user;

1. $ pw-play /usr/share/sounds/Oxygen-Sys-Log-In.ogg

2. $ aplay /usr/share/sounds/Oxygen-Sys-Log-In.ogg

and as root;

1. # pw-play /usr/share/sounds/Oxygen-Sys-Log-In.ogg

2. # aplay /usr/share/sounds/Oxygen-Sys-Log-In.ogg

All of these were executed without any problems.

Moreover, I changed 50-sound.conf;

options snd slots=snd-hda-intel # Intel HD Audio Controller alias snd-card-0 snd-hda-intel enable=1

This file also played the sound without any problems.

I was hoping to get some hints, but instead, I got confused.

tks, -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet oftc What sort of day was it? A day like all days, filled with those events that alter and illuminate our times...

Am 07.02.22 um 14:36 schrieb Patrick Shanahan:

* Patrick Shanahan [02-07-22 05:53]:

...

root no longer has access to sound devices, wft ????

play FAIL formats: can't open output file `default': can not open audio device: Connection refused

i could confirm tumbleweed: gst123 xxx.mp3 XDG_RUNTIME_DIR (/run/user/1000) is not owned by us (uid 0), but by uid 1000! (This could e.g. happen if you try to connect to a non-root PulseAudio as a root user, over the native protocol. Don't do that.) gst123 is running, but no sound output simoN -- www.becherer.de