Description of problem: I have https://us.ankerwork.com/products/a3305?ref=navimenu that I use extensively for conference calls, lsusb shows it as "Bus 001 Device 003: ID 291a:3305 Anker Anker PowerConf S500". Since moving to a new desktop that is running Fedora 37 from my old one using Fedora 36, the mute and unmute behaviour has changed. In Fedora 36, hitting the mute button was local to the speakerphone only, and if I used a tool such as pavucontrol to look at the devices, the microphone was not muted. On the new computer with the same device connected via USB the same as the old computer, when I hit the mute button, it toggles the mute status of the microphone device on the host. unmuting does not change the mute status, I have to mute again to toggle the status on the host to unmuted, followed by a 4th touch on the mute button to unmute the speakerphone again. I end up having to hit the microphone button four times rather than two to mute and unmute. Version-Release number of selected component (if applicable): pipewire-0.3.59-2.fc37.aarch64 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
an extra data point here, this behaviour only happens when running gnome on Wayland, if running on Xorg the device does not get muted and unmuted, I wonder if there is an incoming keypress that is being ignored when unmuting
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.