Ryan Daly <[EMAIL PROTECTED]> writes: > On Wed, 2002-12-18 at 21:07, Dan Espen wrote: > > 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? > > Yep, here's the output:
Good, that confirms that the EMC problem is the same problem as we see with rm6. Its the same toolkit is being used in both products. > : edm 23#; ldd `which edm` > ** libndvgm.so => /usr/epoch/lib/libndvgm.so ... > > 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. > > > > I wasn't sure whether you wanted me to run this on the Linux box or on > the EDM, so I've attached the output from both. The file names are > pretty descriptive as to what each file contains. (Although, if the > DISPLAY variables are the same, not sure that this really matters > anyway.) Run this on the Linux machine, (the display with the problem). Please send BOTH the error message from EDM and the xwininfo that existed just before the error message is generated. There is a window id in the error message that I want to find in the xwininfo output. > > Strange as it seems, thats what we observed. > > I just started :1 and verified things act the same as :0. I think that shows that the problem has some kind of random component to it. The same thing with vmware, its not vmware itself causing the problem, it just changing something enough to make this problem start to appear. -- 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]
