Red Hat Bugzilla – Bug 977998
freezed display when jpeg compression enabled (over WAN)
Last modified: 2017-02-06 10:16:56 EST
Description of problem: When you run spice over a limited bandwidth, the display might freeze, and wouldn't unfreeze till the client disconnects and reconnects. Easily reproduced when running with rhel7 guest over WAN (try entering wrong password in the login screen). The origin of the problem is a wrong flag that was set when sending bitmaps that were intended to replace lossy bitmaps inside the cache. The bug resulted in an endless wait at the client display channel.
Created attachment 765259 [details] fix
I think that this bug can be the same as the bug that Marian hit in bug 809187 comment #9. But its not the same as the original report in 809187 (since it wasn't over WAN).
We need details of component versions and config to try to reproduce before we can ack.
(In reply to Paul Vine from comment #3) > We need details of component versions and config to try to reproduce before > we can ack. It doesn't matter. The component is any spice-server of rhel6.4, rhel6.3, or even previous ones. And the network environment should be a low bandwidth one.
(In reply to Yonit Halperin from comment #0) > Easily reproduced when running with rhel7 guest over WAN (try entering wrong > password in the login screen). > Hi Yonit, I've seen such freeze in this even over LAN (that was F19 host & guest, client was connected to the same switch). Is it possible that the cause is the same?
(In reply to David Jaša from comment #5) > (In reply to Yonit Halperin from comment #0) > > Easily reproduced when running with rhel7 guest over WAN (try entering wrong > > password in the login screen). > > > > Hi Yonit, I've seen such freeze in this even over LAN (that was F19 host & > guest, client was connected to the same switch). Is it possible that the > cause is the same? Hi, no, it is not the same one, I think I mentioned the bug you are referring to in comment #2.
Reproduced according to steps, so qa_ack+. The client doesn't freeze entirely though. When another connects, you can see in the input what was typed after the display freezed, which is consistent with comment 0: > The bug resulted in an endless wait at the client display channel.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2013-1571.html