Dan Espen <[EMAIL PROTECTED]> writes:
> Dominik Vogt <fvwm-workers@fvwm.org> writes:
> > On Fri, Jun 29, 2001 at 08:32:06AM -0400, Dan Espen wrote:
> > > Dominik Vogt <[EMAIL PROTECTED]> writes:
> > > > On Thu, Jun 28, 2001 at 02:21:05PM -0400, Dan Espen wrote:
> > > > > I just observed another problem that was fixed a while back and
> > > > > appears to have come back.  As long as a menu is posted, fvwm
> > > > > is causing X activity.
> > > > 
> > > > I don't see any X activity, but this may depend on the menu styles
> > > > you use.  Can you please post the relevant lines?
> > > 
> > > It happens for me with no .fvwm2rc file at all,
> > > just using the built in menu.
> > > 
> > > I've only got one computer at home, this is difficult to debug without
> > > 2 machines.
> > 
> > You can either start a second X server and fvwm in an XNest
> > window:
> > 
> >   $ exec Xnest -full -sync -name "Xnest :3" :3
> >   $ fvwm2 -d :3 -cmd "FvwmCpp $HOME/.fvwm/.fvwm2rc"
> > 
> > Or start a second X server:
> > 
> >   $ exec xinit /bin/sleep 100000 -- :1
> >   $ fvwm2 -d :1 -cmd "FvwmCpp $HOME/.fvwm/.fvwm2rc"
> > 
> > Running fvwm in xnest is often easier to debug since you don't
> > need to switch screens, but moving the pointer out of the window
> > may generate unwanted events.
> 
> I'm at home.
> I'm stuck with Exceed and W98.
> Actually, I see that I can use a telnet window at the same time I have
> a menu posted.
> 
> I'll see if I can figure out whats going on.

Ok, heres a trace:

Attachment: trace.gdb
Description: Binary data

-- 
Dan Espen
444 Hoes Lane  Room RRC 1C-214           E-mail: [EMAIL PROTECTED]
Piscataway, NJ 08854                     Phone: (732) 699-5570

Reply via email to