Description of problem: When plugging the headphones into headphones port, the volume of the headphones becomes either 74% or 0% (muted). The same happens for the speakers upon unplugging the headphones. Volume levels are neither saved nor restored. It seems that Pipewire is in conflict with Pulseaudio when no pipewire-pulse is installed, however this bug happens even when pulseaudio process is not running (stopped with systemctl --user stop pulseaudio.service pulseaudio.socket). Version-Release number of selected component (if applicable): pipewire.x86_64 0.3.32-1.fc34 pipewire-alsa.x86_64 0.3.32-1.fc34 pipewire-jack-audio-connection-kit.x86_64 0.3.32-1.fc34 pipewire-libs.x86_64 0.3.32-1.fc34 pulseaudio.x86_64 14.2-3.fc34 How reproducible: All the time Steps to Reproduce: 1. Have Pulseaudio along with Pipewire (pipewire+pulseaudio, not pipewire-pulse, default configuration when upgrading Fedora 33→34) 2. Plug in the headphones to the jack 3. Disconnect the headphones Actual results: The volume of headphones is either 74% or muted upon connection, regardless of the previous volume levels. The volume of speakers is either 74% or muted upon headphones disconnection, regardless of the previous volume levels. Expected results: The volume and muted/unmuted state is saved and restored properly. Additional info: I've tried to disable volume restoring modules in pulseaudio, that didn't help. Even stopping pulseaudio process completely, letting pipewire handle everything, triggers this bug. Everything is fine with pipewire-pulse (no real pulseaudio).
Created attachment 1809913 [details] PIPEWIRE_DEBUG=3 and PIPEWIRE_DEBUG=4 logs This is pipewire log running with PIPEWIRE_DEBUG=3, PIPEWIRE_DEBUG=4 and no pulseaudio process running. 1. Pipewire is started 2. Volume is decreased from 75% to 30-40% using alsamixer -c0 3. Headphones are plugged in 4. Volume is decreased from 75% to 30-40% using alsamixer -c0 5. Headphones are unplugged 6. Volume is decreased from 75% to 30-40% using alsamixer -c0
Upstream: https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/1475
Pipewire developer says that installing Pipewire with plugins along with Pulseaudio is not supported, however this is exactly what happens on Fedora 33-34 upgrade. >If you install PulseAudio along with PipeWire you need to disable all audio functionality in PipeWire. Usually this means uninstalling the alsa plugin, pipewire-pulse and jack support. This will remove an with-* files from the session manager config directory and disable all audio. >With that in place, PipeWire doesn't do anything with audio and it can't be a pipewire bug. >I suspect some audio parts are still routed to PipeWire, causing both pulseaudio and PipeWire to mess with the volume. This is not supported.
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.