GNOME Bugzilla – Bug 778929
Attempting to edit a non-custom keyboard shortcut freezes the Settings window
Last modified: 2018-02-13 15:53:59 UTC
When I try to edit a keyboard shortcut in Settings->Keyboard (by either clicking on an entry, or picking one with the keyboard & pressing Enter), the entire Settings window becomes unresponsive to all mouse & keyboard input, with the exception of pressing Esc, which brings it back to normal. The popup window that should appear to prompt me to press the new keyboard shortcut I want doesn't appear. It's not as if that popup is invisible, because even if I press the keyboard shortcut I want to set (as if the popup were there), nothing happens. Also, it's not as if the Settings window is completely frozen, either, because I can make the Settings window show a different screen by searching for one in the Overview. For example, while it's locked-out, I can make the Settings window show the Bluetooth screen by pressing Super, typing "Bluetooth" in the search box, and selecting it. The window will still be unresponsive to input until I press Esc, though. When the window is locked-out, I can't even move or resize it, with either the mouse or keyboard. All I can do is move it to different workspaces. The only way to close the window when it's locked-out is to press "Close" in the Application Menu. Clicking the "X" in the top-right corner doesn't work, and neither does Alt+F4. By the way, even when locked-out, the Setting window's Application Menu is fully-functional, as are all of its commands (Keyboard Shortcuts, Help, and Quit). This problem doesn't happen when either editing or adding a Custom Shortcut, or when restoring any command to its default shortcut (by clicking the "X" arrow to right of it). So right now, the only way I can edit keyboard shortcuts is via the dconf editor or gsettings. Maybe related to Case 760301.
Which version of gnome-control-center, gnome-shell and mutter is that with? Are you using Wayland or Xorg?
gnome-control-center: 3.22.1 gnome-shell: 3.22.2 mutter: 3.22.2 I'm on 64-bit Fedora 25 with Xorg. I thought that Wayland was supposed to be the default for F25 sessions, but my sessions have always been Xorg by default without me having explicitly chosen it. Maybe that's because I'm using Nvidia's proprietary Xorg graphics driver. (I have to use it because my graphics card is unsupported by nouveau.)
I should clarify that when I log in, whether I choose a "Gnome" or "Gnome on Xorg" session, loginctl always reports my sessions' Type as "x11". This bug happens regardless of which choice I make. However, the bug goes away if I log out & log back in, but I haven't tried this enough times to be sure that it works consistently. Also, this may be a duplicate of Case 777309. It's marked as a GOA bug, but it looks like it's about the exact same issue as this case. Feel free to mark one of these cases as a duplicate of the other.
I uninstalled the Nvidia graphics driver to troubleshoot another (non-Gnome) problem I've been having (it turns out nouveau supports my graphics card after all), and the keyboard config issue still happens. This means the Nvidia driver isn't to blame for this issue. Maybe that's useful for you to know.
Is this still happening with GNOME 3.24?
Sorry for not having replied to your question for so long. I think the problem still happened in 3.24, but I can't get it to reproduce at the moment in 3.26 on either Xorg or Wayland, and I haven't ran into the problem again for a long time. Since no one else has piped in on this problem, chances are it's been fixed. Since bug 777309 looks like the same issue as this bug, it might be fixed as well.
Thanks for the heads up, I'll close it as a duplicate of the other bug. *** This bug has been marked as a duplicate of bug 777309 ***