I have experienced hangups in starting X/fvwm2 on my Linux box, but they
are generally my fault. I diagnose them by looking at the virtual
terminal output. I am using ssh-agent to invoke xinit (bypassing startx
because I want to run with -auth options and it hasn't worked through the
std startx script; no I haven't done what the startx comments say
internally and rebuilt the script to fix my problems).
What I saw before I got my .Xauthority file set up correctly was a raft of
"can't connect to display" messages from fvwm as it tried to connect to
the display without the proper magic cookie codes. Such errors don't
leave the mouse hung up, though. It should be an interesting diagnostic
pointer, if someone's mouse is frozen. I have had Netscape do (I think) a
server grab and freeze my X display for activities, but I can still move
the mouse. I haven't disabled the Ctrl-Alt-BackSpace hotkey for killing
the X server, so I use that for getting out of this problem. I can also
use the Shift-Alt-F? keys to get to the other virtual terminals on a Linux
system to try to determine what is happening if I can't tell from error
messages on the VC from which X was started.
Hope this helps, but it isn't at all fvwm(2) specific. Back to background
mode.....
Michael Tiefenback
--
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 Wed Jul 29 1998 - 11:49:25 BST