Ryan Daly <[EMAIL PROTECTED]> writes: > Guys, > > I have been experiencing the exact problem that you described in your > various e-mails. > > I can't pinpoint what causes the problem, but I experience it quite > often. It seems that stopping FVWM and restarting will cure the problem > for a bit, but after (something happens) the problem crops up once > again. > > The application I started seeing this with is the GUI that accompanies > the EMC Data Manager. I know immediately if things are working or not > because the window immediately gets closed. I usually get an error > similar to the following:
Thats pretty strange, any chance EMC Data Manager and rm6 use the same GUI toolkit? If you do an ldd on the EMC binary do you see anything that looks like libndcore, libndvgm? Note that in the case of rm6, the rm6 was not the binary, it was just a shell, I had to look in the shell to figure out what the real name of the binary was. > X Error of failed request: BadWindow (invalid Window parameter) > Major opcode of failed request: 3 (X_GetWindowAttributes) > Resource id in failed request: 0x2800001 > Serial number of failed request: 921 > Current serial number in output stream: 922 OK, the application is calling XGetWindowAttributes and getting a bad window return code. Ie. the window doesn't exist. The window id is 0x2800001. You can see window id's with the xwininfo command. The easiest way is to type: xwininfo -root -tree The window id will be different each time you run, so run this command just before you create the problem. Then we should know which window its trying to read the attributes on that it can't find. > Today I started to attempt to "debug" this, and looked for help on any > debugging options when I came across this thread. I shut FVWM down and > restarted it. I stopped and started the application numerous times with > no trouble. I'm not sure if the number of windows I had open has > anything to do with things or not, but the problem came back after I had > a few XTerms open. Now that I don't have that many XTerms open, the > problem has gone away (but then again, I have 5 or 6 Mozilla windows > open). > > I also saw the same problem with rm6 (release 06.22.01.54). I just > installed the app today and started to familiarize myself with the it. > The initial window comes up with no problems. When I open any of the > other windows (i.e. Configuration, Status, Recovery, etc.) I get the > window, again with no trouble. That newly created window closes, > however, when I move the mouse over the buttons near the top of the > window (just below the File, Module, Options, Help section). > > Both premature closes happen during the same time frame. Meaning, if I > start the EDM window and it immediately closes, then I can also get rm6 > windows to close just by moving the mouse over the buttons, and vice > versa. If the action is happening with rm6, then the EDM window will > not start. > > Once one application starts functioning properly, the other does as > well. > > I'm sad to say that for a while I had moved to GNOME because I was not > seeing these problems there. But I can't handle GNOME any more and > wanted to come back 'home'. > > Please let me know what I can do to help track this problem down. Well, I think you've given us some useful hints. > I'm running on Red Hat 7.3 if that matters. > > Am I taking the previous e-mails correct when I say that it appears that > these problems do not crop up on :1, and only on :0? Strange as it seems, thats what we observed. -- Dan Espen E-mail: [EMAIL PROTECTED] -- Visit the official FVWM web page at <URL:http://www.fvwm.org/>. To unsubscribe from the list, send "unsubscribe fvwm-workers" in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
