Comment 5 for bug 276582

booting up my computer yesterday revealed no sound, even after "killall
pulseaudio"
i did another update with update manager.. returned home just now and tried
again, this time
killall pulseaudio worked again.
i have an m-audio delta 44.
strange that this won't just simply work after all this trouble with pulse.
why does an interface work, and later on when the support for the device
should be improved, the device stops working
instead.... ?

On Sun, Nov 2, 2008 at 10:36 PM, Pekka Vuorela <email address hidden> wrote:

> This seems to still be present in Intrepid final with my Delta66.
> Additionally, the gnome-sound-properties (Sound Preferences) freezes
> when the above error is shown. Clicking on the close button leaves the
> button as pushed down and the window cannot be even closed. The
> application has to be killed to get rid of it when autodetect or
> pulseaudio output are tested.
>
> Also setting the device to ALSA doesn't work anymore as it did with
> Hardy. Default Alsa output seems to be Pulseaudio so I had to comment
> out the corresponding line from /usr/share/alsa/alsa.conf to get my
> audio working. Not a really nice fix.
>
> --
> Sound Preferences error with M-Audio Delta44 in Intrepid Alpha 6
> https://bugs.launchpad.net/bugs/276582
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in PulseAudio sound server: New
> Status in Ubuntu: New
>
> Bug description:
> clicking the "Test" button on any row in Intrepid's Sound Preferences off
> the live CD system reveals this error message:
> "audiotestsrc wave=sine freq=512 ! audioconvert ! audioresample !
> gconfaudiosink: Failed to connect stream: Invalid argument"
>
> it is known to be most likely pulseaudio related
>
> when set to ALSA, any of the lines will render a clean test signal upon
> clicking "test"
>