RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 977998 - freezed display when jpeg compression enabled (over WAN)
Summary: freezed display when jpeg compression enabled (over WAN)
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: spice-server
Version: 6.4
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: rc
: ---
Assignee: Yonit Halperin
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-06-25 18:46 UTC by Yonit Halperin
Modified: 2017-02-06 15:16 UTC (History)
9 users (show)

Fixed In Version: spice-server-0.12.4-1.el6
Doc Type: Bug Fix
Doc Text:
Cause (from comment #0): When running spice over a limited bandwidth (with jpeg compression enabled), it was possible for a wrong flagto be set when sending bitmaps that were intended to replace lossy bitmaps inside the cache. Consequence (from comment #0): This can result in an endless wait at the client display channel. The display freeze, and wouldn't unfreeze till the client disconnects and reconnects. Fix: In such a case send the correct flags Result: That freeze does not happen.
Clone Of:
Environment:
Last Closed: 2013-11-21 07:42:07 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
fix (1.64 KB, patch)
2013-06-25 18:49 UTC, Yonit Halperin 		no flags Details | Diff
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2013:1571 0 normal SHIPPED_LIVE spice-server bug fix and enhancement update 2013-11-20 21:39:57 UTC

Description Yonit Halperin 2013-06-25 18:46:00 UTC 
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.
Comment 1 Yonit Halperin 2013-06-25 18:49:05 UTC 
Created attachment 765259 [details]
fix
Comment 2 Yonit Halperin 2013-06-25 18:53:31 UTC 
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).
Comment 3 Paul Vine 2013-07-12 11:45:54 UTC 
We need details of component versions and config to try to reproduce before we can ack.
Comment 4 Yonit Halperin 2013-07-12 12:21:33 UTC 
(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.
Comment 5 David Jaša 2013-07-12 14:19:12 UTC 
(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?
Comment 6 Yonit Halperin 2013-07-12 14:41:02 UTC 
(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.
Comment 7 David Jaša 2013-07-18 16:48:13 UTC 
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.
Comment 10 errata-xmlrpc 2013-11-21 07:42:07 UTC 
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
Note You need to log in before you can comment on or make changes to this bug.