kded crash frequently

[Andres Mujica]

Hi, i'm having an issue with kde.

Every now and then, at starting session, at clossing session, for no reason, opening a windows, randomly, kded crashes.

this is the segfault message

no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
`system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols.
(no debugging symbols found)
(no de
.
.
.
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1231939360 (LWP 9761)]
[New Thread -1286612048 (LWP 9779)]
[New Thread -1278219344 (LWP 9778)]
[New Thread -1269826640 (LWP 9777)]
[New Thread -1259766864 (LWP 9776)]
[New Thread -1242596432 (LWP 9775)]
[New Thread -1250989136 (LWP 9774)]
(no debugging symbols found).
.
.
.
(no debugging symbols found)
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()
#0 0xffffe410 in __kernel_vsyscall ()
#1 0xb7d63c1e in pthread_setcanceltype () from /lib/tls/i686/cmov/libc.so.6
#2 0xb7ea1c71 in operator delete () from /usr/lib/libstdc++.so.6
#3 0xb7ea1ccc in operator delete[] () from /usr/lib/libstdc++.so.6
#4 0xb75abf70 in QStringData::~QStringData () from /usr/lib/libqt-mt.so.3
#5 0xb75a29e4 in QString::deref () from /usr/lib/libqt-mt.so.3
#6 0xb75a2c20 in QString::operator= () from /usr/lib/libqt-mt.so.3
#7 0xb60b358f in KatIndexerManager::customEvent ()
   from /usr/lib/kde3/kded_katd.so
#8 0xb7288bc7 in QObject::event () from /usr/lib/libqt-mt.so.3
#9 0xb7222f80 in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3
#10 0xb7223172 in QApplication::notify () from /usr/lib/libqt-mt.so.3
#11 0xb78b517c in KApplication::notify () from /usr/lib/libkdecore.so.4
#12 0xb71b3db7 in QApplication::sendEvent () from /usr/lib/libqt-mt.so.3
#13 0xb72244a3 in QApplication::sendPostedEvents ()
   from /usr/lib/libqt-mt.so.3
#14 0xb72245aa in QApplication::sendPostedEvents ()
   from /usr/lib/libqt-mt.so.3
#15 0xb71c6f4f in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3
#16 0xb723acfb in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
#17 0xb723ac1e in QEventLoop::exec () from /usr/lib/libqt-mt.so.3
#18 0xb7221c13 in QApplication::exec () from /usr/lib/libqt-mt.so.3
#19 0xb672637d in kdemain () from /usr/lib/libkdeinit_kded.so
#20 0xb7f22540 in kdeinitmain () from /usr/lib/kde3/kded.so
#21 0x0804dffc in ?? ()
#22 0x00000001 in ?? ()
.
.
.
#32 0x00000000 in ?? ()
#33 0x0805063e in vtable for QPtrList<char> ()
#34 0x00000001 in ?? ()
#35 0x00000000 in ?? ()
#36 0x00000000 in ?? ()
#37 0x00000000 in ?? ()
#38 0x00000000 in ?? ()
#39 0x00000000 in ?? ()
#40 0x00000000 in ?? ()
#41 0x00000000 in ?? ()
#42 0x00000000 in ?? ()
#43 0x00000000 in ?? ()
#44 0x00000000 in ?? ()
#45 0x00000000 in ?? ()
#46 0xb771e630 in vtable for QGArray () from /usr/lib/libqt-mt.so.3
#47 0x00000000 in ?? ()
#48 0x00000000 in ?? ()
#49 0x00000000 in ?? ()
#50 0x08051400 in vtable for QCString ()
#51 0x080a0b80 in ?? ()
#52 0x08051400 in vtable for QCString ()
#53 0x080a0aa8 in ?? ()
#54 0x08051400 in vtable for QCString ()
#55 0x080c49b8 in ?? ()
#56 0x08051400 in vtable for QCString ()
#57 0x080c49b8 in ?? ()
#58 0x08051400 in vtable for QCString ()
#59 0x080a0ae8 in ?? ()
#60 0xb771e630 in vtable for QGArray () from /usr/lib/libqt-mt.so.3
#61 0x080a0ae8 in ?? ()
#62 0xb771e630 in vtable for QGArray () from /usr/lib/libqt-mt.so.3
#63 0x080a0aa8 in ?? ()
#64 0xb771e630 in vtable for QGArray () from /usr/lib/libqt-mt.so.3
#65 0x080a0b80 in ?? ()
#66 0x00000000 in ?? ()
#67 0x00000000 in ?? ()
#68 0x00000000 in ?? ()
#69 0x00000000 in ?? ()
#70 0x00000000 in ?? ()
#71 0x00000000 in ?? ()
#72 0xb771e630 in vtable for QGArray () from /usr/lib/libqt-mt.so.3
#73 0x080a1928 in ?? ()
#74 0x00000000 in ?? ()
#75 0x00000000 in ?? ()
#76 0x00000000 in ?? ()
#77 0x00000000 in ?? ()
#78 0x00000000 in ?? ()
#79 0x00000000 in ?? ()
#80 0xb771e630 in vtable for QGArray () from /usr/lib/libqt-mt.so.3
#81 0x00000000 in ?? ()
#82 0x00000000 in ?? ()
#83 0x00000000 in ?? ()
#84 0x00000000 in ?? ()
#85 0x00000000 in ?? ()
#86 0x00000000 in ?? ()
#87 0x00000000 in ?? ()
#88 0x00000000 in ?? ()
#89 0x00000000 in ?? ()
#90 0x00000000 in ?? ()
#91 0x00000000 in ?? ()
#92 0x00000000 in ?? ()
#93 0x080a0ac8 in ?? ()
#94 0x080a0b48 in ?? ()
#95 0x00000000 in ?? ()
#96 0x00000000 in ?? ()
#97 0x00000000 in ?? ()
#98 0x00000000 in ?? ()
#99 0x080a1820 in ?? ()
#100 0x00000000 in ?? ()
#101 0x00000000 in ?? ()
#102 0x00000000 in ?? ()
#103 0x00000000 in ?? ()
#104 0xbf000000 in ?? ()
#105 0xb6f8a7d0 in ?? () from /usr/lib/libX11.so.6
#106 0x00000001 in ?? ()
#107 0x0805d028 in ?? ()
#108 0xbfc3cad8 in ?? ()
#109 0xbfc3cc28 in ?? ()
#110 0x00000001 in ?? ()
#111 0x0805d028 in ?? ()
#112 0xbfc3cc78 in ?? ()
#113 0x0804fc03 in ?? ()
#114 0x00000000 in ?? ()
#115 0x00000000 in ?? ()
#116 0x00000000 in ?? ()
#117 0x00000000 in ?? ()
#118 0x00000000 in ?? ()
#119 0x00000000 in ?? ()
#120 0x08050612 in vtable for QPtrList<char> ()
#121 0x00000001 in ?? ()
#122 0xb7cf33b1 in malloc () from /lib/tls/i686/cmov/libc.so.6

what can i do to improve this bug report so it can be properly solved¿?

[Andres Mujica (andres.mujica)]

Just after report this bug, another crash window popped up

(no d(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
`system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols.
(noebugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
`system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols.
(no.
..
.
.
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1231992608 (LWP 10130)]
[New Thread -1286804560 (LWP 10142)]
[New Thread -1278411856 (LWP 10141)]
[New Thread -1269830736 (LWP 10140)]
[New Thread -1261438032 (LWP 10139)]
[New Thread -1242240080 (LWP 10138)]
[New Thread -1250632784 (LWP 10137)]
(no debugging symbols found)
.
.
.
(no debugging symbols found)
[KCrash handler]
#6 0xffffe410 in __kernel_vsyscall ()
#7 0xb7ca99d1 in raise () from /lib/tls/i686/cmov/libc.so.6
#8 0xb7cab2e9 in abort () from /lib/tls/i686/cmov/libc.so.6
#9 0xb7cdd70a in __fsetlocking () from /lib/tls/i686/cmov/libc.so.6
#10 0xb7ce4e44 in free () from /lib/tls/i686/cmov/libc.so.6
#11 0xb7ce63b1 in malloc () from /lib/tls/i686/cmov/libc.so.6
#12 0xb7e964c5 in operator new () from /usr/lib/libstdc++.so.6
#13 0xb71a6ae9 in QString::setLength () from /usr/lib/libqt-mt.so.3
#14 0xb71a72b4 in QChar::decomposition () from /usr/lib/libqt-mt.so.3
#15 0xb71a76f1 in QString::arg () from /usr/lib/libqt-mt.so.3
#16 0xb6102469 in KatIndexerManager::currentFileString ()
   from /usr/lib/kde3/kded_katd.so
#17 0xb61025d1 in KatIndexerManager::customEvent ()
   from /usr/lib/kde3/kded_katd.so
#18 0xb6e8cbc7 in QObject::event () from /usr/lib/libqt-mt.so.3
#19 0xb6e26f80 in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3
#20 0xb6e27172 in QApplication::notify () from /usr/lib/libqt-mt.so.3
#21 0xb759817c in KApplication::notify () from /usr/lib/libkdecore.so.4
#22 0xb6db7db7 in QApplication::sendEvent () from /usr/lib/libqt-mt.so.3
#23 0xb6e284a3 in QApplication::sendPostedEvents ()
   from /usr/lib/libqt-mt.so.3
#24 0xb6e285aa in QApplication::sendPostedEvents ()
   from /usr/lib/libqt-mt.so.3
#25 0xb6dcaf4f in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3
#26 0xb6e3ecfb in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
#27 0xb6e3ec1e in QEventLoop::exec () from /usr/lib/libqt-mt.so.3
#28 0xb6e25c13 in QApplication::exec () from /usr/lib/libqt-mt.so.3
#29 0xb7ed137d in kdemain () from /usr/lib/libkdeinit_kded.so
#30 0xb7c95ec2 in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
#31 0x080483d1 in ?? ()

[Yuriy Kozlov (yuriy-kozlov)]

Are you still experiencing this problem in latest Dapper? I haven't had instability problems with KDE in a long time..

[Andres Mujica (andres.mujica)]

i haven't updated to dapper yet, i'm going to do it and report back about it.

I can say that the problem exists with kde 3.5.2-0ubuntu0breezy1

it is very random the behaviouras soon as i start my session the error popups twice, and no more... after a while (3-4hrs) it pop ups again.

i tend to think that is related somehow to KAT , but i have not managed to probe it...

anyway i'm going to upgrade to dapper, and see how it works.

Thanks

[Vitus (vitus-warpmail)]

Hello!

I had kded crashes with dapper as downloaded on easter sunday. Sorry, can't provide crash data. :-(
Last week I updated kde, kernel, mostly everything to the latest version available in universe and haven't expirienced any crashes ever since.

Sorry, a bit vague but I kept my thinkpad R51e at home today.

[Andres Mujica (andres.mujica)]

Hi, i'm still using breezy (is hard to update, cause is a production server)
but digging deeply on the problem i've found some mention to kat,

so i checked with another user, and him didn't have any issue as i described,
and he hasn't enabled kat.

so i remove it from the system and for about 2 days there hasn't been any kded
crashes as before.

so i want to redirect this bug to kubuntu's KAT responsible, how can i do it?

thanks!

El Jueves, 4 de Mayo de 2006 08:30, Vitus escribió:
> Hello!
>
> I had kded crashes with dapper as downloaded on easter sunday. Sorry,
> can't provide crash data. :-( Last week I updated kde, kernel, mostly
> everything to the latest version available in universe and haven't
> expirienced any crashes ever since.
>
> Sorry, a bit vague but I kept my thinkpad R51e at home today.

--
Andrés Mauricio Mujica Zalamea
Consultor Linux

SEAQ SERVICIOS CIA LTDA
www.seaq.com.co

Brindamos soluciones en el área de Conectividad (Cableado Estructurado, Redes
Inalámbricas, Networking) y en el área de Servicios IT (Seguridad,
Optimización, Administración, Linux, Antispam, Antivirus)

---

         CONFIDENCIAL. La información contenida en este e-mail es
         confidencial y sólo puede ser utilizada por el individuo o la
         compañía a la cual está dirigido. Si no es usted el destinatario
         autorizado, cualquier retención, difusión, distribución o copia
         de este mensaje está prohibida y es sancionada por la ley. Si
         por error recibe este mensaje, favor reenviar y borrar el
         mensaje recibido inmediatamente.

         CONFIDENTIAL. The information on this e-mail is intended to be
         confidential and only for the use of the individual or entity to
         whom it is addressed. If you are not the intended recipient, any
         retention, dissemination, distribution or copying of this
         message is strictly prohibited and sanctioned by law. If you
         receive this mail in error, please immediately send back and
         delete the message received

[Andres Mujica (andres.mujica)]

seems to be related to kat

[Jonathan Jesse (jjesse)]

Good evening,

I am working on cleaning up the bugs here assigned to the Kubuntu team and am wondering if you are still having problems with this bug and kded crashing frequently. I see the last update has not been in a long time and I'm trying to track down if you are still having pproblems. Can you please update this bug to reflect if you are currently having this problem and alsow hat version of Kubuntu you are using?

Thanks,

Jonathan

[Vitus (vitus-warpmail)]

Hello Jonathan,
after that update I mentioned in my first opst I never experienced kded crashes again. So I would say after Dapper Drake final (it was'nt released easter 2006, wasn't it) no more faults.

I'm still running Dapper Drake.

[Jonathan Jesse (jjesse)]

Marking this bug as fix released due to last post from the initial requestor