1

When it goes to sleep, sound working, when it wakes from sleep the sound doesn't work. So I go into gnome settings > sound and the output device has been reset to 'dummy output'. Instead of HDMI output [nvidia card driver 430.50].

Simply changing the output device in settings, back to HDMI, does not fix things.

Issuing the command pulseaudio -k does fix things. The dummy output option disappears and the HDMI option is restored. This is played out, entirely reproducible, every time the machine wakes.

Perhaps related... For a week, I had to use some external speakers via the line-out, immediately before this all started. Although all I did was plug them in, and everything worked automagically. They've since been returned.

Alternatively, one is tempted to blame it on something in the ubuntu 19.10 update? Although that might be unfair, the timing does fit.

Anyways, the question is, what is the permanent fix so that I do not have to issue a kill order on pulseaudio on every wake?

  • It's not unfair to blame the 19.10 update. Errors are expected and many have already been reported. – WinEunuuchs2Unix Nov 25 '19 at 22:47
  • I've been experiencing the same issue and made a post a few weeks ago: askubuntu.com/questions/1187835/… – Dzinic Nov 26 '19 at 17:01
  • @Dzinic Did you implement the solution offered there? I'm confident the one @WinEunuuchs2Unix has offered below will do the trick, but I'm just tinkering with features in /etc/pulse/default.pa before resorting to that-prevention before cure. Turning off module-rescue-streams is my current best hope. Will post what works, or tick that, when I've confirmed my fix. – John Mee Nov 26 '19 at 21:57
  • @JohnMee I haven't tried that yet because it doesn't seem to make much of a difference from what I currently do by simply running pulseaudio -k if I notice the Dummy Output. Problem with both of these solutions is I then have to restart several programs that break once you run the pulseaudio restart. – Dzinic Nov 26 '19 at 23:18
  • @JohnMee I was recommended to remove the proprietary nvidia driver by a developer from pulseaudio (gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/…) and after doing so the issue went away. It seems like it's an issue between the driver and the kernel. – Dzinic Nov 26 '19 at 23:54
1

It be caused by a new kernel introduced in 19.10 like this case:

If not then you can use this script /etc/systemd/system-sleep/reloadpulse:

#!/bin/sh

# NAME: reloadpulse
# PATH: /lib/systemd/system-sleep
# CALL: Called from SystemD automatically

# DESC: PulseAudo 8 sets sound to dummy ouput when going to sleep.
#       This script kills and reloads pulse audio.

# DATE: November 25, 2019.

# NOTE: Written for ask ubuntu question:
#       https://askubuntu.com/questions/1191649/why-no-sound-on-wake-dummy-output-takes-over-pulseaudio-k-the-fix

case $1/$2 in
  pre/*)
    echo "$0: Going to $2..."
    ;;
  post/*)
    echo "$0: Waking up from $2..."
    pulseaudio -k
    ;;
esac

Mark the script executable with chmod a+x /etc/systemd/system-sleep/reloadpulse

After updates deactivate it with chmod a-x /etc/systemd/system-sleep/reloadpulse

Then if the update didn't fix the problem make it executable again.

You need to reboot for changes to take effect.

0

Disable the pulseaudio module module-rescue-streams by sudo editing the file /etc/pulse/default.pa and commenting it out.

### Automatically move streams to the default sink if the sink they are
### connected to dies, similar for sources
# I commented this out to stop it defaulting to a 'dummy output' after sleep/suspend [JM:november 2019]
# load-module module-rescue-streams

I'm guessing that there has been a change in the wake sequence such that, now, this runs before all the sound sinks are restored. Consequently, it decides all the 'dead' sinks need to be "rescued" to a new default/dummy sink. They all subsequently wake up, but they've already been rerouted to the dummy.

I'm also guessing that this could break some ability to unplug and replug speakers/headphones as and whenever you like, but I haven't discovered that for myself yet.

  • Didn't fix the issue for me but glad it worked out for you. – Dzinic Nov 27 '19 at 23:50

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.