Fedora-33 No Audio out -

[Bob Goodwin]

In a new install of Fedora-33 I have no audio. It appears that PA has no 
input when viewing the pa volume display.

[bobg@Workstation-2 ~]$ aplay /home/bobg/apps/audio/login.wav
ALSA lib pulse.c:242:(pulse_connect) PulseAudio: Unable to connect: 
Connection refused

aplay: main:830: audio open error: Connection refused

For whatever reason the pa volume shows audio set for HDMI and my audio 
is coming from the motherboard speaker j=output. The same connection 
always worked with Fedora-32 and earlier ...

Am I the only one seeing this and what can I do to fix it?

Bob

[Marco Guazzone]

Hi,

On Sun, Nov 29, 2020 at 9:03 PM Bob Goodwin  wrote:
> In a new install of Fedora-33 I have no audio. It appears that PA has no
> input when viewing the pa volume display.
>
> [bobg@Workstation-2 ~]$ aplay /home/bobg/apps/audio/login.wav
> ALSA lib pulse.c:242:(pulse_connect) PulseAudio: Unable to connect:
> Connection refused
>
> aplay: main:830: audio open error: Connection refused
>
> For whatever reason the pa volume shows audio set for HDMI and my audio
> is coming from the motherboard speaker j=output. The same connection
> always worked with Fedora-32 and earlier ...
>
> Am I the only one seeing this and what can I do to fix it?

I am experiencing similar issues in Fedora 33 (I performed a fresh install
as well).

Occasionally, my system has no audio (with pulseaudio that is unable to
connect), and to get it back I have to run these commands:
  $ pulseaudio --kill
  $ pulseaudio --start

I suspect that the problem could be ascribed to the desktop environment
that I am using (i.e., Cinnamon), as every time I tried to use Gnome I
didn't experience that problem.
There were no such problems in Fedora 32.
My audio interface is integrated in my laptop's motherboard.

Best regards,
Marco
> --
> Bob Goodwin - Zuni, Virginia, USA
> FEDORA-32/64bit LINUX XFCE Fastmail POP3
> _______________________________________________
> users mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines:
> httpthatthats://fedoraproject.org/wiki/Mailing_list_guidelines
> https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/[e-mail]

[Bob Goodwin]

On 2020-11-29 16:51, Marco Guazzone wrote:
> Hi,
>
> On Sun, Nov 29, 2020 at 9:03 PM Bob Goodwin <[e-mail] 
> > wrote:
> In a new install of Fedora-33 I have no audio. It appears that PA
> has no
> input when viewing the pa volume display.
>
> [bobg@Workstation-2 ~]$ aplay /home/bobg/apps/audio/login.wav
> ALSA lib pulse.c:242:(pulse_connect) PulseAudio: Unable to connect:
> Connection refused
>
> aplay: main:830: audio open error: Connection refused
>
> For whatever reason the pa volume shows audio set for HDMI and my
> audio
> is coming from the motherboard speaker j=output. The same connection
> always worked with Fedora-32 and earlier ...
>
> Am I the only one seeing this and what can I do to fix it?
>
>
> I am experiencing similar issues in Fedora 33 (I performed a fresh 
> install as well).
>
> Occasionally, my system has no audio (with pulseaudio that is unable 
> to connect), and to get it back I have to run these commands:
>   $ pulseaudio --kill
>   $ pulseaudio --start
>
> I suspect that the problem could be ascribed to the desktop 
> environment that I am using (i.e., Cinnamon), as every time I tried to 
> use Gnome I didn't experience that problem.
> There were no such problems in Fedora 32.
> My audio interface is integrated in my laptop's motherboard.
>
> Best regards,
> Marco

.
That did not fix the sound problem in Fedora-33
However it did work on Fedora-32 which has had no sound for six months 
or so.

Thanks for the help ...     Bob

[stan]

On Sun, 29 Nov 2020 15:02:38 -0500
Bob Goodwin  wrote:
> aplay: main:830: audio open error: Connection refused

Did alsa recognize the sound devices? Check with
aplay -l

