Red Hat Bugzilla – Bug 670238
jpeg messages encoding is transfered as 4 and not 1, breaking client
Last modified: 2014-08-04 18:08:30 EDT
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):
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
client aborts with ASSERT
A new spice-client-0.7.2-1.el6 fixing this has been build, moving to modified.
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.
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.
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.