Bug 142264 - Kontact / kmail crashes without showing the kcrash handler.
Summary: Kontact / kmail crashes without showing the kcrash handler.
Status: RESOLVED NOT A BUG
Alias: None
Product: kontact
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR normal with 10 votes (vote)
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-02-27 12:29 UTC by Raúl
Modified: 2007-07-03 00:32 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 Raúl 2007-02-27 12:29:06 UTC
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
Comment 1 Bram Schoenmakers 2007-05-15 12:35:01 UTC
Unfortunately we cannot do much with this amount of information. Do you have steps to reproduce, perhaps?
Comment 2 Bram Schoenmakers 2007-07-03 00:25:23 UTC
No feedback, hence closing.
Comment 3 Raúl 2007-07-03 00:32:11 UTC
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.