Description of problem: mumble cannot be used in Push To Talk mode in wayland when the keyboard focus is switched away from the mumble window. When running under X11 mumble's Push-To-Talk button works regardless of the current keyboard focus. This is a fundamental feature of mumble since its primary use-case is to provide voice communication to people playing games (i.e. with keyboard focus applied to the game). I know this is somewhat by design for wayland. Are there any services that mumble can subscribe to allow it to monitor specific keys or shift states? Version-Release number of selected component (if applicable): mumble-1.2.18-1.fc25 (and gnome-shell-3.22.2-2.fc25) How reproducible: Always Steps to Reproduce: 1. Configure mumble in push-to-talk mode 2. Choose a push-to-talk button. I am using AltGr (ISO_Level3_Shift). 3. Connect to a mumble server Actual results: The lips icon turns red when my push-to-talk button is pressed if, and only if, the mumble application has keyboard focus. Expected results: The lips icon should turn red when the push-to-talk button is pressed regardless of which application has keyboard focus.
There is an related issue [0] on the mumble project. That issue does include a proposal for action bindings [1] within wayland. [0]: https://github.com/mumble-voip/mumble/issues/3243 [1]: https://lists.freedesktop.org/archives/wayland-devel/2017-August/034776.html
This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. 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 Fedora 'version' of '25'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 25 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, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 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. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
This is still an issue in Fedora 32. Upstream has added dbus calls to support desktop environments setting their own shortcuts, which is expected to land in version 1.4.0. https://github.com/mumble-voip/mumble/pull/3675 I'm experimenting with 1.3.2 with that patch included, but so far I haven't figured out how to have Gnome run a different command on key release.
https://src.fedoraproject.org/rpms/mumble/pull-request/1
John, please take a look at my pull request.
FEDORA-2020-ca26a3f832 has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2020-ca26a3f832
FEDORA-2020-f869e01557 has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2020-f869e01557
FEDORA-2020-f869e01557 has been pushed to the Fedora 33 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-f869e01557` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-f869e01557 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2020-8372f6bae4 has been pushed to the Fedora 32 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-8372f6bae4` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-8372f6bae4 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2020-ca26a3f832 has been pushed to the Fedora 31 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-ca26a3f832` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-ca26a3f832 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2020-f869e01557 has been pushed to the Fedora 33 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2020-ca26a3f832 has been pushed to the Fedora 31 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2020-8372f6bae4 has been pushed to the Fedora 32 stable repository. If problem still persists, please make note of it in this bug report.