Bug 537024
| Summary: | Metacity terminates unexpectedly with BadWindow (invalid Window parameter) | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 5 | Reporter: | RHEL Program Management <pm-rhel> |
| Component: | metacity | Assignee: | Owen Taylor <otaylor> |
| Status: | CLOSED ERRATA | QA Contact: | desktop-bugs <desktop-bugs> |
| Severity: | urgent | Docs Contact: | |
| Priority: | urgent | ||
| Version: | 5.4 | CC: | pm-eus, smaitra, tao |
| Target Milestone: | rc | Keywords: | Patch, ZStream |
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2009-11-26 08:11:13 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: | 523777 | ||
| Bug Blocks: | |||
|
Description
RHEL Program Management
2009-11-12 09:03:54 UTC
Built as metacity-2.16.0-12.el5_4.1 For Testing this bug, Can you please make me a bit more clear over the following test steps to reproduce and both expected and actual Results : Steps to Reproduce: 1. Run a remote application (steps to follow or commands to run this) 2. Open a transient (like "Find" in gedit for example) 3. Close the main window (Close gedit window in this case, right?) Actual results: metacity dies with Unexpected X error BadWindow (invalid Window parameter) and gets restarted by the session manager. Expected results: metacity survives closing a window Actually, Suppose, I am running a system with vnc, and open gedit there and open Find Window and then Close Gedit window (main window). Is this the way to reproduce this bug? OR any other way to run a remote application? Please inform. And one more details to know, suppose if I am running gedit within vnc system, then what does actually metacity do? Whats its involvement when I attempt to close main window, keeping the child window open? I need some more elaborate test steps, OR better in depth understanding of this bug really! Please inform vnc is not a remote system for the purposes of this bug report. All operations within the vnc X server are run locally to the test machine, and the entire display is sent as a unit to your system. As described in "how to test", you need to run 'ssh -Y' from the test system to another system, and the run an X application (e.g., gedit) from within the ssh session. Tested this bug with old (metacity-2.16.0-12) and fixed (metacity-2.16.0-12.el5_4.1) version of metacity. Bug reproduced in the old version and Fixed in the proposed version resolving the X error. Tested. Result : PASS Version of the component Tested : metacity-2.16.0-12.el5_4.1 OS :RHEL-5.4z Test Observation : Metacity, with this proposed package version, survives, closing the window successfully. 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-2009-1610.html |