Bug 2018784 - No audio output device after unplugging HDMI cable
Summary: No audio output device after unplugging HDMI cable
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: pipewire
Version: 35
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Wim Taymans
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-10-31 07:48 UTC by Peter
Modified: 2022-12-13 15:44 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-12-13 15:44:02 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Peter 2021-10-31 07:48:24 UTC
Description of problem:

First, plugging an HDMI cable does not auto-switch the Output Device and it has to be switched manually every time.

Second, in Gnome Settings -> Sound -> Output Device the drop-down appears as blank after unplugging the HDMI cable. At this point there is no sound at all. However I am able to select the builtin speakers if I click on the drop-down window and the sound comes back on.

Version-Release number of selected component (if applicable): 0.3.38


How reproducible: 100%


Steps to Reproduce:

1. Plug in an HDMI cable and manually switch sound output to the new device
2. Unplug cable
3. Go to settings and check Output Devices

Actual results:

Output devices are not switched automatically and unplugging the HDMI cable results in sounds loss.

Expected results:

Devices are switched automatically as in Fedora 34. Disconnecting the HDMI device does not result in a sound loss.

Additional info:

Not the same as https://bugzilla.redhat.com/show_bug.cgi?id=2001279

Just tested and this is not reproducible with a bluetooth speaker although it doesn't auto-switch to bluetooth speaker exactly after reproducing the bug and the small icon (for headset) is missing as well in the drop-down window.

Comment 1 flavonol 2021-11-16 05:27:51 UTC
I suspect I am experiencing the same bug.

When I boot my desktop computer and open GNOME Sound Settings, the output device name is blank. No change in audio device happens automatically regardless of what is being plugged in or unplugged.

Version-Release number of selected component (if applicable): 0.3.40

How reproducible: 100%

Steps to Reproduce:

1. See the steps provided by @p.bozukov.

Comment 2 flavonol 2021-11-16 05:29:45 UTC
(In reply to flavonol from comment #1)
> I suspect I am experiencing the same bug.
> 
> When I boot my desktop computer and open GNOME Sound Settings, the output
> device name is blank. No change in audio device happens automatically
> regardless of what is being plugged in or unplugged.
> 
> Version-Release number of selected component (if applicable): 0.3.40
> 
> How reproducible: 100%
> 
> Steps to Reproduce:
> 
> 1. See the steps provided by @p.bozukov.


I submitted this comment before it was complete by accident. I apologize for the mistake.

The steps can be reproduced using headphones, plugged into either line out or the headphone jack.

Comment 3 smaug 2022-03-30 06:30:03 UTC
I can reproduce the same set of behaviors as described by p.bozukov with a DisplayPort Audio Output device

Comment 4 Peter 2022-05-28 16:16:05 UTC
This bug is resolved in Fedora 36. Probably was fixed with one of the updates in F35. Please close or let me know with what status to close.

Comment 5 Sergei Petrosian 2022-09-26 14:02:00 UTC
Hi @p.bozukov

I am running F36, I confirm that I am latest RPM versions, and this bug still persist. Can you help me troubleshoot it?

Thank you

Comment 6 Peter 2022-10-01 15:06:19 UTC
Hi @spetrosi 

Sorry, I haven't done anything besides upgrading to F36. I don't experience this bug anymore.

Comment 7 Sergei Petrosian 2022-10-06 08:34:45 UTC
Hm I think I confused between two different things. The first scenario that works:
1. Select built-in speakers as an audio output device
2. Plug-in headphones
3. Audio output device switches to headphones successfully, and speakers do not sound anymore, that is expected

And the second scenario that I had in mind when writing my first comment:
1. Select some external speakers as an audio output device, in my case ThinkPad dock station's audio output mini jack with external speakers connected to it
2. Plug-in headphones into the laptop's built-in mini jack
3. Audio output device does not switch to headphones. I guess that is expected behavior too, but I think it would be nice if I can control this.

Comment 8 Ben Cotton 2022-11-29 17:12:15 UTC
This message is a reminder that Fedora Linux 35 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 35 on 2022-12-13.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '35'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 35 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 9 Ben Cotton 2022-12-13 15:44:02 UTC
Fedora Linux 35 entered end-of-life (EOL) status on 2022-12-13.

Fedora Linux 35 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.