Bug 1381248

MAybe this is important:

# alsamixer
ALSA lib pulse.c:243:(pulse_connect) PulseAudio: Unable to connect: Connection refused

cannot open mixer: Connection refused

Thinking again, if i see the cards in lspci, then the kernel does see them. Reassigning it to pulseaudio.

adapted also the bug report title

When you say 'listed', where do you mean? What do you see in e.g. pavucontrol? What desktop are you using? What does 'alsamixer -c0' and 'alsamixer -c1' show?

Created attachment 1207468 [details]
pavucontrol screenshot

I mean lspci output. After installing pavucontrol i was able to figure out the problem. The default output was all set to digital. 'pavucontrol' should be installed by default if this is the only decent interface to audio control. Also, surprisingly, 'alsamixer' can be executed today with the expected output for all cards.
Find attached the pavucontrol screenshot.

After reboot, the output device remained the analogue card, but the port changed from "headphones (unplugged)" (is not unplugged but well...) to "line out (unplugged)". Maybe this is another bug.

This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '25'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 25 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Plugging in as I have a problem that looks very similar or at least related.

It's almost perfectly described under https://askubuntu.com/questions/974389/ubuntu-17-10-upgrade-built-in-audio-lost so it seems an issue of PulseAudio across the board.

What is described there, I have it since upgrade to F27: pactl shows all sinks of my built-in card to be non available so that PulseAudio and/or KDE doesn't use it by default and I have to switch back to it each time.

pactl shows all built-in profiles and ports as non available, whereas all ports/profiles of my webcam (no other sound device in this PC) are marked available.

Is perhaps the `module-switch-on-port-available` the culprit? Or:

Module #7
        Name: module-alsa-card
        Argument: device_id="0" name="pci-0000_00_1f.3" card_name="alsa_card.pci-0000_00_1f.3" namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no deferred_volume=yes use_ucm=yes card_properties="module-udev-detect.discovered=1"
        Usage counter: 0
        Properties:
                module.author = "Lennart Poettering"
                module.description = "ALSA Card"
                module.version = "11.1-rebootstrapped"

$ lspci -nn | grep -i audio
00:1f.3 Audio device [0403]: Intel Corporation Sunrise Point-H HD Audio [8086:a170] (rev 31)

I notice that all reports are related to Intel audio (knowing that it's probably in 95% of all PCs, perhaps not remarkable).

Let me know if I can provide any other input to help fix this issue, I have to switch the sound each time after a reboot, this is painful.

I have the impression that #1381248 and #1514979 are duplicates (I reported to both the same issue at different times without realizing it until right now, sorry).

This message is a reminder that Fedora 27 is nearing its end of life.
On 2018-Nov-30  Fedora will stop maintaining and issuing updates for
Fedora 27. It is Fedora's policy to close all bug reports from releases
that are no longer maintained. At that time this bug will be closed as
EOL if it remains open with a Fedora  'version' of '27'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 27 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Fedora 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.