%% Dominik Vogt <dominik_vogt_at_hp.com> writes:
dv> On Mon, Feb 15, 1999 at 09:47:05PM -0700, don_at_grames.net wrote:
>> I just upgraded to FVWM 2.1.10 from 2.1.7 and immediately started
>> experiencing x server lockups. No core dumps or any other remains to
>> look at. I can't even say it is a problem with Fvwm, but where would a
>> good place to start be.
dv> I had the same with 2.0.46 and all later fvwm's (well, I never used
dv> another window manager long enough to verify if it's fvwm only).
dv> The X server doesn't really lock up. It just takes a minute or two
dv> before fvwm comes up.
The problem might be more than this. Remember there were situations
where some of the modules (WinList again? I forget) and fvwm2 could get
into a deadlock situation in some circumstances, where both were waiting
for the other--something to do with input grabs or something.
I believe a partial fix for this was made (actually IIRC it involved
removing a fix that made this problem worse) in later betas.
PS. fvwm takes a minute or two to come up? Really? Amazing. Even back
when I had a pathetic 486/66 for Linux fvwm2 started a lot faster
than that for me. Of course, my config is pretty straightforward.
--
-------------------------------------------------------------------------------
Paul D. Smith <psmith_at_baynetworks.com> Network Management Development
"Please remain calm...I may be mad, but I am a professional." --Mad Scientist
-------------------------------------------------------------------------------
These are my opinions---Nortel Networks takes no responsibility for them.
--
Visit the official FVWM web page at <URL: http://fvwm.math.uh.edu/>.
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 Tue Feb 16 1999 - 08:55:11 GMT