[OptiPlex 3050, Realtek ALC3234, Black Headphone Out, Front] No sound at all
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
alsa-driver (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
As soon as I've booted my ubuntu 19.10, I've plugged my headphones and got some clicking sound, but then there was no sound at all afterwards.
The device shows on Settings > Output and it's detected by alsamixer also.
The headphone works normally on my phone.
This is the first time I've booted ubuntu since I've updated it (not considering when you have to do so for the installing process). Sound worked normally back then.
Only sound I hear is the clicking sound whenever I plug it in and off.
Headphone is at maximum gain on alsamixer.
HW info shows at title.
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: alsa-base 1.0.25+
ProcVersionSign
Uname: Linux 5.3.0-23-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
/dev/snd/pcmC0D0p: tadeu 1556 F...m pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Mon Nov 25 07:51:05 2019
InstallationDate: Installed on 2019-03-27 (242 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
PackageArchitec
SourcePackage: alsa-driver
Symptom: audio
Symptom_
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_
USER PID ACCESS COMMAND
/dev/snd/
/dev/snd/pcmC0D0p: tadeu 1556 F...m pulseaudio
Symptom_Jack: Black Headphone Out, Front
Symptom_Type: No sound at all
Title: [OptiPlex 3050, Realtek ALC3234, Black Headphone Out, Front] No sound at all
UpgradeStatus: Upgraded to eoan on 2019-11-22 (3 days ago)
dmi.bios.date: 08/09/2018
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.10.2
dmi.board.name: 0JP3NX
dmi.board.vendor: Dell Inc.
dmi.board.version: A01
dmi.chassis.type: 3
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.
dmi.product.family: OptiPlex
dmi.product.name: OptiPlex 3050
dmi.product.sku: 07A3
dmi.sys.vendor: Dell Inc.
Status changed to 'Confirmed' because the bug affects multiple users.