KARMIC: Audio Playback hangs on subsequent file
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
pulseaudio (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: pulseaudio
Since the latest pulseaudio upgrade to 1:0.9.19-0ubuntu3 applications like rhythmbox or totem sometimes fail to play audio when repeating or playing the next video/audio file in the playlist. There is a thread in http://
"When Totem gets to the end of a file it is playing (seemingly any filetype, audio or video), it won't play anything more for an indeterminate amount of time. If you have a playlist it will move to the next item and claim to be playing it, but with no AV output or timeline progression. Often, several minutes later it will suddenly burst into life and start playing the track.
Clicking pause/play, changing track or loading a new file in doesn't help in this state; nothing will play until Totem randomly wakes up, or you quit/reload it."
I noticed the following messages in syslog, when the problem occured:
Oct 21 14:44:31 morryis-laptop pulseaudio[3941]: protocol-native.c: Failed to push data into queue
Oct 21 14:44:31 morryis-laptop pulseaudio[3941]: protocol-native.c: Failed to push data into queue
Oct 21 14:44:31 morryis-laptop pulseaudio[3941]: protocol-native.c: Failed to push data into queue
ProblemType: Bug
Architecture: i386
ArecordDevices:
**** List of CAPTURE Hardware Devices ****
card 0: Intel [HDA Intel], device 0: CONEXANT Analog [CONEXANT Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
/dev/snd/pcmC0D0p: morryis 3941 F...m pulseaudio
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xfc020000 irq 17'
Mixer name : 'Conexant CX20561 (Hermosa)'
Components : 'HDA:14f15051,
Controls : 14
Simple ctrls : 7
Date: Wed Oct 21 14:49:40 2009
DistroRelease: Ubuntu 9.10
Package: pulseaudio 1:0.9.19-0ubuntu3
ProcEnviron:
LANG=de_DE.UTF-8
SHELL=/bin/bash
ProcVersionSign
SourcePackage: pulseaudio
Uname: Linux 2.6.31-14-generic i686
This symptom actually sounds more like a GSt issue. Can you reproduce
it from a command line with gst-launch and GST_DEBUG set to 3?