[Compaq 610, IDT 92HD75B2X5, Black Headphone Out, Front] Pulseaudio fails to detect card
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
pulseaudio (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
ly sound device not working
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: pulseaudio 1:1.1-0ubuntu4
ProcVersionSign
Uname: Linux 3.2.0-10-generic i686
NonfreeKernelMo
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
AplayDevices:
**** List of PLAYBACK Hardware Devices ****
card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
Subdevices: 0/1
Subdevice #0: subdevice #0
ApportVersion: 1.91-0ubuntu1
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: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xe8504000 irq 47'
Mixer name : 'IDT 92HD75B2X5'
Components : 'HDA:111d7608,
Controls : 14
Simple ctrls : 9
Date: Sat Mar 3 15:44:56 2012
ProcEnviron:
PATH=(custom, no user)
LANG=en_IN
SHELL=/bin/bash
SourcePackage: pulseaudio
Symptom: audio
Symptom_Card: HDA-Intel - HDA Intel
Symptom_Jack: Black Headphone Out, Front
Title: [Compaq 610, IDT 92HD75B2X5, Black Headphone Out, Front] Pulseaudio fails to detect card
UpgradeStatus: Upgraded to precise on 2012-02-17 (14 days ago)
dmi.bios.date: 11/24/2009
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68PVD Ver. F.0C
dmi.board.name: 308B
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 26.08
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnHewlett-
dmi.product.name: Compaq 610
dmi.product.
dmi.sys.vendor: Hewlett-Packard
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.