Description of problem: Since the upgrade from Fedora 30 to Fedora 31, suspend-to-RAM messes up pulseaudio in a way that the GNOME volume icon appears muted and no audio is output any longer. Killing and restarting the logged-in user's pulseaudio driver seems to help. Version-Release number of selected component (if applicable): 13.0-1.fc31.x86_64 How reproducible: unknown Steps to Reproduce: 1. suspend the computer to RAM through GNOME's Pause button 2. wake the computer up Actual results: Expected results: Additional info:
I also have this problem since upgrading to Fedora 31 and have to issue 'pulseaudio -k' to restore sound when resuming from suspend-to-RAM.
Are we going to see a fix, or is F32 also going to ship with utterly broken pulseaudio suspend/hibernate?
Let me know what debug info is required and how to collect it.
pulseaudio-13.99.1-2.fc31.x86_64 is also affected
Seems to be a duplicate of Bug 1290977.
I also experience this problem, however I also have found that: - "pulseaudio -k" does not (always/ever) fix it - trying to fix it by changing settings pavucontrol nearly always results in immediate pulseaudio crash / CORE DUMP - the restart of pulseaudio then renders the sound "loud scratchy" and inaudible - subsequent repeats of toggling "pavucontrol->Configuration->Built-in Audio->Off/Play HiFi quality" results in further core dump/restarts of pulseaudio - changing the "pavucontrol->Output Devices->Built-in Audio Headphones + Speakers->Port" from "Speakers" to "Headphones (unplugged)" and back also affects "loud scratchy" sound and sometimes seems to cause core dump also - at some point repeating either pavucontrol-driven core dumps or 'pulseaudio -k' restores sound (haven't found reliable sequence) This affects pulseaudio-13.99.1-3.fc31.x86_64 (what I'm running), Fedora 31. Core dump in system logs looks like this: May 17 19:13:03 localhost systemd-coredump[24801]: Process 24756 (pulseaudio) of user 1000 dumped core.#012#012Stack trace of thread 24756:#012#0 0x00007f0a335aa674 pa_idxset_string_hash_func (libpulsecommon-13.99.so)#012#1 0x00007f0a335a9adc pa_hashmap_get (libpulsecommon-13.99.so)#012#2 0x00007f0a219450cf pa_alsa_ucm_set_profile (libalsa-util.so)#012#3 0x00007f0a219cffcf card_set_profile (module-alsa-card.so)#012#4 0x00007f0a336acd61 pa_card_set_profile (libpulsecore-13.99.so)#012#5 0x00007f0a21a10727 command_set_card_profile (libprotocol-native.so)#012#6 0x00007f0a335ba720 pa_pdispatch_run (libpulsecommon-13.99.so)#012#7 0x00007f0a21a1b07b pstream_packet_callback (libprotocol-native.so)#012#8 0x00007f0a335bd0f7 do_read (libpulsecommon-13.99.so)#012#9 0x00007f0a335bfedb do_pstream_read_write (libpulsecommon-13.99.so)#012#10 0x00007f0a335c029a srb_callback (libpulsecommon-13.99.so)#012#11 0x00007f0a335c0b2a srbchannel_rwloop (libpulsecommon-13.99.so)#012#12 0x00007f0a33625b73 pa_mainloop_dispatch (libpulse.so.0)#012#13 0x00007f0a33625ea2 pa_mainloop_iterate (libpulse.so.0)#012#14 0x00007f0a33625f40 pa_mainloop_run (libpulse.so.0)#012#15 0x0000559ebf0db3af main (pulseaudio)#012#16 0x00007f0a3328d1a3 __libc_start_main (libc.so.6)#012#17 0x0000559ebf0dbf9e _start (pulseaudio)#012#012Stack trace of thread 24797:#012#0 0x00007f0a3335cb36 ppoll (libc.so.6)#012#1 0x00007f0a336be144 pa_rtpoll_run (libpulsecore-13.99.so)#012#2 0x00007f0a20709b55 thread_func (module-null-sink.so)#012#3 0x00007f0a335cfdac internal_thread_func (libpulsecommon-13.99.so)#012#4 0x00007f0a3343f4e2 start_thread (libpthread.so.0)#012#5 0x00007f0a333676a3 __clone (libc.so.6) [...] May 17 19:14:00 localhost kernel: pulseaudio[24820]: segfault at 0 ip 00007f1b2635a674 sp 00007ffcd1927f38 error 4 in libpulsecommon-13.99.so[7f1b2633a000+4b000] May 17 19:14:00 localhost kernel: Code: 00 00 00 48 8d 0d e4 1a 03 00 56 e8 66 38 fe ff 48 83 c4 20 e8 cd 2c fe ff 66 66 2e 0f 1f 84 00 00 00 00 00 66 90 f3 0f 1e fa <0f> be 17 45 31 c0 84 d2 74 1a 66 90 44 89 c0 48 83 c7 01 c1 e0 05 [...] May 17 19:14:14 localhost systemd-coredump[24878]: Process 24820 (pulseaudio) of user 1000 dumped core.#012#012Stack trace of thread 24820:#012#0 0x00007f1b2635a674 n/a (n/a)
This message is a reminder that Fedora 31 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24. 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 '31'. 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 31 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 31 changed to end-of-life (EOL) status on 2020-11-24. Fedora 31 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.
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days