What's requested
Per-instance keyboard/mouse isolation — an assigned keyboard or mouse should control only the instance it's assigned to, the way gamepad controllers already do.
Current behavior
Gamepad controllers assign and isolate correctly per instance: DeviceManager assigns hidraw/gamepad devices and gamescope's --evdev routes those gamepad evdev nodes into the per-instance gamescope. Keyboard/mouse evdev devices aren't routed into a per-instance gamescope, so they stay attached to the host compositor and control everything.
Requested change
Route the assigned kb/mouse evdev into that instance's gamescope, analogous to gamepads. This needs care: keyboards/mice are also how the primary session is navigated, so a full grab must avoid locking the user out of the host.
What's requested
Per-instance keyboard/mouse isolation — an assigned keyboard or mouse should control only the instance it's assigned to, the way gamepad controllers already do.
Current behavior
Gamepad controllers assign and isolate correctly per instance:
DeviceManagerassigns hidraw/gamepad devices and gamescope's--evdevroutes those gamepad evdev nodes into the per-instance gamescope. Keyboard/mouse evdev devices aren't routed into a per-instance gamescope, so they stay attached to the host compositor and control everything.Requested change
Route the assigned kb/mouse evdev into that instance's gamescope, analogous to gamepads. This needs care: keyboards/mice are also how the primary session is navigated, so a full grab must avoid locking the user out of the host.