Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • gnome-shell gnome-shell
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 2,052
    • Issues 2,052
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 147
    • Merge requests 147
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GNOMEGNOME
  • gnome-shellgnome-shell
  • Issues
  • #6066
Closed
Open
Issue created Nov 08, 2022 by Adam Williamson@adamwContributor

Can't switch layouts with super+space when password entry active in GDM with GNOME Shell 43.1

With gnome-shell 43.1 and mutter 43.1 - not sure which caused the problem - switching keyboard layouts with super+space does not work when the password entry box is active in GDM. This works fine with gnome-shell 43.0 and mutter 43.0. This is reproducible at will: just have two or more layouts available in GDM, hit 'enter' to select a user, and - now the password entry box is active - try super+space to switch layouts. It doesn't work. I've tried three cycles of downgrade to 43.0 -> reboot -> it works -> upgrade to 43.1 -> reboot -> it fails.

Layout switching works fine if you hit tab so the password entry box isn't active (though obviously this isn't ideal - it's quite natural to want/need to change the layout with the entry box active), and it works fine after logging in, in all the situations I tested. There may be other affected cases I didn't find (maybe other password entry fields?)

Assignee
Assign to
Time tracking