Hi all,
I just thought I'd share with all of you a little annoyance I have
observed a few times.
Just now my netscape 4.03 (aka communicator) froze... kept control
of my pointer and would not allow me to shift focus to an xterm
in order to kill it.
I had to wait for it to release control of the pointer for about
10 minutes!! Is there any other solution to this but waiting
(Short of kill the X server - or dropping to console and kill
netscape from there).
I kind of thend to think this is a wm problem.
Any comments on this as to why fvwm (2.0.45) would allow an X client
to take over control???
Is it proper to dismiss this as a problem of fvwm2? If not are there
any explainations as to why this would be allowed?
If this is a wm problem does anyone see a nice little fix for it?
I'm running fvwm 2.0.45 on Linux 2.0.0 on a i486 DX2 66 with 32MB RAM
and 2.1 gig drive ( with plenty of swap space :)
Thanks in advance,
Patrick ...
patrick_at_boxsoft.com
--
Visit the official FVWM web page at <URL:http://www.hpc.uh.edu/fvwm/>.
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 Sep 23 1997 - 21:09:59 BST