Yes, I know this problem. You can avoid rebooting by:

1. Check that your swapfile is not full. If it is, generate a much bigger one.

Tip: Use a console (Ctrl+Alt+F2), log in as root, and run top. Swapfile stats are at the top.
This will then be there whenever you want it. whether KDE is running or not.
Don't run it from KDE, because of 2 below.


2. When things slow down do Ctrl+Alt+Backspace and relog on. This is quick and will give you a new KDE and current applications setup.
Particularly in this case a new Mozilla/Galeon, which in my case seems to trigger the slowdown problem.



Adam Williamson wrote:


I've just started noticing this since I came in from work, about
10:30pm. Since then I've updated to kernel 0.5mdk and a few other minor
updates (lm_sensors 2.8.0 and a couple of other small things). Certain
things, between which I can't find much of a link, seem to slow the
system down *massively*; the two I've noticed most so far are running
urpmi --auto-select, and saving a file with Galeon. When doing either of
these, the system becomes incredibly sluggish to respond - if I bring a
window forward, for instance, I can watch it redrawing in separate
stages, with several seconds between each, and the whole system just has
the very sluggish response you'd expect if 100% CPU were being used or
something. top does not report 100% CPU usage, though. Anyone else
seeing this? Any idea what the problem is?



-- Ron. [Melbourne, Australia] "If you keep a green bough in your heart, the singing bird will come" Get Fastest Mandrake downloader, English-only, from: http://members.optusnet.com.au/ronst/ Click all ye faithful!





Reply via email to