On Tue April 3 2007 12:08, Jay Smith wrote: <snip>

This problem happened right after the latest hard reboot. Any ideas as to what might fix it? I really don't want to have to reinstall. Thanks all.

Hi Jay, There's nothing "weird" about it... the filesystem has not been shut down correctly. When this happens, temporary files are not cleaned up, open files are left open instead of being properly closed and in-process writes-to-disk are truncated and files lost or corrupted. You really should have dealt with the overheating problem as soon as you diagnosed it instead of suffering through "20" hard reboots. They *can* and do frequently damage installations and cause data loss. Google, 'man' and 'info' really are your friends in this case, I'm afraid. The recovery process is detailed, can be tedious and is usually fraught with caveats and pitfalls. That's why so much time, effort and trouble go into a) employing regular backups and/or b) implementing technologies like mirroring and RAID. Fortunately, it is also extremely well documented in your 'user guide' or 'reference book' or 'admin guide'... whatever they're calling it these days. You can also search the SUSE mailing list archives here: opensuse: http://marc.info/?l=opensuse&r=1&w=2 suse-linux-e: http://marc.info/?l=suse-linux-e&r=1&w=2 Look for threads containing phrases like 'power failure', 'rescue mode', 'repair system', etc. There's a wealth of help maintained there for just these kinds of circumstances. hth & good luck! Carl -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On 4/3/07, Jay Smith <susehelp@torchlighttech.com> wrote:

Let me give you a little background. I have recently been having CPU fan errors and as you know, when it goes out, my CPU overheats and computer locks up. Reluctantly, I have to reboot the computer the hard way. Now, I have done that no more than 20 times in it's life (or at least since i've had this problem, don't kno the exact number). Anyways, now I get an error that says "KLauncher could not be reached via DCOP" whenever I click my desktop or taskbar icons. In addition to that, any KDE keyboard command I use gives me the same error (Ctrl+Esc for Ksysguard). I also can't run any programs. If I got to the KMenu and click YaST or Firefox, it doesn't even attempt to open it. This problem happened right after the latest hard reboot. Any ideas as to what might fix it? I really don't want to have to reinstall. Thanks all.

You can try: rescue system from the install CD/DVD run fsck on all partitions delete everything in /tmp (your system /tmp, not the rescue system in-memory /tmp) delete all in /var/run and /var/tmp (again, the "real" direcotries, not the ones used by the rescue system) in your home directory, see if files like .DC* exist and delete them (do not forget the leading period) in your home directory/.kde there are a bunch of symlinks to files and folders in /tmp, delete them. Reboot This should remove almost all not well written/damaged files which may cause KDE to not work. I may miss something, so others can add to this. Also - for recovery purposes - when I say "delete" actually I mean - rename the directories to something else, and recreate them with the old names. i.e. rename /tmp to /tmp.old, and create /tmp, etc. That way, if something goes wrong, you can recover to the current state. Cheers -- Svetoslav Milenov (Sunny) Even the most advanced equipment in the hands of the ignorant is just a pile of scrap. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org