I also experienced that Sametime Connect won't redisplay if you switch to a different workspace and back. I solved this in fvwm by a) making it "sticky", so it'd go with me when I switched, and b) putting it below everything else in the window stacking layer and making it stay there via fvwm's "StaysOnBottom" style.
Also re: the tiny "wine systray" window: fvwm allows you to override the "don't allow resize" hint, in which case you can resize it all you want. I use these settings:
Style "Lotus Sametime Connect*" NoTitle, Layer 0 2, CirculateSkip, Sticky
Style "Wine-Systray" ResizeHintOverride, CirculateSkip, Layer 0 2, Sticky
I recently upgraded to kernel 2.6.6 and CxOffice 3.0, and observed something else: if I'm logged in, and I exit, I get an uncaught exception (and lots of debugging output about "such-and-such library has-or-doesn't-have debug information". But, if I log out, and then exit, no exception, and so no extra debug output.
One really weird behavior I haven't been able to pin down or explain: it seems to run better (connects w/out error more frequently) if I cd to the installation directory and run it from there:
cd "/opt/cxoffice/support/dotwine/fake_windows/Program Files/Lotus/Sametime Client"
wine ./Connect.exe
than if I just run /opt/cxoffice/bin/connect. Running just /opt/cxoffice/bin/connect often seems to result in a hung connection. Not always, but often, so I just run it from the install directory and don't worry about it.
-- Larry Clapp, larry@theclapp.org