Hey everyone. I'm seeing a strange problem with FVWM v2.5.27. I'm not sure if it's a bug or some odd configuration on my end or what, but I'd appreciate some help all the same.
So, I've got 2.5.27 installed on a Redhat EL5.5 machine and in general, it seems to work fine. We also have installed on the machine an in-house Smalltalk app that runs using Cincom Visualworks 7. When we open the app, the first window appears just fine, but if we try to open any other of the application's windows, the whole thing freezes, the new window does not appear, and we have to forcibly kill the process. Then, even stranger, the next time we load up the app, everything works fine and we can open as many windows are our hearts desire. But, when we reboot, log out, or otherwise end our login session, we have to repeat the process over again (i.e. launch the app, close it, and launch it again before we can actually use it.) I launched the smalltalk app in gdb and found that it was hanging in an Xlib call: XPeekIfEvent(). I can't really introspect it more than that, I'm afraid. Strangely, when I launched the app in gdb again afterwards (the second time, so everything should be cool) and asked it to break on an XPeekIfEvent() call, I found that no such call was made. I've seen the same thing happen with FVWM 2.5.13, but not any of the 2.4 series. Does anyone have any ideas as to what's going on or whether this is indeed a bug? -- Omar Zakaria Agilent Technologies W: 707-577-4214
