Description of problem: Pipewire somehow gets the channels confused when it restores the volumes on boot. My configuration has LFE muted: > $ cat .config/pipewire/media-session.d/default-routes > { > "default.route.alsa_card.pci-0000_38_00.1:profile:off": [ ], > "default.route.alsa_card.pci-0000_38_00.1:profile:output:hdmi-stereo": [ ], > "default.route.alsa_card.pci-0000_38_00.1:profile:output:hdmi-surround": [ "hdmi-output-0" ], > "default.route.alsa_card.pci-0000_38_00.1:output:hdmi-output-0": { "mute": false, "volumes": [ 1.000000, 1.000000, 1.000000, 1.000000, 1.000000, 0.000000 ], "channels": [ "FL", "FR", "RL", "RR", "FC", "LFE" ] } > } However on boot it instead RR that is muted. Version-Release number of selected component (if applicable): pipewire-0.3.33-1.fc34.x86_64 How reproducible: 100% Steps to Reproduce: 1. pactl set-sink-volume 41 100% 100% 100% 100% 100% 0% 2. reboot 3. play multichannel audio Actual results: RR is muted. Expected results: LFE is muted. Additional info: Except for the wrong channel being muted, everything else works fine and audio is routed to the correct channel on playback. pipewire also still believes it did the right thing ("pactl list sinks" shows what's configured, not reality).
Side note, alsamixer does not cause default-routes to get updated for some reason. Not sure if that's a bug or not.
FEDORA-2021-667b4bfc51 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-667b4bfc51
FEDORA-2021-667b4bfc51 has been pushed to the Fedora 34 stable repository. If problem still persists, please make note of it in this bug report.
I'm afraid I have to report that after an upgrade to pipewire-0.3.33-3.fc34.x86_64 and a reboot the problem still remains. :/
The problem is fortunately symmetrical, so I can work around the issue by muting RR instead and and rebooting: > $ pactl set-sink-volume 41 100% 100% 100% 0% 100% 100% > $ sudo reboot This works well enough for me as I don't need to dynamically change the volume once the machine is up and running.
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.
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.