WD15 Dell Thunderbolt dock no audio
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
pulseaudio (Ubuntu) |
Invalid
|
High
|
Hui Wang |
Bug Description
Followup from bug 1718824 and bug 1745765 respectively as reported in the other bugs neither front (headphones) nor back (line-out) jack is working after the updates.
A Workaround manually adding the profile for pulseaudio might have been persistet from changes before the upgrade / updates.
pactl is listed in the other bug, alsa-info should be automatically attached.
Output of pactl info:
"benste@
Server String: unix:/run/
Library Protocol Version: 32
Server Protocol Version: 32
Is Local: yes
Client Index: 21
Tile Size: 65472
User Name: benste
Host Name: benste-xps13-ubuntu
Server Name: pulseaudio
Server Version: 11.1
Default Sample Specification: s16le 2ch 44100Hz
Default Channel Map: front-left,
Default Sink: alsa_output.
Default Source: alsa_input.
Cookie: bb32:a8fe"
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: pulseaudio 1:11.1-1ubuntu7
ProcVersionSign
Uname: Linux 4.15.0-20-generic x86_64
NonfreeKernelMo
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
/dev/snd/pcmC1D0c: benste 2287 F...m pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Mon May 21 11:06:17 2018
EcryptfsInUse: Yes
InstallationDate: Installed on 2016-10-13 (584 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
SourcePackage: pulseaudio
UpgradeStatus: Upgraded to bionic on 2018-04-28 (22 days ago)
dmi.bios.date: 10/03/2017
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 2.3.1
dmi.board.name: 0T3FTF
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.
dmi.product.family: XPS
dmi.product.name: XPS 13 9360
dmi.sys.vendor: Dell Inc.
Changed in pulseaudio (Ubuntu): | |
importance: | Undecided → High |
assignee: | nobody → Hui Wang (hui.wang) |
There haven't been any updates to pulseaudio in bionic. So do you mean it regressed a while ago in an artful update?
Do you know the last version in which it was working?