summary refs log tree commit diff stats
path: root/results/classifier/gemma3:12b/peripherals/1868617
diff options
context:
space:
mode:
Diffstat (limited to 'results/classifier/gemma3:12b/peripherals/1868617')
-rw-r--r--results/classifier/gemma3:12b/peripherals/186861716
1 files changed, 16 insertions, 0 deletions
diff --git a/results/classifier/gemma3:12b/peripherals/1868617 b/results/classifier/gemma3:12b/peripherals/1868617
new file mode 100644
index 00000000..a6251231
--- /dev/null
+++ b/results/classifier/gemma3:12b/peripherals/1868617
@@ -0,0 +1,16 @@
+
+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.
\ No newline at end of file