I've had this problem with shifting sound devices because of the video
(hdmi) device being recognized before the other audio devices.  This
makes sense, since the video has to be initialized early in the boot
process.  It is a race condition.  Wolfgang's suggestion that you use
pavucontrol to set the default sound device is a good one.  That way,
no matter the order that they are initialized in, pulse will always use
the device you want as the default output device.

You can also change the alsa default device in 
/etc/alsa/alsactl.conf
However, if the order of sound devices changes with every boot, that
will be problematic.

You can put a file in 
/etc/modprobe.d
to specify the order of devices explicitly, but that is more complex.
Basically, put stanzas like the following for each device.
alias snd-card-0 snd-hda-intel id="SB"
options snd-hda-intel index=0
changing the card description to reflect the information from 
aplay -l
and setting a different index number in the range 0-7 for each of them.
The file name doesn't matter as long as it is unique for that
directory, but choose something descriptive so you recognize it.

[Bob Goodwin]

On 2020-11-30 13:35, stan via users wrote:
> On Sun, 29 Nov 2020 15:02:38 -0500
> Bob Goodwin  wrote:
> > aplay: main:830: audio open error: Connection refused
>
> Did alsa recognize the sound devices? Check with
> aplay -l
>
> I've had this problem with shifting sound devices because of the video
> (hdmi) device being recognized before the other audio devices.  This
> makes sense, since the video has to be initialized early in the boot
> process.  It is a race condition.  Wolfgang's suggestion that you use
> pavucontrol to set the default sound device is a good one.  That way,
> no matter the order that they are initialized in, pulse will always use
> the device you want as the default output device.
>
> You can also change the alsa default device in
> /etc/alsa/alsactl.conf
> However, if the order of sound devices changes with every boot, that
> will be problematic.
>
> You can put a file in
> /etc/modprobe.d
> to specify the order of devices explicitly, but that is more complex.
> Basically, put stanzas like the following for each device.
> alias snd-card-0 snd-hda-intel id="SB"
> options snd-hda-intel index=0
> changing the card description to reflect the information from
> aplay -l
> and setting a different index number in the range 0-7 for each of them.
> The file name doesn't matter as long as it is unique for that
> directory, but choose something descriptive so you recognize it.
> ______

'
Well now I am overwhelmed with more information than I can deal with.

I have been comparing the files mentioned for the Fedora-32 system that 
has a working sound system with the Fedora-33 which does not. Other than 
the xfce volume control Configuration that I mentioned earlier I see:

[bobg@Workstation-2 ~]$ pulseaudio --kill
and then:
[bobg@Workstation-2 ~]$ pulseaudio --start
N: [pulseaudio] main.c: User-configured server at 
{fc279515ec6c4fa39007fba37b0f7d6b}unix:/run/user/1000/pulse/native, 
refusing to start/autospawn.

Nothing seems to work ... I will continue the effort, probably start 
fresh tomorrow morning.

Thanks,      Bob

[Samuel Sieb]

On 11/30/20 12:36 PM, Bob Goodwin wrote:
> I have been comparing the files mentioned for the Fedora-32 system that 
> has a working sound system with the Fedora-33 which does not. Other than 
> the xfce volume control Configuration that I mentioned earlier I see:
>
> [bobg@Workstation-2 ~]$ pulseaudio --kill
> and then:
> [bobg@Workstation-2 ~]$ pulseaudio --start
> N: [pulseaudio] main.c: User-configured server at 
> {fc279515ec6c4fa39007fba37b0f7d6b}unix:/run/user/1000/pulse/native, 
> refusing to start/autospawn.

Pulseaudio gets restarted automatically as soon as you kill it, so 
there's no point in trying to start it manually.  From the other email, 
it's clearly running, but for some reason some clients can't talk to it.

What happens if you use "paplay" instead of "aplay"?

What does "lsof /run/user/1000/pulse/native" show?

Run the "PulseAudio Volume Control" ("pavucontrol" from the command 
line).  Under configuration, what profiles do you see?

"Analog Stereo Duplex" would be the expected one for motherboard audio. 
  If you pick that one, does it show the right options in the Output tab?

I have occasionally had trouble getting HDMI audio to work when I have 
been connecting and disconnecting from HDMI.  Running "pulseaudio -k" 
fixes it.  Other than that, no issues at all on any F33 systems.  But 
I'm also using Gnome.