HDMI/DP audio: ELD not updated on hotplug event
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
When using HDMI or Displayport audio, the EDID-like Data (ELD) fails to update properly when hotplugging or hot-unplugging displays. This in turn prevents tools like the GNOME sound settings control panel from accurately presenting the system's current audio capabilities.
How reproducible:
Hot plug and hot unplug an audio-capable display and observe the state of the ELDs, either by directly reading the ELD files in /proc/asound/
Steps to Reproduce:
1. Log into a desktop session with no audio-capable displays plugged in
2. Plug in an audio-capable display
3. Open the GNOME sound settings control panel
Actual results:
The audio-capable display is not selectable as an output device.
Expected results:
The audio-capable display should be selectable as an output device.
Additional info:
This bug has been fixed upstream with commit 37a3a98ef601f89
This behavior was observed on a system with an NVIDIA GPU running the NVIDIA proprietary driver. The particular NVIDIA GPU on the system is not currently compatible with Nouveau. It is possible and likely that this problem is also reproducible on other systems which do have GPUs that are compatible with Nouveau, and even on systems with HDMI or Displayport connectors being driven by non-NVIDIA GPUs.
When the ELD fails to update in response to a hotplug event, an update can be forced by accessing the underlying ALSA codec directly. For example, playing an audio stream directly via ALSA or even just reading from the /proc/asound/
tags: | added: patch |
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
apport-collect 1831945
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the Ubuntu Kernel Team.