Dear Maintainer,

I use remote-viewer from virt-viewer to run a VM with two monitors, while
accessing them as two windows. My PC runs Debian Stable. The VM runs
Sid and IceWM (without a login program like SDDM).

Here is the command I use to launch the VM:

qemu-system-x86_64 -smp cores=2,threads=1,sockets=1 -enable-kvm -m 4G
 -netdev user,id=name -device virtio-net-pci,netdev=name -vga none
 -device qxl-vga,vgamem_mb=64,ram_size_mb=256,vram_size_mb=128,max_outputs=2
 -display none -spice unix=on,addr=/tmp/spice.sock,disable-ticketing=on
 -chardev spicevmc,id=charchannel0,name=vdagent
 -device virtio-serial-pci,id=virtio-serial0 -device virtserialport,bus=virtio
 -serial0.0,nr=1,chardev=charchannel0,id=channel0,name=com.redhat.spice.0
 debian-sid-gui-amd64.qcow2

The issue is that, under specific circumstances, when I click on the second
monitor, the click happens on the first monitor. However, I am able to _see_
the whole X desktop composed of the two emulated monitors. Using xeyes,
I found out that the X server thinks that the cursor is always on the
first monitor.
The first monitor behaves normally; only the second one is problematic.

Here are the steps to reproduce:
1. Start the VM and connect to it using remote-viewer.
2. When ready, log into a virtual console and run startx.
3. Open xterm. Run spice-vdagent.
4. Using the remote-viewer GUI, open the second monitor. (You won't see any
   contents yet, only a message saying "Waiting for display 2...".)
5. Log out of IceWM. (The content of the console will appear on the
   second monitor.)
6. Run startx.

Now, the X session will suffer from the issue I described. Running
spice-vdagent again in
xterm will fix the issue.

Interestingly, a similar issue affects SDDM after logging out
from a Plasma session.

Regards,
Samuel Plavec