On Tue, Feb 23, 2010 at 12:15, Tejas Guruswamy
I had never heard of kstartupconfig4 before, but a quick browse through KDE's websvn gives me this:
Neither have I :-)
So for some reason /home/user/.kde4/share/config/startupconfig file is corrupted/unreadable.
That's the approach I took as I started to dig into this. It turns out that KDE4 wasn't at fault here.... the hard drive was. There was a corruption on the hard drive, and the /home partition (reiser) was mounted read-only (discovered that by poking around in the messages logs). With the /home in ro mode, KDE could not start up since it needed to write locks etc to that ro partition. I did a reiserfsck /dev/sda3 which told me to do a --rebuild-tree. So I did a reiserfsck --rebuild-tree /dev/sda3 and it did it's magic... and I'm back up and running again. Question is.... do I trust the Reiser partition to continue working now? Do I need to replace the hard drive? C. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org