Version: 1.5 (using KDE KDE 3.1) Installed from: SuSE RPMs OS: Linux I have two IMAP-Accounts, one on my router/server, another at the mail-server of my university. Not everytime, but often KMail crashes after entering the two passwords with SIGSEGV, before the main-window opens. I think it happens mostly when I start KMail the first time after loading KDE.
*** Bug 53714 has been marked as a duplicate of this bug. ***
*** Bug 53720 has been marked as a duplicate of this bug. ***
Subject: Fix for bug 53889 This patch should do the trick. The folder selection "bounced" and therefore initiated some problems. Took me the whole evening to find and fix.... Regards, Carsten Created an attachment (id=878) password.diff
Subject: RE: Kmail crashes after authorization-dialog Hi, Thanks, i'll try it as soon as i manage to get in to work, and reply what happened :) --- http://www.clanbase.com ClanBase Crew / CS Crew blackop@clanbase.com -----Original Message----- From: owner@bugs.kde.org [mailto:owner@bugs.kde.org] On Behalf Of Carsten Burghardt Sent: 4. helmikuuta 2003 0:55 To: blackop@clanbase.com Subject: [Bug 53889] Kmail crashes after authorization-dialog ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is. http://bugs.kde.org/show_bug.cgi?id=53889 ------- Additional Comments From cb@magic-shop.de 2003-02-03 23:55 ------- Subject: Fix for bug 53889 This patch should do the trick. The folder selection "bounced" and therefore initiated some problems. Took me the whole evening to find and fix.... Regards, Carsten Created an attachment (id=878) --> (http://bugs.kde.org/attachment.cgi?id=878&action=view) password.diff
Subject: Re: Kmail crashes after authorization-dialog Am Montag, 3. Februar 2003 23:55 schriebst Du: > Subject: Fix for bug 53889 > > This patch should do the trick. > The folder selection "bounced" and therefore initiated some problems. Took > me the whole evening to find and fix.... > > Regards, > > Carsten Hi! KMail still crashes after patching. A work-around is to cancel the autorization-dialog and open the IMAP-Servers when KMail is fully started. Mathias
*** Bug 54633 has been marked as a duplicate of this bug. ***
Here is a crash report for this bug (gcc 3.2, 2.1_BRANCH, updated 12/2/2003): [New Thread 1024 (LWP 21588)] 0x415c68c9 in wait4 () from /lib/libc.so.6 #0 0x415c68c9 in wait4 () from /lib/libc.so.6 #1 0x41641c90 in __DTOR_END__ () from /lib/libc.so.6 #2 0x41421a93 in waitpid () from /lib/libpthread.so.0 #3 0x40b63847 in KCrash::defaultCrashHandler(int) (sig=11) at /mnt/KDE/kde-cvs/kdelibs/kdecore/kcrash.cpp:235 #4 0x4141f12b in pthread_sighandler () from /lib/libpthread.so.0 #5 <signal handler called> #6 0x00000011 in ?? () #7 0x080f0571 in KMFolderTree::reload(bool) (this=0xbfffd91c, openFolders=false) at /mnt/KDE/kde-cvs/kdenetwork/kmail/kmfoldertree.cpp:381 #8 0x080ef4fc in KMFolderTree (this=0x82cd4f8, parent=0x83a2cb0, name=0x82203a6 "folderTree") at /mnt/KDE/kde-cvs/kdenetwork/kmail/kmfoldertree.cpp:116 #9 0x080962e1 in KMMainWin::createWidgets() (this=0x8276b98) at /mnt/KDE/kde-cvs/kdenetwork/kmail/kmmainwin.cpp:571 #10 0x08092d66 in KMMainWin (this=0x8276b98) at /mnt/KDE/kde-cvs/kdenetwork/kmail/kmmainwin.cpp:94 #11 0x081d9f39 in KMKernel::openReader() (this=0xbfffe920) at /mnt/KDE/kde-cvs/kdenetwork/kmail/kmkernel.cpp:177 #12 0x081ddd39 in KMKernel::action(bool, bool, QString const&, QString const&, Q String const&, QString const&, QString const&, KURL const&, KURL::List const&) (this=0xbfffe920, check=false, to=@0xbfffe2d0, cc=@0xbfffe2c0, bcc=@0xbfffe2b0, subj=@0xbfffe2a0, body=@0xbfffe290, messageFile=@0xbfffe260, attachURLs=@0xbfffe250) at /mnt/KDE/kde-cvs/kdenetwork/kmail/kmkernel.cpp:979 #13 0x081e0713 in KMailApplication::newInstance() (this=0xbfffeae0) at /mnt/KDE/kde-cvs/kdenetwork/kmail/kmkernel.h:98 #14 0x40b83345 in KUniqueApplication::processDelayed() (this=0xbfffeae0) at /mnt/KDE/kde-cvs/kdelibs/kdecore/kuniqueapplication.cpp:363 #15 0x40b83699 in KUniqueApplication::qt_invoke(int, QUObject*) ( this=0xbfffeae0, _id=10, _o=0xbfffe470) at kuniqueapplication.moc:86 #16 0x40ed0f43 in QObject::activate_signal(QConnectionList*, QUObject*) () from /opt/qt-3.1/lib/libqt-mt.so.3 #17 0x41197c57 in QSignal::signal(QVariant const&) () from /opt/qt-3.1/lib/libqt-mt.so.3 #18 0x40ee9555 in QSignal::activate() () from /opt/qt-3.1/lib/libqt-mt.so.3 #19 0x40eeff6c in QSingleShotTimer::event(QEvent*) () from /opt/qt-3.1/lib/libqt-mt.so.3 #20 0x40e753c2 in QApplication::internalNotify(QObject*, QEvent*) () from /opt/qt-3.1/lib/libqt-mt.so.3 #21 0x40e74fb2 in QApplication::notify(QObject*, QEvent*) () from /opt/qt-3.1/lib/libqt-mt.so.3 #22 0x40ad9f2f in KApplication::notify(QObject*, QEvent*) (this=0xbfffeae0, receiver=0x839d4b8, event=0xbfffe740) at /mnt/KDE/kde-cvs/kdelibs/kdecore/kapplication.cpp:453 #23 0x40e50f1c in QEventLoop::activateTimers() () from /opt/qt-3.1/lib/libqt-mt.so.3 #24 0x40e3075c in QEventLoop::processEvents(unsigned) () from /opt/qt-3.1/lib/libqt-mt.so.3 #25 0x40e8827b in QEventLoop::enterLoop() () from /opt/qt-3.1/lib/libqt-mt.so.3 #26 0x40e88124 in QEventLoop::exec() () from /opt/qt-3.1/lib/libqt-mt.so.3 #27 0x40e75610 in QApplication::exec() () from /opt/qt-3.1/lib/libqt-mt.so.3 #28 0x081e13a5 in main (argc=1, argv=0xbfffec74) at /opt/kde3/include/kapplication.h:178 #29 0x415414a2 in __libc_start_main () from /lib/libc.so.6
Here is the newest (strange) crash report for this bug (gcc 3.2, 3.1_BRANCH, updated 5/3/2003): [New Thread 1024 (LWP 23951)] 0x4172e8c9 in wait4 () from /lib/libc.so.6 #0 0x4172e8c9 in wait4 () from /lib/libc.so.6 #1 0x417a9c90 in __DTOR_END__ () from /lib/libc.so.6 #2 0x41589a93 in waitpid () from /lib/libpthread.so.0 #3 0x40c9f502 in KCrash::defaultCrashHandler(int) (sig=0) at /mnt/KDE/kde-cvs/kdelibs/kdecore/kcrash.cpp:235
*** Bug 56626 has been marked as a duplicate of this bug. ***
Subject: KDE_3_1_BRANCH: kdenetwork/kmail CVS commit by burghard: Fix bug 53889. Obviously a timing-problem, reload was called too often. CCMAIL: 53889-done@bugs.kde.org M +3 -3 kmfoldertree.cpp 1.209.2.5 --- kdenetwork/kmail/kmfoldertree.cpp #1.209.2.4:1.209.2.5 @@ -101,7 +101,4 @@ KMFolderTree::KMFolderTree( QWidget *par header()->setStretchEnabled( true, namecol ); - // connect - connectSignals(); - // popup to switch columns header()->setClickEnabled(true); @@ -115,4 +112,7 @@ KMFolderTree::KMFolderTree( QWidget *par // add the folders reload(); + + // connect + connectSignals(); // read the config
The patch has solved only a part of the problem, or there is another bug. It's really great that my users can use kmail again - keep on with your good work. Situation: two or more imap folder on two or more imap server. You fill out all authorization dialogs -> all is fine You click on cancel at one of the dialogs -> crash kde3.1_branch updated 3.april, suse 8.1, gcc 3.2, imap/s, backtrace: [New Thread 1024 (LWP 9641)] 0x417518c9 in wait4 () from /lib/libc.so.6 #0 0x417518c9 in wait4 () from /lib/libc.so.6 #1 0x417ccc90 in __DTOR_END__ () from /lib/libc.so.6 #2 0x415aca93 in waitpid () from /lib/libpthread.so.0 #3 0x40c9f702 in KCrash::defaultCrashHandler(int) (sig=0) at /mnt/KDE/kde-cvs/kdelibs/kdecore/kcrash.cpp:235
Ralated to this: if one has more than 1 imap account, requiring password authentication (password not stored in config file), kmail asked for "a" password. However kmail does not provide information for which account it wants to obtain a password. Should I open a new bug report for this or is this sufficient?
Subject: KDE_3_1_BRANCH: kdenetwork/kmail CVS commit by burghard: Fix crash when the imap auth dialog is cancelled. It's a bit nasty that the KMImapJob deletes itself if there is no connection. CCMAIL: 53889@bugs.kde.org M +4 -0 kmmainwin.cpp 1.541.2.9 --- kdenetwork/kmail/kmmainwin.cpp #1.541.2.8:1.541.2.9 @@ -1632,4 +1632,8 @@ void KMMainWin::slotMsgSelected(KMMessag !msg->isComplete()) { + // make sure we get a connection, otherwise KMImapJob will delete itself + KMAcctImap* acct = (static_cast<KMFolderImap*>(msg->parent()))->account(); + if ( !acct->makeConnection() ) + return; mMsgView->clear(); KMImapJob *job = new KMImapJob(msg);
@Richard: this is not correct, the very first line of the authorization dialog mentiones the account.
Carsten, you're very right. I did not read the dialogue carefull enough.
yeah, no crash anymore. Great work.