Bug 2182384 - Cannot change/select audio output between two display ports, audio always stay with one port
Summary: Cannot change/select audio output between two display ports, audio always sta...
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: pipewire
Version: 39
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: Wim Taymans
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-03-28 13:59 UTC by Mohd Yusuf
Modified: 2023-08-16 08:06 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: ---
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Mohd Yusuf 2023-03-28 13:59:11 UTC
Description of problem:
I cannot select audio to different display port. I have two exact model of monitor attached to two display ports. Audio always initialized to display port 0 on reboot and will not change to other port even if I set in the Settings > Sound to display port 2.

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

How reproducible:
Always

Steps to Reproduce:
1. Connect 2 display ports (preferably both same model) that support audio out.
2. Reboot, test audio on port 0, change "Settings > Sound" to secondary port and test again.
3. No sound will go to secondary port.

Actual results:
No sound will go to secondary port.

Expected results:
Sound will change to secondary port.

Additional info:
If I disconnect the secondary monitor, the audio will resort to secondary monitor and stays there too. I cannot go back to primary monitor unless I reboot.

Hardware:
Nvidia RTX 4090
Lenovo T32p-20 (2x)

Comment 1 Mohd Yusuf 2023-03-28 14:00:20 UTC
Adding NVidia proprietary driver info: version 530.41.03

Comment 2 Fedora Release Engineering 2023-08-16 08:06:59 UTC
This bug appears to have been reported against 'rawhide' during the Fedora Linux 39 development cycle.
Changing version to 39.


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