Bug 53714 - kmail crashed after adding IMAP account, and it just keeps crashing everytime im trying to start it
Summary: kmail crashed after adding IMAP account, and it just keeps crashing everytime...
Status: RESOLVED DUPLICATE of bug 53889
Alias: None
Product: kmail
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Slackware Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-01-31 06:07 UTC by Mikko Rinne
Modified: 2007-09-14 12:17 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 Mikko Rinne 2003-01-31 06:07:35 UTC
Version:            (using KDE KDE 3.1)
Installed from:    Slackware Packages
OS:          Linux

I added new IMAP account, and after that it simply stuckked, and now it crashes everytime when i'm starting kmail, and entering password for the IMAP account.

Here's the backtrace error log it gaves me:

[New Thread 1024 (LWP 8778)]
0x4131b239 in __wait4 () at __wait4:-1
        in __wait4
#0  0x4131b239 in __wait4 () at __wait4:-1
#1  0x41395e58 in __DTOR_END__ () from /lib/libc.so.6
#2  0x411ec7b2 in waitpid (pid=32330, stat_loc=0x0, options=0)
    at wrapsyscall.c:173
#3  0x409d97ac in KCrash::defaultCrashHandler ()
   from /opt/kde/lib/libkdecore.so.4
#4  0x411ea144 in pthread_sighandler (signo=11, ctx=
      {gs = 0, __gsh = 0, fs = 0, __fsh = 0, es = 43, __esh = 0, ds = 43, __dsh = 0, edi = 137598256, esi = 3221220444, ebp = 3221220476, esp = 3221220388, ebx = 1, edx = 3221220252, ecx = 3, eax = 0, trapno = 14, err = 4, eip = 135093869, cs = 35, __csh = 0, eflags = 66199, esp_at_signal = 3221220388, ss = 43, __ssh = 0, fpstate = 0xbfffe9a8, oldmask = 2147483648, cr2 = 40}) at signals.c:97
#5  <signal handler called>
#6  0x080d5e6d in KMFolderTree::addDirectory ()
#7  0x080d57b1 in KMFolderTree::reload ()
#8  0x080d47d8 in KMFolderTree::KMFolderTree ()
#9  0x080918a7 in KMMainWin::createWidgets ()
#10 0x0808e8a7 in KMMainWin::KMMainWin ()
#11 0x0818bbc2 in KMKernel::openReader ()
#12 0x0818eaff in KMKernel::action ()
#13 0x0819120f in KMailApplication::newInstance ()
#14 0x409f0549 in KUniqueApplication::processDelayed ()
   from /opt/kde/lib/libkdecore.so.4
#15 0x409f08e9 in KUniqueApplication::qt_invoke ()
   from /opt/kde/lib/libkdecore.so.4
#16 0x40d0c1c4 in QObject::activate_signal ()
   from /usr/lib/qt-3.1.1/lib/libqt-mt.so.3
#17 0x40f8de2a in QSignal::signal () from /usr/lib/qt-3.1.1/lib/libqt-mt.so.3
#18 0x40d22294 in QSignal::activate () from /usr/lib/qt-3.1.1/lib/libqt-mt.so.3
#19 0x40d27983 in QSingleShotTimer::event ()
   from /usr/lib/qt-3.1.1/lib/libqt-mt.so.3
#20 0x40cb772a in QApplication::internalNotify ()
   from /usr/lib/qt-3.1.1/lib/libqt-mt.so.3
#21 0x40cb7536 in QApplication::notify ()
   from /usr/lib/qt-3.1.1/lib/libqt-mt.so.3
#22 0x4096a3db in KApplication::notify () from /opt/kde/lib/libkdecore.so.4
#23 0x40c99495 in QEventLoop::activateTimers ()
   from /usr/lib/qt-3.1.1/lib/libqt-mt.so.3
#24 0x40c7b354 in QEventLoop::processEvents ()
   from /usr/lib/qt-3.1.1/lib/libqt-mt.so.3
#25 0x40cc98d3 in QEventLoop::enterLoop ()
   from /usr/lib/qt-3.1.1/lib/libqt-mt.so.3
#26 0x40cc9822 in QEventLoop::exec () from /usr/lib/qt-3.1.1/lib/libqt-mt.so.3
#27 0x40cb78ad in QApplication::exec ()
   from /usr/lib/qt-3.1.1/lib/libqt-mt.so.3
#28 0x081920e3 in main ()
#29 0x4129117d in __libc_start_main (main=0x8191628 <main>, argc=7,
    ubp_av=0xbffff7b4, init=0x8071318 <_init>, fini=0x81c23f0 <_fini>,
    rtld_fini=0x4000a534 <_dl_fini>, stack_end=0xbffff7ac)
    at ../sysdeps/generic/libc-start.c:129
Comment 1 Carsten Burghardt 2003-02-03 19:49:30 UTC
As a workaround you can try to remove the account-entry from your kmailrc (~/.kde/share/config/kmailrc) and the local cache (~/.kde/share/apps/kmail/imap/<accountname>) and start once again. Let kmail remember the password, there seems to be a bug.

*** This bug has been marked as a duplicate of 53889 ***