With fvwm-2.4.1 and above, I've been experiencing really weird X
crashes. fvwm works fine, until I switch virtual consoles away from X
and back again. When using any window manager but fvwm-2.4.x, nothing
bad happens; but if fvwm-2.4.x is running in the X session[1], every X
client that was being managed by fvwm at the time of the switch freezes
solid. fvwm thinks it's still there (so you can manipulate the --- now
forever unrepainted --- windows), and the process is still there, but
it's blocked in select() forevermore.
I'm using XFree86-4.1.0 (from CVS at XFree86) on an i586-pc-linux-gnu
box with glibc-2.2.4 and the mga driver.
I'm not sure if this is really a fvwm bug, but fvwm is implicated
(somehow); if it's not a fvwm bug it's an XFree86 bug triggered by
fvwm-2.4.x. To be honest, I'm not even sure where to start searching for
the bug; nothing's looping and eating CPU or I could hit it with gprof,
nothing dumps core, and I'd rather eat my own intestines than try to
debug a running X server. Everything just, well, stops working.
(This probably started happening somewhere in the 2.3.x range, but I
jumped straight from 2.2.5 to 2.4.1. It still happens with 2.4.3.)
I'm stumped. Anyone else got any clues?
[1] I'm not sure if the session being switched away from or the one
being switched to crashes.
--
`You're the only person I know who can't tell the difference
between a pair of trousers and a desk.' --- Kieran, to me
--
Visit the official FVWM web page at <URL: http://www.fvwm.org/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_fvwm.org.
To report problems, send mail to fvwm-owner_at_fvwm.org.
Received on Sat Nov 03 2001 - 07:31:03 GMT