GNOME Bugzilla – Bug 792010
Regression: top bar not keyboard-navigable under Wayland (when numlock is off?)
Last modified: 2021-07-05 14:40:39 UTC
What works: * Super+F10 opens the application menu with the first item focused. Navigation selection *if remaining within the menu* works. * Super+M opens the messages/calendar menu, with the first item focused. Navigation selection *if remaining within the menu* works. What doesn't work: * After selecting a different top bar menu, there is no way to navigate to menu contents. The down arrow doesn't work (it used to). * After using Ctrl+Alt+Tab to focus the top bar, menus can't be opened - none of the down arrow, Space or Enter work. * There is no way of getting into the RHS ("system"?) menu at all via keyboard, since it doesn't have a dedicated shortcut (that I could find). Previously, e.g. Super+M then the right arrow could be used.
The top bar is keyboard navigable here (gnome-shell 3.26.2). Please check whether you have enabled GNOME Shell extensions that may be interfering.
That was the first thing I checked, happens with no extensions enabled ;) Should have mentioned I'm on Wayland - I just tested and the bug's not present under an X session.
Someone please remove NEEDINFO from this.
(In reply to Stephen from comment #0) > What doesn't work: > > * After selecting a different top bar menu, there is no way to navigate to > menu contents. The down arrow doesn't work (it used to). > * After using Ctrl+Alt+Tab to focus the top bar, menus can't be opened - > none of the down arrow, Space or Enter work. > * There is no way of getting into the RHS ("system"?) menu at all via > keyboard, since it doesn't have a dedicated shortcut (that I could find). > Previously, e.g. Super+M then the right arrow could be used. I re-tested those cases in a wayland session, and keyboard navigation works correctly in all of them. So I'll tentatively close the bug, please re-open if you can still reproduce this with more recent versions.
The behaviour is still as described in GNOME Wayland 3.28.2 on four different systems (Fedora 28).
All of what is described in the initial comment 0 works for me in GNOME Wayland 3.28.2 on Fedora 28. Cannot reproduce at all, needs better steps.
After Super+M, then right arrow twice to select RHS menu, you're able to navigate to items on the RHS menu with the down arrow (or any other key)?
(In reply to Stephen from comment #7) > After Super+M, then right arrow twice to select RHS menu, you're able to > navigate to items on the RHS menu with the down arrow (or any other key)? Yes I can, following these steps, with the Down arrow.
OK, there's a wrinkle - it depends on the numlock state. My daily drivers are numpad-less, so doesn't have a numlock to toggle. But I was testing with a full-size keyboard and found that having numlock off causes the behaviour I'm seeing (with the normal arrow keys, not the numpad arrows). Toggling on numlock fixed it for the numpad-less keyboard too. Everywhere else (including in Shell, for example in overview search results, the arrow keys work fine in either state - just not for shell top bar nav as described.
I'm able to reproduce this as well, even on the login screen. As long as Num Lock is on, items in the top bar can't be opened with Enter or the down arrow key.
(Ubuntu 18.10, GS 3.30, GNOME session, Wayland-only) I hit the same bug as Stephen (#0). However (#9) I'm unable to make down arrow work it even with numlock enabled in dconf (Thinkpad T480s, no numpad, no numpad on letters too).
Ok once my T480s connected to a (Dell !) dock where an external keyboard is connected, I confirm (#10) that toggling OFF the numlock allows to navigate with keyboard in top bar.
Could it be the same as https://gitlab.gnome.org/GNOME/gnome-shell/issues/550 ?
Yes !
It can't be the same - this issue has been present since at least last year, and the linked bug is described as a regression caused by a specific commit 3 months ago. It seems that there are two slightly different behaviours being described here - in my case, numlock *off* causes the problem. According to krinkodott22 and thirioux, numlock *on* causes the problem. Maybe it's something to do with an inconsistency of numlock state tracking instead of the actual state?
Please note : on a numpad-less keyboard, changing the dconf numlock key to OFF does not allow to navigate in top bar with down arrow. With an external keyboard (with numpad), disabling numlock through the numlock keyboard key does allow it.
Ok, another tip : I disabled numlock on my external keyboard and after a reboot of my numpad-less laptop not connected to anything, the navigation with down arrow in top bar is available. Jonas please note as a feature request that the left dock navigation should allow the right arrow to show the contextual menu of an app. Did I miss any key here ?
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org. As part of that, we are mass-closing older open tickets in bugzilla.gnome.org which have not seen updates for a longer time (resources are unfortunately quite limited so not every ticket can get handled). If you can still reproduce the situation described in this ticket in a recent and supported software version, then please follow https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines and create a new ticket at https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/ Thank you for your understanding and your help.