Bug 670238 - jpeg messages encoding is transfered as 4 and not 1, breaking client
Summary: jpeg messages encoding is transfered as 4 and not 1, breaking client
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: spice-client
Version: 6.1
Hardware: Unspecified
OS: Unspecified
low
medium
Target Milestone: rc
: ---
Assignee: Uri Lublin
QA Contact: Hans de Goede
URL:
Whiteboard:
Depends On:
Blocks: 671383
TreeView+ depends on / blocked
 
Reported: 2011-01-17 16:24 UTC by Alon Levy
Modified: 2014-08-04 22:08 UTC (History)
5 users (show)

Fixed In Version: spice-client-0.7.2-1.el6
Doc Type: Bug Fix
Doc Text:
When spice-client was set to use JPEG compression for images, the client sometimes terminated unexpectedly. This bug has been fixed and the spice-client now handles JPEG images properly.
Clone Of:
Environment:
Last Closed: 2011-05-19 13:15:21 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2011:0583 0 normal SHIPPED_LIVE libcacard and spice-client bug and enhancement update 2011-05-19 09:37:34 UTC

Description Alon Levy 2011-01-17 16:24:02 UTC
Description of problem:
The header field sent in jpeg compressed images which specifies upside downness of the image is being inconsistently handled:
 * server sends 4 or 0
 * client ASSERTS it is 1 or 0
Results in client crash.

Upstream fix for the client:
046b9a7 common, canvas_get_jpeg_alpha: let top_down be any value

Patch makes the client handle 0 as 0 and positive as 1

Version-Release number of selected component (if applicable):
0.7.1

How reproducible:
Always

Steps to Reproduce:
1. start guest with jpeg enabled (force it so it doesn't require emulating a wan environment)
2. in windows guest toggling the start menu repeatedly trigers a jpeg image sent
3. watch client crash
  
Actual results:
client aborts with ASSERT

Expected results:
client works

Additional info:

Comment 2 Hans de Goede 2011-01-25 13:52:14 UTC
A new spice-client-0.7.2-1.el6 fixing this has been build, moving to modified.

Comment 5 Tomas Capek 2011-05-17 11:36:28 UTC
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
When spice-client was set to use JPEG compression for images, the client sometimes terminated unexpectedly. This bug has been fixed and the spice-client now handles JPEG images properly.

Comment 6 errata-xmlrpc 2011-05-19 13:15:21 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2011-0583.html


Note You need to log in before you can comment on or make changes to this bug.