Description of problem: Since my upgrade to Fedora 35 (from 33) the default audio source and sink are not persisted across reboot. So on every boot I must reconfigure my audio devices. Not unusable but quite annoying. I am not the only one to observe this regression. See ML: https://www.spinics.net/linux/fedora/fedora-users/msg510079.html I read through the FAQ and found some closely related (no sound after upgrade, release notes about wireplumber migration) but nothing address how to continue to enjoy persisted sound configuration. I didn't see an existing bug so I decided to file this one. Version-Release number of selected component (if applicable): Fedora 35 pipewire 0.3.40 wireplumber 0.4.5 xfce4-pulseaudio-plugin 0.4.3 pasystray 0.7.1 How reproducible: Always Steps to Reproduce: Configure a non-default sound source or sink. Reboot. Actual results: The source or sink returns to the default. Expected results: The source or sink should save the user setting so they do not have to reconfigure it every time. Additional info: xfce spin, configuration done using pasystray or xfce4-pulseaudio-plugin
I upgraded a second system from 33 to 35 and suffer the same issue on it - in 33, the sound came up as expected (HDMI audio out to go with the video) every time, and now with 35 it must be reset on every boot away from the built in but unused analog audio out.
This comment was flagged a spam, view the edit history to see the original text if required.
Indeed I am disappointed at how little attention this has gotten. Thank you for the suggestion about using wpctl. I will try to cobble something together, although I love to recommend Fedora to friends and family - "it works great out of the box!" but usability problems like this really hurt the experience for mere mortals. And it used to work just fine!
My first attempt to write a startup script failed: apparently the ID that pipewire assigns to each audio device is not stable (last boot it was 54, this boot 55...)
I'm not clear as to why the (rather helpful) information from l88629 above was hidden as spam. Regardless, I still don't have a satisfying solution scripting on my own (it is surprisingly tricky when you end up with multiple similar named devices), and this is something that really should be handled by the base system (and was in the past!)
PA does also not honor the default desired default device: $ pactl set-default-sink alsa_output.pci-0000_0a_00.4.analog-stereo $ pactl get-default-sink alsa_output.pci-0000_04_00.1.hdmi-stereo-extra1 $ rpm -qf $(which pactl) pulseaudio-utils-15.0-2.fc35.x86_64
Bugreport #2138857 maybe helpfull to solve this.
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.
This remains a problem in Fedora 36. I'll test Fedora 37 as soon as I can upgrade (waiting on zfs)
@Steven: You are the reporter, change the bug version to 36 or 37(if verified there)
I tried to do that, but it is not clear that I am able to in Bugzilla. I can update Status, Alias, Product, Component, Severity, and Tags. But I do not think I can update the affected version. I am sorry if I am missing something obvious. PS, thank you for the additional related ticket link. I tried the workaround there (deleting possibly corrupted pipewire state) but it did not fix the audio configuration being lost on reboot.
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.
Aha, I had to show advanced fields, which was not suggested until the ticket was closed. I tested against 37 and this problem still exists, so I am attempting to reopen it against 37.
ATM not fixed in F36 either. Still not working.
This message is a reminder that Fedora Linux 37 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 37 on 2023-12-05. 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 '37'. 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. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 37 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 37 entered end-of-life (EOL) status on None. Fedora Linux 37 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.