>> I have some more info, after doing more research. It turns out that
>> kicker hangs. When I run kicker -v, I get:
>> Qt: 2.3.0
>> KDE: 2.1.1
>> KDE Panel: 1.1
>> I can't find any documentation that describes what files kicker reads.
>> I am guessing that a file is missing after the hard disk corruption.
>> Since it works for root, I don't think it is a problem with the kicker
>> - Gardner
>>> I am running Red Hat linux 7.1. My computer (IBM Thinkpad) locked up
>>> when I tried to run xconq, and I had to power it off. When it came
>>> up, there were errors that I had to fix with fsck.
>>> My problem is now that my user login (gardner) comes up with a
>>> desktop with no kde panel. I can log in as root and the panel comes
>>> up for me there. I have looked all over the ~/Desktop directories for
>>> both gardner and root, and they seem to be identical.
>>> Is there a way to force a rebuid of the panel? Under the kde FAQ,
>>> they seem to indicate that you can run "kpanel" to get a kde panel
>>> under other window managers, but I can't find kpanel on my system
>>> anywhere (find / -name kpanel returns nothing).
>>> Thanks for any help!
>>> - Gardner
> $ rm -r ~/.kde
> Log out, log in.
Thanks! I did that and the panel reappeared until I finished with
the KDE Desktop wizard that shows up when you first log in under kde 2.2
(which I installed trying to fix this problem). Then the panel went
away again and I had a core file in my home directory.
So, I just did the rm again (I removed *everything* .x* .m* .D* .M*, .k*,
etc), logged in again and skipped the wizard. Now I seem to be ok.