Just upgraded to Fedora Workstation 37, but virt-manager now no longer passes the Super Key through to the VM. It still works correctly when connecting with virt-viewer albeit virt-viewer does ask about “allow inhibiting shortcuts” (which I do); I seem to remember virt-manager doing this previously, but now no longer does. A clue? How to get virt-manager to see the super key again?
With my Fedora 37, upgrade to latest with “dnf update”, rebooted.
I am having the same issue as yours.
Sounds like one of you should file a bug (if bug report not yet existing).
As of now, after updating F37 with sudo dnf upgrade
. Super Key works (pass to VM Guest instead of to Host)
Sorry, not for me. The host is Silverblue in this case, running gnome-shell 43.3 if that makes any difference. Reading the other bug report #2144172 and following all the links it seems it should be working for me. I think I’ll wait until Fedora 38 is GA and try again.
Please share your ‘rpm-ostree status’ output with us.
I am running Silverblue 38 at the moment before Beta released. Almost update daily. And meta key pass through is not an issue so far.
rpm-ostree status
State: idle
AutomaticUpdates: check; rpm-ostreed-automatic.timer: last run 2h 29min ago
Deployments:
● fedora:fedora/37/x86_64/silverblue
Version: 37.20230320.0 (2023-03-20T00:48:14Z)
BaseCommit: 008ef1f466e75de52c3981399f3eb5244ea730448e13f3ed2a20504e4efbe898
GPGSignature: Valid signature by ACB5EE4E831C74BB7C168D27F55AD3FB5323552A
LayeredPackages: gstreamer1-plugin-openh264 libvirt libvirt-client libvirt-daemon libvirt-daemon-kvm qemu-img
qemu-kvm tilix virt-install virt-manager virt-viewer
fedora:fedora/37/x86_64/silverblue
Version: 37.20230316.0 (2023-03-16T17:47:53Z)
BaseCommit: c1e950ed639c085f19485ab5d458fb778b1f9e05208ef46a0420948dd4b83efc
GPGSignature: Valid signature by ACB5EE4E831C74BB7C168D27F55AD3FB5323552A
LayeredPackages: gstreamer1-plugin-openh264 libvirt libvirt-client libvirt-daemon libvirt-daemon-kvm qemu-img
qemu-kvm tilix virt-install virt-manager virt-viewer
This is my production system, so I’m hesitant to switch to 38 until it’s fully baked. Especially since I’ve already run into issues with the Workstation beta.
I would never recommend switching to a beta release for a system that is required to be 100% all of the time.
Delaying until full release is best, and sometimes even wait another month or so for more issues to be identified and fixed if the system is critical.
I generally agree…but silverblue makes it easy to dip your toe in and then bounce back no harm done if there is a problem. I just don’t have the time right now to even spare the 10 minutes to rollback.