Ultimately the problem turned out to have something to do with a screwed
up menu and the .kde/share/applnk directory. I cleaned out all of the
Koffice related entries in this directory and recreated the KOffice menu
in the Menu Editor. Everything appears to be in sync now and kword
starts as it should.
>>> I hope someone can help me solve this weird problem with KWord.
>>> I am running Red Hat 7.2 with Qt 2.3.1, KDE 2.2.2-2, and KWord 1.1.1.
>>> For one user KWord will no longer start, although: it used to work, all
>>> of the other KOffice apps work, and KWord still works for other users on
>>> the same box.
>>> Starting kword from the command prompt returns no information
>>> whatsoever. (Not very helpful for debugging.) Starting it with the
>>> --nocrashhandler option does not produce a core file.
>>> Can anyone suggest a solution?
>> First of all backup all the users config files. If you have
>> a backup of some working config files try restoring them
>> and verify that they still work. Otherwise use working
>> config files from another user optionally a newly create
>> Now that you have one set of files that works and one that
>> doesn't you can start looking for the problem. First find
>> the directory causing the problem, then find the file and
>> finally find the line.
>> That is the way I usually fix problems in KDE config files.
>> I have often experienced KDE spontaneously breaking its
>> config files. When you have found the problem you could
>> tell us the details if you want to.
> I initially tried replacing the obvious files like kwordrc and the
> .kde/share/config directory. When this didn't work I renamed the .kde
> directory to .kde.bak and allowed KDE to create a new .kde directory.
> It worked! Now I just have to replace the .kde directory components with
> my .kde.bak components until KWord stops working again.