Orphaned X11 Windows

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Have 2+ OWL clients logged in
2. Have 1+ X11 program running (e.g. Firefox, Open Office Calc, etc.)

What is the expected output? What do you see instead?
Expect that the X11 screen will be in-sync on all client sessions.
One client X11's screen will freeze (orphan) at some point and will no longer 
receive any screen updates or the client be able to take control.
Rest of clients seem unaffected.
Logging client out/in will cure the issue.
Sometimes issue returns during a session.  If it does it can affect any client, 
not just the original one affected.
This happens on locally and internet connected clients.

What version of the product are you using? On what operating system?
OWL 2012-02 release, JAVA 64-bit 1.7.2, Centos 6.2 64-bit.
Quad CPU, 4GB memory, dedicated OWL server.

Please provide any additional information below.
It never happens to a client that has control over a window, only to clients in 
viewing mode.
We run all X11 programs from wrapper scripts, which create a new temporary home 
directory and environment variables specifically for that X11 session.

Original issue reported on code.google.com by support%...@gtempaccount.com on 16 May 2012 at 8:52

[GoogleCodeExporter]

Please add this to the list of issues to be addressed in the next release.

Original comment by bernho...@gmail.com on 18 May 2012 at 7:46

• Added labels: Priority-High, Component-AppSharing
• Removed labels: Priority-Medium

[GoogleCodeExporter]

Please provide client error reports and corresponding Shared Application Server 
logs. We use X11 apps every week during Wonderland Wednesday and do not see 
this issue.

Original comment by jonathan...@gmail.com on 31 May 2012 at 5:07

[GoogleCodeExporter]

Original comment by pympno...@gmail.com on 19 Sep 2012 at 5:11

• Added labels: Priority-Medium
• Removed labels: Priority-High