Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • S spice-gtk
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 66
    • Issues 66
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 7
    • Merge requests 7
  • 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
  • spice
  • spice-gtk
  • Issues
  • #143
Closed
Open
Issue created Apr 19, 2021 by Daniel Berrange@berrangeMaintainer

Guest sees multiple caps_lock events when caps_lock is remapped to ctrl on the client

Originally reported against virt-viewer

https://gitlab.com/virt-viewer/virt-viewer/-/issues/29

Running on Fedora 33, with GNOME desktop, launch gnome-tweaks

Under additional keyboard options, Caps lock behaviour, select Caps lock is also ctrl.

Now attempt to interact with a guest, pressing Caps lock.

Since SPICE is forwarding raw scancodes, the guest is still going to see a "Caps lock" scancode of course.

The wierd part is that a press+release on the client results in press+release, then a short delay, then press+release in the guest.

It looks like the remapping of capslock to be a modifier in the client is confusing spice-gtk somewhere, causing it to inject an extra set of input events.

Assignee
Assign to
Time tracking