Comment 14 for bug 301261

On Wed, 2008-11-26 at 11:45 +0000, peternix wrote:
> Problem appears to be fixed.

I doubt this is actually a dupe of Bug #299093, I'm still seeing this
bug. The original description mentions that pulseaudio only sees a null
output which works fine. So pulseaudio is unable to load the alsa
module.

I'm using up to date jaunty (updated 1 or 2 hours ago) and the bug is
still present in my system.

As far as i can see, pulseaudio rejects the output (input is present)
because alsalib fails.

-- Snip --
ressu@denial:~/Music/ > gst-launch-0.10 filesrc location="file.mp3" ! decodebin ! audioconvert ! audioresample ! alsasink
Setting pipeline to PAUSED ...
Pipeline is PREROLLING ...
Pipeline is PREROLLED ...
Setting pipeline to PLAYING ...
New clock: GstAudioSinkClock
Got EOS from element "pipeline0".
Execution ended after 2061024225240 ns.
Setting pipeline to PAUSED ...
Setting pipeline to READY ...
Setting pipeline to NULL ...
FREEING pipeline ...
ressu@denial:~/Music/ > gst-launch-0.10 filesrc location="file.mp3" ! decodebin ! audioconvert ! audioresample ! alsasink
Setting pipeline to PAUSED ...
Pipeline is PREROLLING ...
ERROR: from element /GstPipeline:pipeline0/GstAlsaSink:alsasink0: Could not get/set settings from/on resource.
Additional debug info:
gstalsasink.c(523): set_hwparams (): /GstPipeline:pipeline0/GstAlsaSink:alsasink0:
Unable to set hw params for playback: Invalid argument
ERROR: pipeline doesn't want to preroll.
Setting pipeline to NULL ...
FREEING pipeline ...
-- Snip --

First run is with all lines in /usr/share/alsa/pulse.conf commented and
second one is with the default content in pulse.conf. Also after
restarting pulseaudio with the commented pulse.conf, the output is
present.

I can open a new bug about the issue if it feels like a different bug,
but to me it looks like the same issue.

Regards, Sami

--
Sami Haahtinen <email address hidden>