Hi Dave. Thanks for the good suggestions.
I've tried a few of them. Right now I'm running on the "buggy" X and monitoring from my other machine at the same time. I've dropped the number of proggies. Still not sure what's up, and I'll inform the thread when I figure it out. Thanks again. Chris W. On March 24, 2005 05:36 pm, David Liontooth wrote: > Hi Chris, > > To try to isolate the problem (I have no clue and others may have better > suggestions), I would start just X, without running a desktop manager. > Just type X at the command prompt -- that is to say, don't run gdm at > boot, or kill it and log in without running X-windows, then type X. > Open a new CLI (Ctrl+Alt+F2) and run top to see CPU usage. If you see > the same behavior, you know the problem in in XFree86, not in any number > of other apps that run when you run X-windows. I would in that case take > the problem to the Debian X-strike force, and active and responsive bunch. > > OTOH, the problem may well lie somewhere else, and running X alone works > fine. In that case, you could start a terminal session inside X-windows > with a command like > > xterm -display <your machine name>:0 & > > (I've only tried this on remote systems running a vncserver), and then > start one application at a time until you find the culprit. Sometimes > moving the configuration files temporarily out of the way helps (for > instance, ~/.kde). Or you could run icewm as your window manager and see > if you get the same problems. > > Dave -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
