Hide Forgot
Description of problem: Sound card is randomly not detected after waking up from hibernation. If the machine is restarted, then the sound card is detected. Version-Release number of selected component (if applicable): Latest pulseaudio version in Fedora 25 fully updated. How reproducible: Many times after waking up the computer from hibernation. Other times the sound card is detected. Steps to Reproduce: 1.Put the system in hibernation mode. 2.Wake up the system. 3.No sound / sound card missing. Actual results: No sound. Expected results: Sound as usual. Additional info: After some research, I ran the pacmd list command and got the following, suggesting the onboard sound card is indeed detected: 1 card(s) available. index: 0 name: <alsa_card.pci-0000_00_1b.0> driver: <module-alsa-card.c> owner module: 6 properties: alsa.card = "0" alsa.card_name = "HDA Intel PCH" alsa.long_card_name = "HDA Intel PCH at 0xf7d10000 irq 31" alsa.driver_name = "snd_hda_intel" device.bus_path = "pci-0000:00:1b.0" sysfs.path = "/devices/pci0000:00/0000:00:1b.0/sound/card0" device.bus = "pci" device.vendor.id = "8086" device.vendor.name = "Intel Corporation" device.product.id = "1e20" device.product.name = "7 Series/C210 Series Chipset Family High Definition Audio Controller (P8H77-I Motherboard)" device.form_factor = "internal" device.string = "0" device.description = "Built-in Audio" module-udev-detect.discovered = "1" device.icon_name = "audio-card-pci" I am just guessing it is a pulseaudio issue. Not totally sure about it.
Can you include the content/output from alsa-info.sh ?
Here is the information as requested: [francisco@localhost ~]$ alsa-info.sh ALSA Information Script v 0.4.64 -------------------------------- This script visits the following commands/files to collect diagnostic information about your ALSA installation and sound related hardware. dmesg lspci lsmod aplay amixer alsactl /proc/asound/ /sys/class/sound/ ~/.asoundrc (etc.) See '/usr/sbin/alsa-info.sh --help' for command line options. Automatically upload ALSA information to www.alsa-project.org? [y/N] : y Uploading information to www.alsa-project.org ... Done! Your ALSA information is located at http://www.alsa-project.org/db/?f=0f187dd25a0e98d1f4e5268a27a9a1544c081bdb Please inform the person helping you. The command was run as soon as the problem appeared again. I am also including two sound settings screenshots.
Created attachment 1227733 [details] Screenshot before going to hibernate
Created attachment 1227734 [details] Screenshot after waiking up from hibernation
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.
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 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.