On Sun May 13 21:54 , Ralph <[EMAIL PROTECTED]> sent: > > >On Sun May 13 14:55 , 'James G. Sack (jim)' >[EMAIL PROTECTED]> sent: > >>Ralph wrote: >>> "shorter, pointed questions" (Thanks jim): >[snip] >>> 3) Why does the clock continue to tick along when >everything >>> else seems frozen? >> >>(see last comment) X may be frozen (and processes blocked on >>non-forthcoming X-events) but the CPU and clock keep on >ticking. Indeed, >>as you have shown, everything outside of that X-instance >still works. >>Corollary: everything running within that X-instance is >toast. > >Well, that's where I must disagree. In every instance where >Mozilla got hosed, switching somewhere else then switching >back would show a Mozilla title bar on a blank window. This >Mozilla window continues to display correctly which leads me >to believe that Mozilla is still fine. > >It seems like something is stuck thinking that the icon I was >dragging is still in the drag process, even though it has >become detached from the mouse pointer.
Well, I just tried an experiment and confirmed that X is *not* hosed. I was pondering the list of items given by "ps afx". I was looking to see if I could figure out what I could kill to try to get it to let go of the frozen icon drag. I realize that mixer probably had nothing to do with anything, but figured "What could it hurt to kill that?". I killed it, and switched back over to the unresponsive X on F7 and found waiting for me a popup warning dialog stating, '"Volume Control" has quit unexpectedly. If you reload a panel object, it will automatically be added back to the panel." It gives me the options [Don't Reload] and [Reload] (as well as [X] in the upper right corner. I can't do anything about that dialog since mouse clicks and keyboard input are ignored over on F7, but the point is that X on F7 *is* responsive. I already went ahead and killed the mapping-daemon (not really knowing what it was (no man entry)) since it appeared that nothing else was spawned from it. I figured I would report this finding before trying the next "kill" (just in case the next kill bites off more than I want). (Like peeling an onion, wondering if the next layer will make the rest go "poof".) ---- Msg sent via CWNet - http://www.cwnet.com/ -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
