Sorry, I don't understand what this "kludge" is. Is there some type of
"kludge code" somewhere (WM, X Server, something else?) that was
put in to circumvent some known problems with any (or perhaps all) window
managers when a Zaurus is suspended for a certain amount of time?
I remember posting about the noticed WM restart after along suspend, and at
the time I posted "everything is fine afterwards". I never left Firefox running though,
just simple X clients, so most likely all would not have been fine.
In addition to wanting to know a little more about both the kludge and why it
was put in, I'm also very curious as to why Firefox and some other X clients fail. I
think it might be helpful to invoke Firefox from an xterm, and capturing the
output, after resuming and a client termination occurs. I install just about everything
to SD including Firefox, and perhaps the hang occurs due to the fact that
the SD isn't 100% usable immediately after a resume? (just a thought)
In the past, on a variety of *IX machines, I would often change window
managers on the fly. But I would start X11 a little differently, such the X
Server would not terminate when the WM did. I could then simply kill the
WM, and restart a different one at will. I never encountered an X client that
would have problems with this.
Another thought that came to mind, is that if any system time setting is done on a
resume, that could be a factor causing a hang. I figured I'd mention that also,
in case it rings a bell as something that might have been changed after RC10.
John
