Dummy Output for audio output device after upgrade to focal
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
pulseaudio (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
After and upgrade to Focal audio output not working. Dummy Output device in the sound settings.
It seems like drivers are loaded:
00:1f.3 Audio device: Intel Corporation Device 02c8 (prog-if 80)
Subsystem: Lenovo Device 2292
Flags: bus master, fast devsel, latency 64, IRQ 177
Memory at ea23c000 (64-bit, non-prefetchable) [size=16K]
Memory at ea000000 (64-bit, non-prefetchable) [size=1M]
Kernel driver in use: sof-audio-pci
Kernel modules: snd_hda_intel, snd_sof_pci
#champagne
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: pulseaudio 1:13.0-3ubuntu1
ProcVersionSign
Uname: Linux 5.4.0-12-generic x86_64
ApportVersion: 2.20.11-0ubuntu15
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CurrentDesktop: ubuntu:GNOME
Date: Tue Jan 28 10:02:41 2020
InstallationDate: Installed on 2019-12-25 (33 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
ProcEnviron:
TERM=screen-
PATH=(custom, no user)
XDG_RUNTIME_
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: pulseaudio
UpgradeStatus: Upgraded to focal on 2020-01-27 (0 days ago)
dmi.bios.date: 10/18/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: N2QET15W (1.09 )
dmi.board.
dmi.board.name: 20R1S05A00
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.
dmi.modalias: dmi:bvnLENOVO:
dmi.product.family: ThinkPad X1 Carbon 7th
dmi.product.name: 20R1S05A00
dmi.product.sku: LENOVO_
dmi.product.
dmi.sys.vendor: LENOVO
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 1860697, 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.