Output Device selection messed (Line Out <-> HDMI)

Bug #1901538 reported by Florian Schwarz
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-control-center (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

[System]
- Freshly installed Ubuntu 20.04.1 LTS with 3rd party software/drivers enabled
- pulseaudio 1:13.99.1-1ubuntu3.7
- NVIDIA graphics card (GeForce GTX 650 Ti Boost) using nvidia-driver-450
- Monitor with build-in (stereo) speakers connected via HDMI to graphics card
- External (stereo) speakers connected via audio jack to mainboard

[Expected Behavior]

1. Go to "Settings" -> "Sound" -> "Output" -> "Output Device"
2. Switch from "HDMI / DisplayPort 2 - GK106 HDMI Audio Controller" to "Line Out - Built-in Audio"
3. The switching should enable the chosen output device.

[Bug Description and Behavior]

If I switch from "HDMI / DisplayPort 2 - GK106 HDMI Audio Controller" to "Line Out - Built-in Audio" and test the output, sound comes still from monitor speakers and not from my external speakers.

[Workaround]

While "HDMI / DisplayPort 2 - GK106 HDMI Audio Controller" selected, go to "Configuration" and switch from "Digital Stereo (HDMI 2) Output" to "Digital Surround 5.1 (HDMI 2) Output". Instantly "Configuration" row disappears, in Output Device "Line Out - Built-in Audio" is selected and external speakers are active.

[Further comments]

I'm affected by this bug and the "wrong audio output on every reboot/wake up/login" since upgrade to 20.04 but the latter may be worth another bug report or maybe you could guide me to an active bug report that isn't linked to a previous Ubuntu version and already marked as fixed.
At first I thought it may be caused by failed upgrade or my system configurations, but now I tested with a freshly installed Ubuntu on a spare SSD and the problem still exists, so here I am.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-control-center 1:3.36.4-0ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
Uname: Linux 5.4.0-52-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.10
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Mon Oct 26 13:15:41 2020
ExecutablePath: /usr/bin/gnome-control-center
InstallationDate: Installed on 2020-10-26 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Florian Schwarz (f.schwarz) wrote :
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

This kind of looks like bug 1866194, but you also appear to have the fix for that installed. Regardless, please try:

  cd ~/.config
  rm -rf pulse

and then reboot.

Changed in gnome-control-center (Ubuntu):
status: New → Incomplete
Revision history for this message
Florian Schwarz (f.schwarz) wrote :

OK, so deletion of pulse config helped. First deletion only temporarly and the weird behavior came back after some switching. But after the second one it seems to be permanently fixed and I can't reproduce the faulty behavior.

So I assume it can be seen as fixed?!

If it happens again and is reproducible, I'll report again.

Thank you for your help!

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

No problem. If there are no more comments after 60 days then the bug will close automatically.

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for gnome-control-center (Ubuntu) because there has been no activity for 60 days.]

Changed in gnome-control-center (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.