Update: Citrix on Unix (Solaris)
Okay, my tests with w9wm and with lwm both failed. It appears that no WM actually shows the same wrong behaviour as another one. lwm has big problems with rendering transient windows, e.g. properties boxes from Lotus Notes. Well, it mustn't be lwms fault, actually the Citrix Client tries to do the window placement, too.
Citrix (ICA Client) doesn't work as VNC, it just doesn't draw on a part of the screen, but it tries to interact with the X server. So every window appearing on screen is registered in X and the Window Manager. Which means that, obviously, the Window Manager goes through its list of windows to determine the best place where to place this new window. Actually this new window gets two new locations. What eventually happens is that X thinks that the window is in one place, while ICA Client thinks it's somewhere else.
And, officially, ICA Client is responsible for redrawing all windows it cares for. The client will redraw it's own location of the window and only accept interaction in this area - rendering the the window the WM placed originally somewhere else entirely useless.
What makes matters worse is that this this behaviour isn't always reproducable, thus it's unpredictable. But there seems to be a correlation between the Window Managers window placement policy and Citrix capabilities to correctly mark windows as transient and/or children.
Right now working with fvwm again, but fluxbox seems to be promising, too.
I would be interested in hearing from you folks if you experience similar or other problems with the ICA client.
Update: Using fvwm with Citrix kills the Citrix session the moment the workspace switcher is used. Disabled it.
Citrix (ICA Client) doesn't work as VNC, it just doesn't draw on a part of the screen, but it tries to interact with the X server. So every window appearing on screen is registered in X and the Window Manager. Which means that, obviously, the Window Manager goes through its list of windows to determine the best place where to place this new window. Actually this new window gets two new locations. What eventually happens is that X thinks that the window is in one place, while ICA Client thinks it's somewhere else.
And, officially, ICA Client is responsible for redrawing all windows it cares for. The client will redraw it's own location of the window and only accept interaction in this area - rendering the the window the WM placed originally somewhere else entirely useless.
What makes matters worse is that this this behaviour isn't always reproducable, thus it's unpredictable. But there seems to be a correlation between the Window Managers window placement policy and Citrix capabilities to correctly mark windows as transient and/or children.
Right now working with fvwm again, but fluxbox seems to be promising, too.
I would be interested in hearing from you folks if you experience similar or other problems with the ICA client.
Update: Using fvwm with Citrix kills the Citrix session the moment the workspace switcher is used. Disabled it.
cptsalek - 8. Okt, 09:17