On 12/03/2011 03:46 PM, Middlecope wrote:
> Do you have a hint which log file to inspect?
> I see several.
/var/log/kdm.log (not sure about that one)
and, do this:
1. before you log out next time open kedit (or similar) and type this
into a new doc:
and save it to /home/[yourID]/.kde4/Autostart/sneekypeeky
# created 03 Dec 11 to open top on the desktop at boot
then, in a terminal type and enter
(OR, you can use Dolphin to nav to that file and mark it executable)
chmod +x ~/.kde4/Autostart/sneekypeeky
2. shut down all your open applications so that next time you start it
won't have a bunch to begin (in fact, that may be all you have to do:
STOP leaving every thing running)
3. then when you reboot it should pop up a terminal with a running
instance of 'top' where you can SEE what is sucking up the
resources...it will change every few seconds...write down the name of
the running resource sucker as it changes..
if you are not already familiar with top: open a terminal and start it,
once you have discovered what is taking so much horsepower you can use
Dolphin to delete (or move) sneekypeeky
openSUSE®, the "German Engineered Automobiles" of operating systems!