Bug 118080 - right after login causes signal8 repeatedly (respawns indefinitely and I cannot use KDE session at all)
Summary: right after login causes signal8 repeatedly (respawns indefinitely and I cann...
Status: RESOLVED DUPLICATE of bug 116652
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:
Depends on:
Blocks:
 
Reported: 2005-12-10 18:26 UTC by Ivica Culjak
Modified: 2006-07-26 10:24 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 Ivica Culjak 2005-12-10 18:26:12 UTC
Version:            (using KDE KDE 3.4.2)
Installed from:    Mandriva RPMs
OS:                Linux

It starts right after logging in into KDE session.  At first (it started happening 2 days ago) it would display signal8 message once right after logon finished and the desktop and icons were fully displayed. Today it started happening repeatedly (as soon as I close one message it displays another and so ad infinitum. If I use GNOME than it crashes once after logon and it doesn't happen again until the next logon, so I can work in GNOME session but not in a KDE.

This is the Backtrace display:

 (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)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1230620992 (LWP 4679)]
[New Thread -1250677840 (LWP 4684)]
[New Thread -1242285136 (LWP 4683)]
[New Thread -1233892432 (LWP 4682)]
(no debugging symbols found)
[KCrash handler]
#4  0xb6a17831 in KatIndexerManager::customEvent ()
   from /usr/lib/kde3/kded_katd.so
#5  0xb748308c in QObject::event () from /usr/lib/qt3/lib/libqt-mt.so.3
#6  0x081291b8 in ?? ()
#7  0x083926f8 in ?? ()
#8  0xbfa85f64 in ?? ()
#9  0xb78c9434 in ?? () from /usr/lib/qt3/lib/libqt-mt.so.3
#10 0xb78c9434 in ?? () from /usr/lib/qt3/lib/libqt-mt.so.3
#11 0x080d4248 in ?? ()
#12 0xbfa85f64 in ?? ()
#13 0xb7421e80 in QApplication::internalNotify ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#14 0x081291b8 in ?? ()
#15 0x083926f8 in ?? ()
#16 0x083926f8 in ?? ()
#17 0xb78c9434 in ?? () from /usr/lib/qt3/lib/libqt-mt.so.3
#18 0x081969e0 in ?? ()
#19 0x080ece98 in ?? ()
#20 0x00000000 in ?? ()
Comment 1 Ivica Culjak 2006-02-18 19:50:28 UTC
*** This bug has been confirmed by popular vote. ***
Comment 2 Andreas Kling 2006-07-26 10:24:19 UTC

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