http://bugzilla.suse.com/show_bug.cgi?id=979049
http://bugzilla.suse.com/show_bug.cgi?id=979049#c18
--- Comment #18 from Takashi Iwai
(In reply to Takashi Iwai from comment #16)
I've bought this stick because a) it has a builtin BT audio support (A"DP as well as aptX, that is nothing to do for alsa) and b) it had worked in past with older kernel/alsa version (compare with comment #2). The question rises: why does now not work with current kernel/alsa version? Is there any way to cause alsa usb driver to wait on BTD USB device currently connecting to the headphone up to the point where it is ready ... currently alsa reports POLLNVAL to pulseaudio:
pulseaudio[2112]: [alsa-sink-USB Audio] alsa-util.c: Got POLLNVAL from ALSA pulseaudio[2112]: [alsa-sink-USB Audio] alsa-util.c: Could not recover from POLLERR|POLLNVAL|POLLHUP with snd_pcm_prepare(): No such device
As the error indicate, PA is likely trying to access to the stale device that has been reset and thus virtually disconnected. At the reconnect, the USB-audio driver registers as another sound card. Maybe PA is confused for the resume recovery while the device itself got lost. You can try the older kernel on your Leap 42.1 system to confirm that it's a kernel side regression, too. -- You are receiving this mail because: You are on the CC list for the bug.