Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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 680763

Summary: x11 spicec hangs on exit handler at XLockDisplay
Product: Red Hat Enterprise Linux 6 Reporter: Alon Levy <alevy>
Component: spice-clientAssignee: Uri Lublin <uril>
Status: CLOSED ERRATA QA Contact: Desktop QE <desktop-qa-list>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.1CC: alevy, bsanford, dblechte, djasa, lkocman, mhasko, mkenneth, tcapek
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: spice-client-0.8.0-1.el6 Doc Type: Bug Fix
Doc Text:
Sometimes, spicec became stuck when exiting from full-screen mode if it received an asynchronous X Window system error. With this update, spicec now correctly calls the appropriate "_exit()" function in this rare circumstance so that spicec does not become stuck if this situation occurs.
Story Points: ---
Clone Of: 679018 Environment:
Last Closed: 2011-05-19 13:15:32 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 679018    
Bug Blocks:    

Comment 2 Hans de Goede 2011-03-01 17:42:07 UTC
We have a simple fix for the hanging when exiting from fullscreen due to an X-error, which is going into the upstream 0.8.0 release, to which we will rebase shortly. Adding devel ack.

Note to qa, qa will be sanity only as actually getting an X-error is not reproducable easily (it should
never happen).

Comment 3 Hans de Goede 2011-03-02 16:28:06 UTC
A build containing a fix for this has been done, moving to modified.

Comment 13 Tomas Capek 2011-05-17 11:27:59 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:
Sometimes, spicec became stuck when exiting from full-screen mode if it received an asynchronous X Window system error. With this update, spicec now correctly calls the         appropriate "_exit()" function in this rare circumstance so that spicec does not become stuck if this situation occurs.

Comment 14 errata-xmlrpc 2011-05-19 13:15:32 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