[prev in list] [next in list] [prev in thread] [next in thread] 

List:       koffice
Subject:    Re: kded not started
From:       Simon Hausmann <tronical () gmx ! net>
Date:       1999-06-05 19:58:58
[Download RAW message or body]

On Sat, 5 Jun 1999, Reginald Stadlbauer wrote:

> On Sat, 05 Jun 1999, Simon Hausmann wrote:
> >On Sat, 5 Jun 1999, Harri Porten wrote:
> >
> >> Simon Hausmann wrote:
> >> > 
> >> > On Sat, 5 Jun 1999, Reginald Stadlbauer wrote:
> >> > 
> >> > > Hi!
> >> > > Shouldn't kded get started automatically? It's not the case for me. So, if I
> >> > > just start e.g. KWord and say file->open it crashes because of a mico
> >> > > exception (in the koFilter stuff). When I start kded manually first,
> >> > > everything works fine.
> >> > 
> >> > Hm, it works fine here.
> >> > The debug output also should say something.
> >> > 
> >> > Perhaps you can copy&paste the output of KWord from the beginning until it
> >> > is completely loaded?
> >> 
> >> Answering on the behalf of Reggie:
> >> 
> >> > kword
> >> kde_bindir() is obsolete. Try to use KStandardDirs instead
> >> kde_bindir() is obsolete. Try to use KStandardDirs instead
> >> kde_configdir() is obsolete. Try to use KStandardDirs instead
> >> kde_configdir() is obsolete. Try to use KStandardDirs instead
> >> QGDict::hashStringKey: Invalid null key
> >> KStdDirs::findResDir(): can't find "de/charset" in type "locale".
> >> KStdDirs::findResDir(): can't find "de_DE/charset" in type "locale".
> >> KStdDirs::findResDir(): can't find "de/charset" in type "locale".
> >> KStdDirs::findResDir(): can't find "de/LC_MESSAGES/kword.mo" in type
> >> "locale".
> >> KStdDirs::findResDir(): can't find "de/LC_MESSAGES/kdelibs.mo" in type
> >> "locale".
> >> exception handling not supported,
> >> the following exception has been thrown:
> >>   IDL:omg.org/CORBA/BAD_PARAM:1.0 (0, not-completed)
> >> Aborted
> >
> >I had something similar once, too, and I solved it by making 100% clean
> >and recompiling everything (kdelibs + koffice) .
> >Or did you do that already?
> 
> I'm doing that every day. But once it was started (two days ago or so) and I
> killed it with killall -9 kded, because it was not killed automatically. After
> that it never started automatically again (I also didn't logout since that
> time). Could it be the problem, that I killed it manually once?

Hmmmm. Perhaps something went wrong with the root-properties stuff?
Has the x-server been restarted since that time? ;-)

To be sure kill any running kded, execute a
xprop -root -remove KDED_RESOURCES
and try again.


Ciao,
  Simon

--
Simon Hausmann       <hausmann@kde.org>
http://www.kde.org/  <tronical@gmx.net>

[prev in list] [next in list] [prev in thread] [next in thread]