Re: FVWM: Help! Windows keep dying on me...

From: Dan Espen <dane_at_mk.telcordia.com>
Date: Sat, 01 Nov 2003 14:57:32 -0500

Ryan Daly <daly_at_ctcnet.net> writes:
> Dan Espen wrote:
> > Ryan Daly <daly_at_ctcnet.net> writes:
> >
> > Ask them to look at this post:
> >
> > http://www.hpc.uh.edu/fvwm/archive/0212/msg00286.html
> >
> > I believe it summarizes our findings.
> >
> > As far as their statement about using another window manager,
> > I don't know what to tell you.
>
> I don't mean to throw something else into the mix here, but I did some
> "testing" before I'd get Sun involved. I remembered a while back when I
> was looking into this that I stumbled on something, but don't think I
> ever made sure of my findings.
>
> Turns out, the two windows that act up at for me don't act up by
> themselves. Meaning, if I have RM6 and/or the EDM GUI running, things
> seem fine. This leads me to believe there's another application in the
> mix that's introducing something strange into the environment that's
> causing the entire problem. Could this be the case?
>
> Here's why I think that. At work, I run Checkpoint's PolicyEditor.
> While that was running, I started my EDM GUI. The main window briefly
> opened, but exited just after the "About" window closed. I closed the
> Checkpoint GUI and restarted the EDM GUI, which now functioned properly.
> I then remembered RM6 showed symptoms while the EDM symptom was there.
> I closed the EDM GUI, started Checkpoint, and then started RM6. Sure
> enough, when moving the pointer over the buttons that pop-up the balloon
> help, the window died, which (I think) is the symptom that most people
> are complaining about.
>
> So, my problems only appeared to be present when the Checkpoint GUI was
> up and running. This was until I noticed yesterday that both RM6's and
> the EDM's symptoms were still present even though the Checkpoint GUI had
> no longer been running. (Maybe there's residual effects from having
> that window open?)
>
> So, thinking back, I remembered that I had been running VMWare
> Workstation v3.x while my problems were present the first time around.
> I grabbed a copy of WMWare 3.x today and started it up (you only need to
> run vmware-config.pl and then start the vmware binary to see the
> problem, no need to actually install a vmware host). The problem was
> there. I stopped VMWare and the problem went away.
>
> Note I started v3.x. The new version of VMWare (4.x) does NOT produce
> the symptoms in RM6 and the EDM GUI.
>
> What do you think about this? Could it be that the problem is VMWare
> 3.x and the Checkpoint GUI instead of the other two (RM6 and EDM GUI)?
> Is it possible that something strange is being introduced that's
> screwing up the other apps?

As I remember, when I did some testing with this, I was using
a virtual X environment so RM6 was running by itself.
One "quirk" is that I would get the problem when the virtual X
environment was set up with
$DISPLAY set to X:0 and it would work fine with $DISPLAY as X:1.

I think that just illustrates that something random is going on.
None of this helps me, or anyone else that followed along with
the debugging to figure out what was going on.

-- 
Dan Espen                           E-mail: dane_at_mk.telcordia.com
--
Visit the official FVWM web page at <URL: http://www.fvwm.org/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_fvwm.org.
To report problems, send mail to fvwm-owner_at_fvwm.org.
Received on Sat Nov 01 2003 - 14:01:32 GMT

This archive was generated by hypermail 2.3.0 : Mon Aug 29 2016 - 19:37:55 BST