Bug 116652 - kded crashes and restarts every few seconds
Summary: kded crashes and restarts every few seconds
Status: RESOLVED FIXED
Alias: None
Product: kat
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Mandriva RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: Roberto Cappuccio
URL:
Keywords:
: 115030 115857 118080 118816 126069 (view as bug list)
Depends on:
Blocks:
 
Reported: 2005-11-18 20:04 UTC by Silvano
Modified: 2006-07-26 10:54 UTC (History)
5 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Silvano 2005-11-18 20:04:50 UTC
Version:            (using KDE KDE 3.4.2)
Installed from:    Mandriva RPMs
OS:                Linux

kded crashes and restarts every few seconds. 
After about 50-60 times he tries to restart itself, it USUALLY stops to restart!
The backtrace is the following:

(no debugging symbols found)
Using host libthread_db library "/lib/tls/libthread_db.so.1".
(no debugging symbols found)
`shared object read from target memory' has disappeared; keeping its symbols.
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1230841632 (LWP 5190)]
[New Thread -1262269520 (LWP 5219)]
[New Thread -1253168208 (LWP 5215)]
[New Thread -1244775504 (LWP 5214)]
[New Thread -1236382800 (LWP 5210)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[KCrash handler]
#4  0xb664f831 in KatIndexerManager::customEvent ()
   from /usr/lib/kde3/kded_katd.so
#5  0xb75aa08c in QObject::event () from /usr/lib/qt3/lib/libqt-mt.so.3
#6  0x0815aa50 in ?? ()
#7  0x083b9198 in ?? ()
#8  0xbfa71d64 in ?? ()
#9  0xb79f0434 in ?? () from /usr/lib/qt3/lib/libqt-mt.so.3
#10 0xb79f0434 in ?? () from /usr/lib/qt3/lib/libqt-mt.so.3
#11 0x080f2b40 in ?? ()
#12 0xbfa71d64 in ?? ()
#13 0xb7548e80 in QApplication::internalNotify ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#14 0x0815aa50 in ?? ()
#15 0x083b9198 in ?? ()
#16 0x083b9198 in ?? ()
#17 0xb79f0434 in ?? () from /usr/lib/qt3/lib/libqt-mt.so.3
#18 0x081255d4 in ?? ()
#19 0x080f06b8 in ?? ()
#20 0x00000000 in ?? ()

The crash has reported the signal 8 (SIGFPE)

I tried to start kded from the shell, and I've received this "responses":

[silvano@Sirio ~]$ KWrited - listening device /dev/pts/1
kded: CppSQLite3DB::~CppSQLite3DB()*****************
kded:  Created engine, scheduler and read catalogs
QLayout "unnamed" added to CatalogStatusItem "CatalogStatus", which already has a layout

[silvano@Sirio ~]$ Last DCOP call before KDED crash was from application 'kded'
to object 'KDirNotify-4', function 'FilesChanged(KURL::List)'.
KCrash: Application 'kded' crashing...

[silvano@Sirio ~]$ KWrited - listening device /dev/pts/1
kded: CppSQLite3DB::~CppSQLite3DB()*****************
kded:  Created engine, scheduler and read catalogs
QLayout "unnamed" added to CatalogStatusItem "CatalogStatus", which already has a layout
Last DCOP call before KDED crash was from application 'DCOPServer'
to object '', function 'applicationRemoved(QCString)'.
KCrash: Application 'kded' crashing...
KWrited - listening device /dev/pts/1
kded: CppSQLite3DB::~CppSQLite3DB()*****************
kded:  Created engine, scheduler and read catalogs
QLayout "unnamed" added to CatalogStatusItem "CatalogStatus", which already has a layout


THIS several times :)

Thank all for any eventual idea :D

B.R.

Silvano
Comment 1 David Förster 2005-11-24 17:50:02 UTC
*** This bug has been confirmed by popular vote. ***
Comment 2 rick stockton 2006-02-05 10:57:52 UTC
I also use Mandriva RPMs, but I am running on the 'Cooker' KDE 3.5.1: and the problem happens here too. Not sure if it's something about Mandriva's packaging. But you have it shown here as a KAT issue?

Can I make the problem go away by removing Kat?
Comment 3 rick stockton 2006-02-05 11:01:18 UTC
I forgot to mention... in my case, I have many concurrent instances of kded: they've all fallen into the crash handler, except for one which is actively running (for a few moments). 
Comment 4 rick stockton 2006-02-06 21:56:58 UTC
I should be in a different bug, my occurences are all SIGSEGV.

HOWEVER: I renamed /usr/bin/kat as "kat-save", and created an empty "kat" file (not even executable). Instead of crashing and restarting 40 times, it now gives up after just a couple of tries. It would be REAL NICE, however, if KDED was modified to:

1) check that "kat" exists, and if not: 2) bypass invoking it.

This would be REAL NICE, because KDED is also responsible for many other things. 


I followed Mandriva instructions to create a file ".mdv-no_Kat" in $HOME, and it had NO EFFECT on the KDED crash loop (I was still looping 40 times with that file present). But maybe that workaround was (accidentally, IMHO) not brought forward to the Cooker 3.5 Version.
Comment 5 Ivica Culjak 2006-02-18 20:16:01 UTC
I have reported the same problem in bug report #118080, so you can have look at that report number. It's backtrace dump is pretty similar to the one reported here, and it is also shown as signal 8, (SIGFPE). My report is listed as UNCONFIRMED, so maybe if you add comments to it the problem should be looked into.
Comment 6 Andreas Kling 2006-07-26 10:24:20 UTC
*** Bug 118080 has been marked as a duplicate of this bug. ***
Comment 7 Andreas Kling 2006-07-26 10:24:58 UTC
*** Bug 115030 has been marked as a duplicate of this bug. ***
Comment 8 Andreas Kling 2006-07-26 10:29:34 UTC
*** Bug 115857 has been marked as a duplicate of this bug. ***
Comment 9 Andreas Kling 2006-07-26 10:46:06 UTC
*** Bug 126069 has been marked as a duplicate of this bug. ***
Comment 10 Andreas Kling 2006-07-26 10:46:20 UTC
*** Bug 118816 has been marked as a duplicate of this bug. ***
Comment 11 Andreas Kling 2006-07-26 10:54:26 UTC
Fixed in revision 482681.