Version: 1.2.3 (using KDE 3.5.5, Debian Package 4:3.5.5a.dfsg.1-6 (4.0)) Compiler: Target: i486-linux-gnu OS: Linux (i686) release 2.6.18p4s I was using kontact and different parts from it: kmail,kaddressbook. Sometimes, kontact crashes without showing the kcrash handler. All I had is this .xsession-error snip: libGL warning: 3D driver claims to not support visual 0x4b libGL warning: 3D driver claims to not support visual 0x4b Try R300_SPAN_DISABLE_LOCKING env var if this hangs. WARNING: DCOPReply<>: cast to 'QStringList' error WARNING: DCOPReply<>: cast to 'QString' error X Error: BadMatch (invalid parameter attributes) 8 Major opcode: 156 Minor opcode: 6 Resource id: 0x4d QLayout::addChildLayout: layout already has a parent *** glibc detected *** malloc(): memory corruption (fast): 0x08af518a *** WeaverThreadLogger: thread (ID: 4) suspended. WeaverThreadLogger: thread (ID: 3) suspended. WeaverThreadLogger: thread (ID: 2) suspended. WeaverThreadLogger: thread (ID: 1) suspended. *** KMail got signal 6 (Crashing) DCOP aborting call from 'anonymous-26668' to 'kaddressbook' ERROR: Communication problem with kaddressbook, it probably crashed. FYI, the crashes I've been suffering lately are related to this bug: https://bugs.kde.org/show_bug.cgi?id=139652
Unfortunately we cannot do much with this amount of information. Do you have steps to reproduce, perhaps?
No feedback, hence closing.
There isn't any method I know to reproduce crashes I know in kontact. I understand and accept that there's nothing you can do with this. But I have the impression that this bug is still there, so I'll be keeping an eye on this anyway. I'll reopen if I see there's anything to be done with this.