[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kmail-devel
Subject:    Bug#4206: marked as done (Kmail crashes on startup)
From:       owner () bugs ! kde ! org (Stephan Kulow)
Date:       2000-05-30 12:03:03
[Download RAW message or body]

Your message dated Tue, 30 May 2000 21:47:43 +1000
with message-id <00053021474300.26210@localhost.localdomain>
and subject line Bug#4206: Kmail crashes on startup
has caused the attached bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I'm
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Stephan Kulow
(administrator, KDE bugs database)

Received: (at submit) by bugs.kde.org; 29 May 2000 20:06:17 +0000
From soeren.siegmund@gmx.de Mon May 29 22:06:17 2000
Received: from rumms.uni-mannheim.de ([134.155.50.52]:48376 "EHLO
        rumms.uni-mannheim.de") by master.kde.org with ESMTP
        id <S742008AbQE2UGF>; Mon, 29 May 2000 22:06:05 +0200
Received: from rosalind.home.local (p3ppp232.rz.uni-mannheim.de [134.155.17.232])
        by rumms.uni-mannheim.de (8.9.3/8.9.3) with ESMTP id WAA07289
        for <submit@bugs.kde.org>; Mon, 29 May 2000 22:06:02 +0200 (MET DST)
Received: (from soeren@localhost)
        by rosalind.home.local (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) id UAA00485;
        Mon, 29 May 2000 20:40:51 +0200
Date:   Mon, 29 May 2000 20:40:51 +0200
From:   =?ISO-8859-1?Q?S=F6ren?= Siegmund (Gastnutzer) <soeren.siegmund@gmx.de>
Message-Id: <200005291840.UAA00485@rosalind.home.local>
To:     submit@bugs.kde.org
Subject: Kmail crashes on startup
Return-Path: <soeren.siegmund@gmx.de>
X-Orcpt: rfc822;submit@bugs.kde.org

Package: kmail
Version: 1.1.48 (KDE 1.90 Beta >= 20000517)
Severity: critical

I have no idea what causes this. kmail used to work for this account. 
Maybe an upgrade problem?


Here is a backtrace generated by DrKonki:
0x40e243d9 in __wait4 () from /lib/libc.so.6
#0  0x40e243d9 in __wait4 () from /lib/libc.so.6
#1  0x40e81618 in __DTOR_END__ () from /lib/libc.so.6
#2  0x406733ab in KCrash::defaultCrashHandler ()
   from /opt/kde/lib/libkdecore.so.3
#3  0x40dc2998 in __restore ()
    at ../sysdeps/unix/sysv/linux/i386/sigaction.c:127
#4  0x809933b in KMFolder::readMsg ()
#5  0x8099148 in KMFolder::getMsg ()
#6  0x8084ae8 in KMHeaders::getMsg ()
#7  0x80821e3 in KMHeaders::setMsgRead ()
#8  0x808061c in KMHeaders::setFolder ()
#9  0x8074bee in KMMainWin::folderSelected ()
#10 0x807d092 in KMFolderTree::folderSelected ()
#11 0x807b98b in KMFolderTree::doFolderSelected ()
#12 0x40ab969f in QListView::currentChanged ()
   from /usr/local/qt/lib/libqt.so.2
#13 0x409f2111 in QListView::setCurrentItem ()
   from /usr/local/qt/lib/libqt.so.2
#14 0x807096d in KMMainWin::KMMainWin ()
#15 0x80e91f0 in KMKernel::openReader ()
#16 0x80eac58 in KMKernel::action ()
#17 0x80eb2b2 in processArgs ()
#18 0x80eb711 in main ()
#19 0x40dbca5e in __libc_start_main () at ../sysdeps/generic/libc-start.c:93

[prev in list] [next in list] [prev in thread] [next in thread]