Originally reported wrongly, I've reproduced this problem.
No idea how to fix it.
We hit the assert in spice-server that was removed.
((null):3743): SpiceWorker-CRITICAL **: red_worker.c:9306:red_create_surface: Untested path stride >= 0
Alon any idea how we can avoid that?
to reproduce install F19 in a RHEL6.4 VM under not spice, then switch to spice.
The problem is I don't know of anything we can trigger to avoid using stride >= 0 cases
(In reply to Dave Airlie from comment #1)
> to reproduce install F19 in a RHEL6.4 VM under not spice, then switch to
> spice.
>
> The problem is I don't know of anything we can trigger to avoid using stride
> >= 0 cases
AFAIK there is no way to find out if the assert is there or not, so indeed there is nothing the guest can do to avoid it.
I believe this is best fixed on the RHEL side as the assert actually is a spice-server bug there. The RHEL side of this is being tracked in bug 952666