| 2008-04-25 03:57:19 |
Diwaker Gupta |
bug |
|
|
added bug |
| 2008-04-25 03:57:19 |
Diwaker Gupta |
bug |
|
|
added attachment 'default.pa' (default.pa) |
| 2008-04-25 03:58:54 |
Diwaker Gupta |
bug |
|
|
added attachment 'pulseaudio.log' (pulseaudio.log) |
| 2008-04-25 15:01:59 |
Nikolaus Rath |
pulseaudio: status |
New |
Confirmed |
|
| 2008-04-27 10:48:59 |
Victor Engmark |
bug |
|
|
added attachment '.asoundrc.asoundconf' (.asoundrc.asoundconf) |
| 2008-05-30 06:16:57 |
Luke Yelavich |
bug |
|
|
assigned to alsa-lib (Ubuntu) |
| 2008-05-30 06:17:33 |
Luke Yelavich |
bug |
|
|
assigned to alsa-plugins (Ubuntu) |
| 2008-05-30 06:21:08 |
Luke Yelavich |
pulseaudio: status |
Confirmed |
Invalid |
|
| 2008-05-30 06:21:39 |
Luke Yelavich |
alsa-lib: status |
New |
In Progress |
|
| 2008-05-30 06:21:39 |
Luke Yelavich |
alsa-lib: assignee |
|
themuso |
|
| 2008-05-30 06:21:57 |
Luke Yelavich |
alsa-plugins: status |
New |
In Progress |
|
| 2008-05-30 06:21:57 |
Luke Yelavich |
alsa-plugins: assignee |
|
themuso |
|
| 2008-05-30 07:12:25 |
Luke Yelavich |
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 |
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 patch to alsa-lib only touches the ioplug plugin, used by various plugins from alsa-plugins, as well as other plugins that may be available either in the archive, or built by users elsewhere. The
patch makes two changes, the first being to return -EPIPE if the io data state records an xrun, and the second is to add a function to allow the correct setting of the io data state. This second
change introduces a new symbol, hense the shlibs bump. Since only one plugin, i.e the pulseaudio plugin will use this new function, nothing else should be broken with the addition of one symbol that
will be only used by one plugin, at least from the Ubuntu archive.
The changes to alsa-plugins are only to the pulseaudio plugin, firstly to remove unneeded asserts, as well as to lock the pulseaudio mainloop in the correct place, which cause such errors as above.
The second change is to make use of the newly introduced function in the alsa-lib ioplug plugin to properly report the state of the application. The required build-dependency on alsa-lib has also
been updated. The possibility of a regression is minimal to none at all.
All patches are already upstream in alsa 1.0.16.
|
|
| 2008-05-30 07:14:25 |
Luke Yelavich |
bug |
|
|
added attachment 'alsa-lib.debdiff' (alsa-lib diff) |
| 2008-05-30 07:19:27 |
Luke Yelavich |
bug |
|
|
added attachment 'pulseaudio.debdiff' (alsa-plugins diff) |
| 2008-06-12 10:10:08 |
Steve Langasek |
alsa-plugins: status |
In Progress |
Fix Released |
|
| 2008-06-12 10:10:36 |
Steve Langasek |
alsa-lib: status |
In Progress |
Fix Released |
|
| 2008-06-12 10:11:06 |
Steve Langasek |
alsa-lib: status |
New |
Incomplete |
|
| 2008-06-12 10:11:06 |
Steve Langasek |
alsa-lib: assignee |
|
themuso |
|
| 2008-06-12 10:11:11 |
Steve Langasek |
alsa-lib: status |
Incomplete |
In Progress |
|
| 2008-06-12 10:11:31 |
Steve Langasek |
alsa-plugins: status |
New |
In Progress |
|
| 2008-06-12 10:11:31 |
Steve Langasek |
alsa-plugins: assignee |
|
themuso |
|
| 2008-06-12 10:11:57 |
Steve Langasek |
pulseaudio: status |
New |
Invalid |
|
| 2008-06-13 03:03:55 |
Luke Yelavich |
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 patch to alsa-lib only touches the ioplug plugin, used by various plugins from alsa-plugins, as well as other plugins that may be available either in the archive, or built by users elsewhere. The
patch makes two changes, the first being to return -EPIPE if the io data state records an xrun, and the second is to add a function to allow the correct setting of the io data state. This second
change introduces a new symbol, hense the shlibs bump. Since only one plugin, i.e the pulseaudio plugin will use this new function, nothing else should be broken with the addition of one symbol that
will be only used by one plugin, at least from the Ubuntu archive.
The changes to alsa-plugins are only to the pulseaudio plugin, firstly to remove unneeded asserts, as well as to lock the pulseaudio mainloop in the correct place, which cause such errors as above.
The second change is to make use of the newly introduced function in the alsa-lib ioplug plugin to properly report the state of the application. The required build-dependency on alsa-lib has also
been updated. The possibility of a regression is minimal to none at all.
All patches are already upstream in alsa 1.0.16.
|
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:
alsa-lib 1.0.16 introduces new symbols related to plugins, but doesn't change any of the API for existing applications that use alsa. Thus the regression potential is minimal.
|
|
| 2008-06-13 03:08:41 |
Luke Yelavich |
bug |
|
|
added attachment 'changelog.ALSA-lib' (alsa-lib changelog) |
| 2008-06-13 03:09:06 |
Luke Yelavich |
bug |
|
|
added attachment 'changelog.ALSA-plugins' (alsa-plugins changelog) |
| 2008-06-13 08:22:05 |
Martin Pitt |
alsa-lib: status |
In Progress |
Fix Committed |
|
| 2008-06-13 08:22:12 |
Martin Pitt |
alsa-plugins: status |
In Progress |
Fix Committed |
|
| 2008-06-13 22:42:28 |
Steve Langasek |
alsa-lib: milestone |
|
ubuntu-8.04.1 |
|
| 2008-06-24 17:57:12 |
Brian Murray |
alsa-plugins: status |
Fix Committed |
Triaged |
|
| 2008-06-24 17:58:26 |
Brian Murray |
alsa-lib: status |
Fix Committed |
Triaged |
|
| 2008-06-25 02:00:26 |
Luke Yelavich |
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:
alsa-lib 1.0.16 introduces new symbols related to plugins, but doesn't change any of the API for existing applications that use alsa. Thus the regression potential is minimal.
|
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.
|
|
| 2008-08-05 22:45:40 |
Steve Langasek |
alsa-lib: milestone |
ubuntu-8.04.1 |
ubuntu-8.04.2 |
|
| 2009-01-26 08:18:28 |
Steve Langasek |
alsa-lib: milestone |
ubuntu-8.04.2 |
|
|
| 2009-07-17 19:10:11 |
Launchpad Janitor |
branch linked |
|
lp:ubuntu/hardy-proposed/alsa-plugins |
|
| 2009-12-05 09:15:40 |
Launchpad Janitor |
branch linked |
|
lp:ubuntu/hardy-proposed/alsa-lib |
|
| 2012-05-18 20:22:35 |
Adolfo R. Brandes |
removed subscriber Adolfo R. Brandes |
|
|
|
| 2014-04-10 04:39:22 |
Luke Yelavich |
alsa-lib (Ubuntu Hardy): assignee |
Luke Yelavich (themuso) |
|
|
| 2014-11-23 15:10:29 |
Rolf Leggewie |
alsa-lib (Ubuntu Hardy): status |
Triaged |
Won't Fix |
|
| 2014-11-23 15:10:34 |
Rolf Leggewie |
alsa-plugins (Ubuntu Hardy): status |
Triaged |
Won't Fix |
|
