Bug 115857 - kded and kat bug with signal 8 (SIGFPE)
Summary: kded and kat bug with signal 8 (SIGFPE)
Status: RESOLVED DUPLICATE of bug 116652
Alias: None
Product: kat
Classification: Applications
Component: general (show other bugs)
Version: 0.6.3
Platform: Mandriva RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: Roberto Cappuccio
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-11-07 13:38 UTC by David
Modified: 2006-07-26 10:29 UTC (History)
0 users

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 David 2005-11-07 13:38:34 UTC
Version:           0.6.3 (using KDE KDE 3.4.2)
Installed from:    Mandriva RPMs
OS:                Linux

When kat is indexing some files it makes kded to crash but when i stop KAT everything is ok. To solve the problem i killed KAT.
I don`t even know what for it`s good too :)
Comment 1 Juan Pablo Morelli 2005-11-29 14:15:44 UTC
Same problem. Killing kat everythin's ok.
Comment 2 Lars-Olof Olsson 2006-01-05 20:19:23 UTC
I also experienced the same error. Uninstalling kat solved it.
Comment 3 Fred Obermann 2006-01-08 11:29:22 UTC
Same problem also using Mandriva 

(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 -1230390400 (LWP 6835)]
[New Thread -1253053520 (LWP 6900)]
[New Thread -1244660816 (LWP 6899)]
[New Thread -1234130000 (LWP 6893)]
(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  0xb6862831 in KatIndexerManager::customEvent ()
   from /usr/lib/kde3/kded_katd.so
#5  0xb761808c in QObject::event () from /usr/lib/qt3/lib/libqt-mt.so.3
#6  0x0813f2e0 in ?? ()
#7  0xb4b71fe8 in ?? ()
#8  0xbfae4e74 in ?? ()
#9  0xb7a5e434 in ?? () from /usr/lib/qt3/lib/libqt-mt.so.3
#10 0xb7a5e434 in ?? () from /usr/lib/qt3/lib/libqt-mt.so.3
#11 0x08118000 in ?? ()
#12 0xbfae4e74 in ?? ()
#13 0xb75b6e80 in QApplication::internalNotify ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#14 0x0813f2e0 in ?? ()
#15 0xb4b71fe8 in ?? ()
#16 0xb4b71fe8 in ?? ()
#17 0xb7a5e434 in ?? () from /usr/lib/qt3/lib/libqt-mt.so.3
#18 0x0812e930 in ?? ()
#19 0x08107f80 in ?? ()
#20 0x00000000 in ?? ()
Comment 4 Bernard Heathcote 2006-04-14 23:18:42 UTC
I'm new to Linux and have only recently installed Mandrake 10.1 followed by update to Mandriva 2006, so I'm not at all sure what is going on. When first installed Mandriva works fine for a day or so but then, during the start up process the 'fault' window appears saying, among other things, "The application KDE (KDED) crashed and caused the signal 8 (SGFPE)". The listing given by earlier report can be viewed. The 'fault' window can be closed but reappears a second or two later, and so on. The first time this happened the only way I could get rid of this problem (not being Linux proficient) was to completely wipe the whole Linux install and re-install. It has now happened, after a couple of days, with my new install.
What do I do???
Comment 5 Andreas Kling 2006-07-26 10:29:33 UTC

*** This bug has been marked as a duplicate of 116652 ***