rc.pulseaudio seems to require that you boot into X, which
I do not.

When I start the system with an executable rc.pulseaudio
there seems to be a daemon running, but it is non-functional.

The only way that pacmd commands can be run, is to
start X, killall pulseaudio, and start pulseaudio from
an Xterm. I may be able to export a DISPLAY within
rc.pulseaudio, but I am now sick and tired of rebooting
the system that allowed me to find the bug.

There is another problem with pulseaudio: there can be
a bug in the config files that you don't see when
rc.pulseaudio is invoked, but you can't tell the problem
is in the config file.

With all this, I still can't find an entry that works
as a default sink. I went into bios to defeat the
sound card on the motherboard to get this far, but
the pacmd list-sinks doesn't tell me what to
enter in the client.conf. With only the NVidia
sound card, pactl info lists the sound as the
NVidia card but I still don't get sound with Chrome,
nor with, say, MPlayer unless I use the -ao option.

root <NoEMail@home.org> wrote:
> rc.pulseaudio seems to require that you boot into X, which
> I do not.

Interesting, I did not know that. Since you are on v15,
there is a script on 15 that replaces pulse with pipewire.
I never used it but maybe that would work better ?

See if you have:
pipewire-enable.sh and pipewire-disable.sh

<snip>

> With all this, I still can't find an entry that works
> as a default sink. I went into bios to defeat the
> sound card on the motherboard to get this far, but
> the pacmd list-sinks doesn't tell me what to
> enter in the client.conf. With only the NVidia
> sound card, pactl info lists the sound as the
> NVidia card but I still don't get sound with Chrome,
> nor with, say, MPlayer unless I use the -ao option.

HTH
John

--
csh(1) - "An elegant shell, for a more... civilized age."
- Paraphrasing Star Wars

John McCue <jmccue@jmclin1.hsd1.ma.comcast.net> wrote:
> root <NoEMail@home.org> wrote:
>> rc.pulseaudio seems to require that you boot into X, which
>> I do not.
>
> Interesting, I did not know that. Since you are on v15,
> there is a script on 15 that replaces pulse with pipewire.
> I never used it but maybe that would work better ?

Sorry, brain fart, I forgot you are on 14.2,
so I really have no ideas on your next step.

FWIW, I moved to 15 current last week and it is
very stable :)

<snip>

--
csh(1) - "An elegant shell, for a more... civilized age."
- Paraphrasing Star Wars

John McCue <jmccue@jmclin1.hsd1.ma.comcast.net> wrote:
> root <NoEMail@home.org> wrote:
>> rc.pulseaudio seems to require that you boot into X, which
>> I do not.
>
> Interesting, I did not know that. Since you are on v15,
> there is a script on 15 that replaces pulse with pipewire.
> I never used it but maybe that would work better ?
>
> See if you have:
> pipewire-enable.sh and pipewire-disable.sh

Thanks for responding. After 15 hours of work yesterday
I found that, for me, pulseaudio is worthless. All that
is required is to have a valid /etc/asound.conf file
and point to it:
export ALSA_CONFIG_PATH=/etc/asound.conf

Importantly, *NONE* of the online documentation for
pulseaudio could be applied to the version included
in 14.2.

As for your followup, all my current problems stemmed
from a slackpkg upgrade of my 14.2 packages. I'm
not ready to jump to current (15?) yet.

Rule of thumb: Never allow an update/upgrade process
to overwrite your current config files.

root wrote on 1/24/22 7:11 PM:

> Rule of thumb: Never allow an update/upgrade process
> to overwrite your current config files.
>

Iusually chose (p)romt and look at (d)iff for each file, before chosing (r)emove or (o)verwrite....

especially for sshd_config and rc.local, before I had set those 2 to chattr +i....
-rasp