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

List:       kde-core-devel
Subject:    Re: kded crashes
From:       Simon Hausmann <tronical () gmx ! net>
Date:       1999-07-12 16:07:03
[Download RAW message or body]

On Mon, 12 Jul 1999, Michael Reiher wrote:

> Werner Trobin wrote:
> > 
> > Michael Reiher wrote:
> > >
> > > Hi,
> > >
> > > Since yesterday konqy always crashes on start up. Output:
> > >
> > > kdevel@penguin:~ > konqueror
> > > KStdDirs::findResDir(): can't find "kfmrc" in type "config".
> > > kiolib (KRegistry): addFactory : adding path /opt/kde-CVS/share/mimelnk/
> > > kiolib (KRegistry): addFactory : adding path
> > > /opt/kde-CVS/share/servicetypes/
> > > kiolib (KRegistry): ========== SCANNING /opt/kde-CVS/share/mimelnk/
> > > ==============
> > > kiolib (KRegistry): Reading directory /opt/kde-CVS/share/mimelnk/
> > > kiolib (KRegistry): Reading directory
> > > /opt/kde-CVS/share/mimelnk/application
> > > kiolib (KRegistry): Reading directory /opt/kde-CVS/share/mimelnk/audio
> > > kiolib (KRegistry): Reading directory /opt/kde-CVS/share/mimelnk/image
> > > kiolib (KRegistry): Reading directory /opt/kde-CVS/share/mimelnk/inode
> > > kiolib (KRegistry): Reading directory /opt/kde-CVS/share/mimelnk/text
> > > kiolib (KRegistry): Reading directory /opt/kde-CVS/share/mimelnk/video
> > > kiolib (KRegistry): ========== SCANNING /opt/kde-CVS/share/servicetypes/
> > > ==============
> > > kiolib (KRegistry): Reading directory /opt/kde-CVS/share/servicetypes/
> > > uncaught MICO exception: IDL:omg.org/CORBA/COMM_FAILURE:1.0 (0,
> > > not-completed)
> > > Aborted
> > >
> > > The problem seems to be somewhere in that function(at least the
> > > exception is thrown at the end of it):
> > >
> > > #0  KDED::InitialReferences_stub::knamingService (this=0x81aced8) at
> > > kded.cc:341
> > > #1  0x40df5998 in KdedInstance::knaming (this=0xbffff5e4) at
> > > kded_instance.cc:144
> > > #2  0x808949b in main (argc=1, argv=0xbffff764) at konq_main.cc:383
> > >
> > > Any idea? Simon? Steffen?
> > >
> > 
> > Try to remove .kde/share/config/kregistry after starting KDE.
> I forgot to mention that I had another kind of crash before. Seemed to
> be because of a corrupted kregistry. So I removed the whole .kde dir
> (It's faster:-) and not only kregistry. Afterwards I got the above.
> Maybe that's the reason. 

To me it looks like kded crashed, but the IOR property was still
published. So Konqy tried to contact a non-existing kded.

Removing the property and restarting kded should fix it, or?

Bye,
 Simon

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