[Precision 5510, Realtek ALC3266, Black Headphone Out, Left] Pulseaudio fails to detect card
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
pulseaudio (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
I can not get audio out. I try the headphone jack, the headphone jack on my HDMI display, internal speakers, no nothing zip nada.
In Miltimedia > PulseAudio Volume Control > Output Devices, there are no audio devices. If I Show All Output Devices then a device called "silence" is listed. I can turn up the volume on that and see the level jumping around but nothing in my ears. The Configuration tab says no cards available.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: pulseaudio 1:8.0-0ubuntu3.3
ProcVersionSign
Uname: Linux 4.4.0-93-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/
CurrentDesktop: XFCE
Date: Mon Sep 18 10:27:49 2017
DistributionCha
# This is a distribution channel descriptor
# For more information see http://
canonical-
EcryptfsInUse: Yes
InstallationDate: Installed on 2016-10-14 (339 days ago)
InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20150720-04:06
SourcePackage: pulseaudio
Symptom: audio
Symptom_Card: HDA-Intel - HDA Intel PCH
Symptom_Jack: Black Headphone Out, Left
Title: [Precision 5510, Realtek ALC3266, Black Headphone Out, Left] Pulseaudio fails to detect card
UpgradeStatus: Upgraded to xenial on 2016-10-14 (339 days ago)
dmi.bios.date: 08/08/2016
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.2.13
dmi.board.name: 0N8J4R
dmi.board.vendor: Dell Inc.
dmi.board.version: A01
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.
dmi.product.name: Precision 5510
dmi.sys.vendor: Dell Inc.
Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1623200, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.