FS#67772 - [linux] Updating to 5.8 breaks headphone detection.

Attached to Project: Arch Linux
Opened by Kamil Krzyżanowski (kamnxt) - Sunday, 30 August 2020, 16:35 GMT
Last edited by Andreas Radke (AndyRTR) - Tuesday, 01 March 2022, 21:16 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To Tobias Powalowski (tpowa)
Jan Alexander Steffens (heftig)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:

After upgrading to 5.8, headphone detection stopped working on my laptop (Dell XPS 15 9560).
Reverting to 5.7 causes it to work again.

Additional info:
* core/linux 5.8.arch1-1 to 5.8.5.arch1-1
* using Pulseaudio 13.99.1

Steps to reproduce:
Run Linux 5.7 kernel
run `pulseaudio -vv`
plug in headphones
headphones get detected, pulseaudio reports "D: [pulseaudio] device-port.c: Setting port analog-output-headphones to status plugged"
output switches to headphones automatically.

Update to 5.8 kernel
run `pulseaudio -vv`
plug in headphones
headphones do get detected, but pulseaudio reports "D: [pulseaudio] device-port.c: Setting port analog-output-headphones to status unknown"
output stays on speakers, which are muted as the headphones are plugged in. no sound until I either select headphone output or unplug headphones.

At first I thought it was something about pulseaudio alsa-mixer paths, but after downgrading to 5.7 (due to another bug) it started working fine again. After upgrading to 5.8.5 now it still doesn't work.
This task depends upon

Closed by  Andreas Radke (AndyRTR)
Tuesday, 01 March 2022, 21:16 GMT
Reason for closing:  Fixed
Comment by Jan-Jaap Korpershoek (JJK) - Monday, 14 September 2020, 11:34 GMT
I had this problem when switching to Linux 5.8.

But as of Linux 5.8.7 this works again for me.

This is on a Dell Precision 5520.
Comment by mattia (nTia89) - Monday, 28 February 2022, 16:36 GMT
I cannot reproduce the issue. Is it still valid for you?
Comment by Kamil Krzyżanowski (kamnxt) - Tuesday, 01 March 2022, 08:42 GMT
Nope, must have gotten fixed a good while ago :)

Loading...