blob: a6340413e8a38af89908d1238b100f88a26fa5aa (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
|
multiseat: route different spice tablet events to distinct vdagents
docs/multiseat.txt says:
> Note on spice: Spice handles multihead just fine. But it can't do
> multiseat. For tablet events the event source is sent to the spice
> agent. But qemu can't figure it, so it can't do input routing.
> Fixing this needs a new or extended input interface between
> libspice-server and qemu. For keyboard events it is even worse: The
> event source isn't included in the spice protocol, so the wire
> protocol must be extended to support this.
I'm not sure exactly what "can't figure it" means, but it looks to me like qemu can't route incoming tablet events from a spice client to distinct vdagent channels.
I think this part of the process can be fixed within qemu. I've reported https://gitlab.freedesktop.org/spice/spice-gtk/issues/121 to address the issues with the keyboard interface at the protocol level.
|