FVWM: Serious Erratic Fvwm Bug

From: Jon Mountjoy <jon_at_fwi.uva.nl>
Date: Fri, 27 Oct 1995 13:49:02 +0100 (MET)

Hello Folks,

Many folks have experienced this problem, and I think it may have been the
cause of a couple of complaints here on the list as well.

patchlevel 38, version 2

When fvwm is called as the last thing in the .xinitrc, and in the
.xinitrc there are a lot of calls to programs which take some time to
start up, then there seems to be some race condition and some windows
are not `captured' by fvwm, or get the wrong colour border, or in the worst
cases, fvwm doesn't work at all and you need to log in else where to kill
everything off.

I can get around it by either of the following:
  [1] Not making fvwm the last entry in my .xinitrc, and making
       say a console window instead. Of course, this means that I have
       to kill the console window to exit.
  [2] Leaving it as the last entry, but starting up any heavy programs
       via the Init function of .fvwmrc
       This seems to work, and avoid the situation.

I suspect some race condition error in fvwm on start up.

Could somebody else try putting fvwm as last call in .xinitrc
with 15 "xload &" programs before it :-)

Jon
--
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_hpc.uh.edu.
To report problems, send mail to fvwm-owner_at_hpc.uh.edu.
Received on Fri Oct 27 1995 - 07:49:21 GMT

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