$ spicy --uri spice://127.0.0.1:5900
GSpice-Message: main channel: opened
GSpice-Message: main channel: closed
Yes, it looks like spicy can handle the display when spicec fails with this error message.
I've found some additional information on how to replicate this problem. It seems this is triggered if you have two host displays of different resolutions mirrored, or partially overlapping.
$ xrandr -q
...
LVDS-0 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 193mm
1920x1080 60.0*+ 50.0
...
DP-2 connected 1440x900+0+0 (normal left inverted right x axis y axis) 410mm x 256mm
1440x900 59.9*+ 75.0 59.9
1280x1024 75.0 60.0
1024x768 75.0 70.1 60.0
800x600 75.0 72.2 60.3 56.2
640x480 75.0 72.8 59.9
If the host displays do not overlap at all, spicec works.
There doesn't appear to be anything in the domain log file for these display connection attempts.
$ spicec -h 127.0.0.1 -p 5900
Error: unhandled exception: unsupported partial overlap
$ spicy --uri spice:/ /127.0. 0.1:5900
GSpice-Message: main channel: opened
GSpice-Message: main channel: closed
Yes, it looks like spicy can handle the display when spicec fails with this error message.
I've found some additional information on how to replicate this problem. It seems this is triggered if you have two host displays of different resolutions mirrored, or partially overlapping.
$ xrandr -q
...
LVDS-0 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 193mm
1920x1080 60.0*+ 50.0
...
DP-2 connected 1440x900+0+0 (normal left inverted right x axis y axis) 410mm x 256mm
1440x900 59.9*+ 75.0 59.9
1280x1024 75.0 60.0
1024x768 75.0 70.1 60.0
800x600 75.0 72.2 60.3 56.2
640x480 75.0 72.8 59.9
If the host displays do not overlap at all, spicec works.
There doesn't appear to be anything in the domain log file for these display connection attempts.