Issued:

2012-02-21

Updated:

2012-02-21

RHBA-2012:0147 - spice-client bug fix update

Synopsis

spice-client bug fix update

Type/Severity

Bug Fix Advisory

Topic

An updated spice-client package that fixes one bug is now available for Red Hat Enterprise Linux 5.

Description

The spice-client package provides the Simple Protocol for Independent Computing Environments (SPICE) client application. SPICE is a remote display protocol designed for virtual environments. SPICE users can access a virtualized desktop or server from the local system or any system with network access to the server. SPICE is used in Red Hat Enterprise Linux for viewing virtualized guests running on the KVM hypervisor or on Red Hat Enterprise Virtualization Hypervisors.

This update fixes the following bug:

• The SPICE client did not correctly handle an exception which was raised when trying to connect to a guest operating system with no running SPICE agent. Consequently, the SPICE client application terminated unexpectedly after the 30-second timeout. With this update, the SPICE client correctly handles this situation and successfully connects to the guest system without unnecessary waiting. (BZ#790894)

All users of spice-client are advised to upgrade to this updated package, which fixes this bug.

Solution

Before applying this update, make sure all previously-released errata relevant to your system have been applied.

This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at This content is not included.https://access.redhat.com/kb/docs/DOC-11259

Affected Products

Updated Packages

• spice-client-0.8.1-6.el5_8.2.src.rpm
• spice-client-0.8.1-6.el5_8.2.i686.rpm
• spice-client-debuginfo-0.8.1-6.el5_8.2.x86_64.rpm
• spice-client-debuginfo-0.8.1-6.el5_8.2.i686.rpm
• spice-client-0.8.1-6.el5_8.2.x86_64.rpm

Fixes

• This content is not included.BZ - 790894

CVEs

(none)

References

(none)

Additional information

• The Red Hat security contact is This content is not included.secalert@redhat.com. More contact details at https://access.redhat.com/security/team/contact/.
• Offline Security Data data is available for integration with other systems. See Offline Security Data API to get started.