Bug 1948091 - Can not change profile on output device while in use (P50)
Summary: Can not change profile on output device while in use (P50)
Alias: None
Product: Fedora
Classification: Fedora
Component: pipewire
Version: 34
Hardware: x86_64
OS: Unspecified
Target Milestone: ---
Assignee: Wim Taymans
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2021-04-10 01:09 UTC by Bohdan Milar
Modified: 2022-06-10 07:54 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2022-06-08 01:08:50 UTC
Type: Bug

Attachments (Terms of Use)

Description Bohdan Milar 2021-04-10 01:09:29 UTC
Description of problem:
ThinkPad P50 has built-in speakers (via Intel 100 Series/C230 Series Chipset Family HD Audio Controller), an HDMI port and a miniDP (both via NVIDIA GM107 High Definition Audio Controller [GeForce 940MX]).

When I plug 1 screen with speakers to HDMI (or miniDP), I can switch sound output (using pavucontrol or Gnome Control Center) without problem. The NVIDIA output has only "HDMI 4" profile active (others are marked as unplugged) and it works.

When I connect 2 external displays (HDMI + miniDP, both with speakers), there are 2 active profiles ("HDMI 4" for the first screen and "HDMI 5" for the later connected screen). When I switch to NVIDIA, "HDMI 4" is selected and sound comes from the first screen. When I try to switch to "HDMI 5" (pavucontrol - Configuration tab), sound is redirected to built-in speakers.

I found a workaround (for Pavucontrol) - when I switch the output to built-in, then switch profile of NVIDIA to "HDMI 5" and then the output to NVIDIA, sound is routed to the second screen.

And it is even more complicated: Once the "HDMI 5" is selected and working, I can freely switch between "HDMI 4" and "HDMI 5". But after I switch back to built-in and then back to NVIDIA with "HDMI 4" profile selected, the problem is back.

Similar problem occurs in Gnome Control Center, but I have not found a workaround there.

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

How reproducible:

Steps to Reproduce:
1. Have a Lenovo P50 (or other notebook with 2 HDMI/DP outputs?)
2. Log-in to Gnome
3. Start Pavucontrol
4. Connect 2 external screens with speakers (2 active HDMI profiles should appear for the external output in the Configuration tab)
5. Play some long sound
6. Select the external output for palying application (Pavucontrol - Playback) - the first profile should be used (HDMI 4 in my case)
7. Select the second available profile at Pavucontrol - Configuration (HDMI 5 in my case)

Actual results:
Sound is routed (and output switched) to built-in speakers.

Expected results:
Sound should be routed to the second external screen.

Additional info:
Looks similar to bz489049

Comment 1 Ben Cotton 2022-05-12 16:44:23 UTC
This message is a reminder that Fedora Linux 34 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 34 on 2022-06-07.
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 '34'.

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 34 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 2 Ben Cotton 2022-06-08 01:08:50 UTC
Fedora Linux 34 entered end-of-life (EOL) status on 2022-06-07.

Fedora Linux 34 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 please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current 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.