Comment 40 for bug 1589008

I think that one of the recent updates fixed it (and it also survives S2RAM):

libpulse0 1:8.0-0ubuntu3.3
libpulsedsp 1:8.0-0ubuntu3.3
libpulse-mainloop-glib0 1:8.0-0ubuntu3.3
pulseaudio 1:8.0-0ubuntu3.3
pulseaudio-module-bluetooth 1:8.0-0ubuntu3.3
pulseaudio-module-gconf 1:8.0-0ubuntu3.3
pulseaudio-module-x11 1:8.0-0ubuntu3.3
pulseaudio-module-zeroconf 1:8.0-0ubuntu3.3
pulseaudio-utils 1:8.0-0ubuntu3.3

linux-generic-hwe-16.04 4.8.0.58.29
linux-headers-4.8.0-58 4.8.0-58.63~16.04.1
linux-headers-4.8.0-58-generic 4.8.0-58.63~16.04.1
linux-headers-generic-hwe-16.04 4.8.0.58.29
linux-hwe-tools-4.8.0-58 4.8.0-58.63~16.04.1
linux-image-4.8.0-58-generic 4.8.0-58.63~16.04.1
linux-image-extra-4.8.0-58-generic 4.8.0-58.63~16.04.1
linux-image-generic-hwe-16.04 4.8.0.58.29
linux-tools-4.8.0-58-generic 4.8.0-58.63~16.04.1
linux-tools-generic-hwe-16.04 4.8.0.58.29

I could not reproduce this issue at least. This time, I repaired my device with Blueman as pure audio device. Could also be that this works around the issue. At least does it seem to work now.