← Back to team overview

touch-packages team mailing list archive

[Bug 221673] Re: ALSA failing with PulseAudio in Hardy

 

Hardy has seen the end of its life and is no longer receiving any
updates. Marking the Hardy task for this ticket as "Won't Fix".

** Changed in: alsa-plugins (Ubuntu Hardy)
       Status: Triaged => Won't Fix

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-lib in Ubuntu.
https://bugs.launchpad.net/bugs/221673

Title:
  ALSA failing with PulseAudio in Hardy

Status in “alsa-lib” package in Ubuntu:
  Fix Released
Status in “alsa-plugins” package in Ubuntu:
  Fix Released
Status in “pulseaudio” package in Ubuntu:
  Invalid
Status in “alsa-lib” source package in Hardy:
  Won't Fix
Status in “alsa-plugins” source package in Hardy:
  Won't Fix
Status in “pulseaudio” source package in Hardy:
  Invalid

Bug description:
  Binary package hint: pulseaudio

  I had been using PulseAudio in Gutsy for the past several months, so
  all the mundane stuff (groups, permissions, config files) is
  configured correctly. Since the upgrade to Hardy, ALSA is unable to
  use PulseAudio anymore. Details follow:

  - I am in the groups pulse-rt and pulse-access
  - ALSA without PulseAudio works just fine
  - PulseAudio seems to work fine with GStreamer

  Here's what my .asoundrc looks like:
  =======================
  pcm.pulse {
      type pulse
  }
  ctl.pulse {
      type pulse
  }
  pcm.!default { type pulse }
  ctl.!default { type pulse }
  =======================

  I'm attaching my default.pa with the bug.

  Here's the output of 'pulseaudio -vvv' when I try to run speaker-test (only relevant portion here, full output attached):
  I: client.c: Created 1 "Native client (UNIX socket client)"
  I: protocol-native.c: Got credentials: uid=1000 gid=1000 success=1
  I: protocol-native.c: Enabled SHM for new connection
  I: client.c: Client 1 changed name from "Native client (UNIX socket client)" to "ALSA plug-in [speaker-test]"
  I: client.c: Freed 1 "ALSA plug-in [speaker-test]"
  I: protocol-native.c: connection died.

  speaker-test fails with the following:
  WAV file(s)
  Rate set to 48000Hz (requested 48000Hz)
  Buffer size range from 43 to 349525
  Period size range from 21 to 87382
  Using max buffer size 349524
  Periods = 4
  was set period_size = 87381
  was set buffer_size = 349524
  *** PULSEAUDIO: Unable to create stream.
  Unable to set hw params for playback: Input/output error
  Setting of hwparams failed: Input/output error
  speaker-test: pcm_pulse.c:115: pulse_stop: Assertion `pcm->stream' failed.
  Aborted

  TEST CASE:
  1. Create an .asoundrc file in your home directory to direct alsa to use the pulseaudio plugin by default for all sound output. This is done with the command "asoundconf set-pulseaudio"
  2. Attempt to run speaker-test with the following command: "speaker-test -twav -c2"
  3. You should get the following error:

  *** PULSEAUDIO: Unable to create stream.
  speaker-test: pcm_pulse.c:115: pulse_stop: Assertion `pcm->stream' failed.

  speaker-test 1.0.15

  Playback device is default
  Stream parameters are 48000Hz, S16_LE, 2 channels
  WAV file(s)
  Rate set to 48000Hz (requested 48000Hz)
  Buffer size range from 128 to 1048576
  Period size range from 64 to 262144
  Using max buffer size 1048576
  Periods = 4
  was set period_size = 262144
  was set buffer_size = 1048576
  Unable to set hw params for playback: Input/output error
  Setting of hwparams failed: Input/output error

  
  NOTE: This SRU is in two parts, one for alsa-lib, and the other for alsa-plugins. The new revision of alsa-plugins requires the new revision of alsa-lib in order to function properly.

  Intrepid status:
  This bug is fixed with alsa-lib 1.0.16 and alsa-plugins 1.0.16 which are both in intrepid.

  Regression potential:
  The diffs in comments 8 and 9 introduce fixes and in the case of alsa-lib, new symbols to be used by alsa-plugins to allow the pulse alsa-plugin to functino properly No other plugin's functionality should be affected with these changes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/221673/+subscriptions