Sound of Rhythm box, Flash and other alsa dependant apps become cracky and noise from time to time

Bug #683722 reported by cablop on 2010-12-01
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
PulseAudio
New
Undecided
Unassigned
alsa-driver (Ubuntu)
Undecided
Unassigned

Bug Description

From time to time sound played by Rhythmbox and Alsa become crappy, cracky and noisy (for me that it starts to sound like square waves instead of sound waves or sound like weirdly filtered waves).

Some things that "pull the trigger" was sound events like instant mesagging events sounds (as in emesene, pidgin and skype).

The problem is more common after a long time of use of the computer, like 12 hours or so and the more the time the more common, after three days of continuous usage it happens every three to ten minutes.

It is also common after hibernations, and also, the more you hibernate the more common the issue is.

If you stop playback for a while, one minute or more, then it becomes normal again, but if you keep playing sound the issue persist, even for hours.

To close the application, that is to close or reload a page with flash (in order to make it reload the flash-player) or close and reopen rhythmbox make them play the sound right, and 'solves' thew issue faster than waiting more than a minute.

Anyway it makes it impossible to use the computer to play music in a reliable way.

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: alsa-base 1.0.23+dfsg-1ubuntu4
ProcVersionSignature: Ubuntu 2.6.35-23.40-generic 2.6.35.7
Uname: Linux 2.6.35-23-generic i686
NonfreeKernelModules: wl
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
AplayDevices:
 **** List of PLAYBACK Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
   Subdevices: 0/1
   Subdevice #0: subdevice #0
Architecture: i386
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: cablop 2027 F.... pulseaudio
 /dev/snd/pcmC0D0p: cablop 2027 F...m pulseaudio
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xfe938000 irq 43'
   Mixer name : 'IDT 92HD81B1X5'
   Components : 'HDA:111d7605,103c1468,00100402'
   Controls : 14
   Simple ctrls : 9
Date: Wed Dec 1 15:38:28 2010
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100427.1)
PackageArchitecture: all
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
SourcePackage: alsa-driver
dmi.bios.date: 11/05/2009
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 14680 Ver. F.01
dmi.board.name: 1468
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 02.10
dmi.chassis.asset.tag: CNU00949BP
dmi.chassis.type: 10
dmi.chassis.vendor: Inventec
dmi.modalias: dmi:bvnHewlett-Packard:bvr14680Ver.F.01:bd11/05/2009:svnHewlett-Packard:pnCompaqMiniCQ10-100:pvr0493200000001C00000300000:rvnHewlett-Packard:rn1468:rvrKBCVersion02.10:cvnInventec:ct10:cvr:
dmi.product.name: Compaq Mini CQ10-100
dmi.product.version: 0493200000001C00000300000
dmi.sys.vendor: Hewlett-Packard

cablop (cablop) wrote :
cablop (cablop) wrote :

It was reported before as a problem between Rhythmbox and IM event messages, but it is also happening with no im open, so the im messages just increase the probability as the messages sometimes trigger the problem, but they're not the cause.

cablop (cablop) wrote :

the other bug report says maybe it is an alsa/hardware issue, but i was sending today the sound to another machine via the pulseaudio server and it happened also... three times... so it is not a coincidence... that makes me thing the problem is in the alsa>pulseaudio pipeline...

This release of Ubuntu is no longer receiving maintenance updates. If this is still an issue on a maintained version of Ubuntu please let us know.

Changed in alsa-driver (Ubuntu):
status: New → Incomplete

This issue has sat incomplete for more than 60 days now. I'm going to close it as invalid. Please feel free re-open if this is still an issue for you. Thank you.

Changed in alsa-driver (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers