• Systemd messages


    Hi guys,

    any way of fixing these errors ?

    [pulseaudio] pid.c: Daemon already running.

    [alsa-sink-USB Audio] alsa-sink.c: ALSA woke us up to write new data to the device, but there was actually nothing to write!
    [alsa-sink-USB Audio] alsa-sink.c: Most likely this is a bug in the ALSA driver ‘snd_usb_audio’. Please report this issue to the ALSA developers.
    [alsa-sink-USB Audio] alsa-sink.c: We were woken up with POLLOUT set – however a subsequent snd_pcm_avail() returned 0 or another value < min_avail.

  • Hi guys,

    any way of fixing these errors ?

    [pulseaudio] pid.c: Daemon already running.

    [alsa-sink-USB Audio] alsa-sink.c: ALSA woke us up to write new data to the device, but there was actually nothing to write!
    [alsa-sink-USB Audio] alsa-sink.c: Most likely this is a bug in the ALSA driver ‘snd_usb_audio’. Please report this issue to the ALSA developers.
    [alsa-sink-USB Audio] alsa-sink.c: We were woken up with POLLOUT set – however a subsequent snd_pcm_avail() returned 0 or another value < min_avail.

  • I have not been able to find a fix for this bug. The error messages are common to most arch systems lately. I first noticed them a couple months ago. Most systems don’t show any performance issues related to these errors. Well, besides what we in the linux community have grown to accept from alsa/pa. This is an interesting article on the state of sound in linux: [http://www.techrepublic.com/blog/linux-and-open-source/pulseaudio-an-achilles-heel-that-needs-repair/][0]">[http://www.techrepublic.com/blog/linux-][1] … ds-repair/

    Sorry couldn’t be of more help

    Best Regards,

    [0]: <a href=
    [1]: http://www.techrepublic.com/blog/linux-

  • I can live with that I guess

Posts 4Views 848
Log in to reply