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

List:       kmail-devel
Subject:    Bug#29297: marked as done (kmail crash without user interaction) by Michael =?iso-8859-1?q?H=E4ckel?
From:       owner () bugs ! kde ! org (Stephan Kulow)
Date:       2001-07-24 7:33:06
[Download RAW message or body]

Your message with subj: Bug#29297: kmail crash without user interaction

fixed in CVS (kdelibs)


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; 19 Jul 2001 01:14:11 +0000
Received: (qmail 18124 invoked by uid 33); 19 Jul 2001 01:14:11 -0000
Date: 19 Jul 2001 01:14:11 -0000
Message-ID: <20010719011411.18123.qmail@master.kde.org>
To: submit@bugs.kde.org
Subject: kmail crash without user interaction
From: mike@twinpeaks.prc.com

Package:           kmail
Version:           July 18 CVS (using KDE 2.2.0 CVS/CVSup/Snapshot)
Severity:          normal
Installed from:    Compiled sources
Compiler:          2.96-85
OS:                Linux
OS/Compiler notes: More or less RH 7.1

If I start kmail, ldo normal checking of my email, then leave it alone, then it will \
sometimes crash several minutes later.  My setup has two remote secure IMAP accounts \
setup, and working normally in interactive use.

After looking through the code in kio, I noticed that the asserts check for valid \
values for host, port, etc. for (apparently) automatic checking of mail.  I looked in \
the control panel->network->email->incoming mail and found that the settings for port \
and use secure transport layer are both cleared.  If I set them, apply them, and quit \
control panel, and then reopen the control panel, they are cleared again (no values \
for either).

0x4116d519 in __wait4 () from /lib/i686/libc.so.6
#0  0x4116d519 in __wait4 () from /lib/i686/libc.so.6
#1  0x411dd9e4 in __DTOR_END__ () from /lib/i686/libc.so.6
#2  0x4093f671 in KCrash::defaultCrashHandler () at eval.c:41
#3  <signal handler called>
#4  0x410e0801 in __kill () from /lib/i686/libc.so.6
#5  0x410e05da in raise (sig=6) at ../sysdeps/posix/raise.c:27
#6  0x410e1d82 in abort () at ../sysdeps/generic/abort.c:88
#7  0x410d9cca in __assert_fail () at assert.c:60
#8  0x4047980e in KIO::Scheduler::slotScheduleCoSlave () at eval.c:41
#9  0x40bd923b in QObject::activate_signal ()
   from /usr/lib/qt-2.3.1/lib/libqt.so.2
#10 0x40c2eb42 in QTimer::timeout () from /usr/lib/qt-2.3.1/lib/libqt.so.2
#11 0x40c0ffab in QTimer::event () from /usr/lib/qt-2.3.1/lib/libqt.so.2

#12 0x40b89571 in QApplication::notify () from /usr/lib/qt-2.3.1/lib/libqt.so.2

#13 0x408aa171 in KApplication::notify () at eval.c:41
#14 0x40b56a36 in qt_activate_timers () from /usr/lib/qt-2.3.1/lib/libqt.so.2
#15 0x40b54774 in QApplication::processNextEvent ()
   from /usr/lib/qt-2.3.1/lib/libqt.so.2
#16 0x40b8b42c in QApplication::enter_loop ()
   from /usr/lib/qt-2.3.1/lib/libqt.so.2
#17 0x40b53f67 in QApplication::exec () from /usr/lib/qt-2.3.1/lib/libqt.so.2
#18 0x081845af in main () at eval.c:41
#19 0x410cf177 in __libc_start_main (main=0x8184284 <main>, argc=7, 
    ubp_av=0xbffffa9c, init=0x806578c <_init>, fini=0x81bded8 <_fini>, 
    rtld_fini=0x4000e184 <_dl_fini>, stack_end=0xbffffa8c)
    at ../sysdeps/generic/libc-start.c:129


(Submitted via bugs.kde.org)

_______________________________________________
Kmail Developers mailing list
Kmail@master.kde.org
http://master.kde.org/mailman/listinfo/kmail


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