Description of problem: Every time I connect to a virtual machine, I get the prompt in the title. This prompt takes over the full screen and blocks all other applications. Working with lots of virtual machines, this behaviour is quite interruptive. I appear to not be alone, given bugs like #1528653. Is it possible to set to always allow (or deny) and not prompt anymore? Using wayland, in case it matters. Version-Release number of selected component (if applicable): gnome-desktop3.x86_64 3.30.2-1.fc29 gnome-session.x86_64 3.30.1-2.fc29 gnome-session-wayland-session.x86_64 3.30.1-2.fc29 gnome-session-xsession.x86_64 3.30.1-2.fc29 gnome-settings-daemon.x86_64 3.30.2-1.fc29 gnome-shell.x86_64 3.30.2-1.fc29 libvirt.x86_64 4.7.0-1.fc29 libvirt-admin.x86_64 4.7.0-1.fc29 virt-manager.noarch 1.6.0-1.3.git3bc7ff24c.fc29 How reproducible: 100% Steps to Reproduce: 1. Use virtual machine manager to connect to a virtual machine 2. Get prompt without ability to suppress future prompts 3. Actual results: Expected results: Additional info:
I suspect this is either a gtk or wayland thing, it's not something coming explicitly from virt-manager code. I haven't really looked into it though: I'm still on X but I've seen it when testing wayland.
Yes this is a newish thing under Wayland. Historically there was no grab feature under Wayland at all. I believe what happens is that GTK now requests the keyboard grab from GNOME shell (which is the wayland compositor/server), and that in turns pops up the confirmation dialog. I agree that this is insanely annoying because it happens every time, even worse with virt-viewer than with virt-manager. There needs to be some kind of option "Don't ask me again for this application". Note I say application, not process, because users will repeatedly launch virt-viewer processes and we don't want to be prompted every time.
Adding Olivier since I believe he implemented the keyboard grab stuff for Wayland / GNOME Shell & would know what, if anything, we can do to address this & what component is responsible.
That's gnome-shell
This is still an issue in Fedora 30. Is there any way anyone has found to stop this behaviour?
Olivier submitted this https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/382 Which is supposed to add a 'do not ask again' or similar option to the pop up, and it should be in f30 gnome-shell 3.32. I haven't tried to reproduce it though
Alternatively, you could try this GNOME Shell extension: https://extensions.gnome.org/extension/1619/quiet-shortcuts/
This message is a reminder that Fedora 29 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26. 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 '29'. 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 29 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 29 changed to end-of-life (EOL) status on 2019-11-26. Fedora 29 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.