Bug 166585

Summary: Crash after IMAP connection doesn't get re-etablished
Product: [Unmaintained] kmail Reporter: Chris A <carnold5>
Component: IMAPAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED WORKSFORME    
Severity: crash CC: bjoern, christophe, finex
Priority: NOR Keywords: triaged
Version: 1.9.52   
Target Milestone: ---   
Platform: openSUSE   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Chris A 2008-07-15 00:30:09 UTC
Version:           1.3 (using KDE 4.0.80)
Installed from:    SuSE RPMs
OS:                Linux

*originally posted on opensuse and opensue-factory mailing list*

I use opensuse 11 x86_64 with kontact Version 1.3 from the opensuse 11
repo. Kontact use to work without this problem but since my workstation ip
changed, i get a constant error:
connection to the server <servername> was unexpectedly closed or timed out.
It will be established automatically if possible"
And in fact, some times it does get re-established but other times, kontact
crashes.

Some things i have done to try to fix this:
-tried just kmail->same problem
-delete existing account and recreated the email account->same problem
-other email clients work fine
-updated kontact from the opensuse repo->same problem
-uninstall kontact/kmail and its dependencies. then delete all
kmail/kontact folders. Reinstall kmail/kontact->same problem
-reformat hdd and reinstall opensuse 11 with kontact->same problem

I have also looked into the mail server logs for errors and found some java
errors that happen around the same time of the error on the workstation. I
restarted the mail server services and do not get that java error but still
get the error on the workstation/kontact. I use zimbra 5.0.4 OSS as a mail
server. I have asked over at their forums and they don't have an answer
either. Backtrace:
Application: Kontact (kontact), signal SIGSEGV
[?1034h(no debugging symbols found)
(no debugging symbols found)
{same as above}
[Thread debugging using libthread_db enabled]
[New Thread 0x7fcded19b700 (LWP 4105)]
(no debugging symbols found)
{same as above}
[KCrash handler]
#5  0x00007fcde7a3efd4 in QMutex::lock () from /usr/lib64/libQtCore.so.4
#6  0x00007fcde7b14b5e in QCoreApplication::postEvent ()
   from /usr/lib64/libQtCore.so.4
#7  0x00007fcdd5da3782 in ?? () from /usr/lib64/libkmailprivate.so.4
#8  0x00007fcdd5da5a2f in ?? () from /usr/lib64/libkmailprivate.so.4
#9  0x00007fcde7b264e0 in QMetaObject::activate ()
   from /usr/lib64/libQtCore.so.4
#10 0x00007fcde8a21a42 in KJob::result () from /usr/lib64/libkdecore.so.5
#11 0x00007fcde8a21db7 in KJob::emitResult () from /usr/lib64/libkdecore.so.5
#12 0x00007fcdea160ae0 in KIO::SimpleJob::slotFinished ()
   from /usr/lib64/libkio.so.5
#13 0x00007fcdea15e567 in KIO::SimpleJob::slotError ()
   from /usr/lib64/libkio.so.5
#14 0x00007fcdea15e762 in KIO::SimpleJob::qt_metacall ()
   from /usr/lib64/libkio.so.5
#15 0x00007fcde7b264e0 in QMetaObject::activate ()
   from /usr/lib64/libQtCore.so.4
#16 0x00007fcdea2018e6 in KIO::SlaveInterface::error ()
   from /usr/lib64/libkio.so.5
#17 0x00007fcdea204064 in KIO::SlaveInterface::dispatch ()
   from /usr/lib64/libkio.so.5
#18 0x00007fcdea201f22 in KIO::SlaveInterface::dispatch ()
   from /usr/lib64/libkio.so.5
#19 0x00007fcdea1f575e in KIO::Slave::gotInput () from /usr/lib64/libkio.so.5
#20 0x00007fcdea1f5a68 in KIO::Slave::qt_metacall ()
   from /usr/lib64/libkio.so.5
#21 0x00007fcde7b264e0 in QMetaObject::activate ()
   from /usr/lib64/libQtCore.so.4
#22 0x00007fcdea1358a1 in ?? () from /usr/lib64/libkio.so.5
#23 0x00007fcdea135f4a in KIO::Connection::qt_metacall ()
   from /usr/lib64/libkio.so.5
#24 0x00007fcde7b229ce in QObject::event () from /usr/lib64/libQtCore.so.4
#25 0x00007fcde42d992d in QApplicationPrivate::notify_helper ()
   from /usr/lib64/libQtGui.so.4
#26 0x00007fcde42dfcfa in QApplication::notify () from /usr/lib64/libQtGui.so.4
#27 0x00007fcde987966b in KApplication::notify () from /usr/lib64/libkdeui.so.5
#28 0x00007fcde7b14e9c in QCoreApplication::notifyInternal ()
   from /usr/lib64/libQtCore.so.4
#29 0x00007fcde7b157cb in QCoreApplicationPrivate::sendPostedEvents ()
   from /usr/lib64/libQtCore.so.4
#30 0x00007fcde435a277 in ?? () from /usr/lib64/libQtGui.so.4
#31 0x00007fcde7b137f2 in QEventLoop::processEvents ()
   from /usr/lib64/libQtCore.so.4
#32 0x00007fcde7b13985 in QEventLoop::exec () from /usr/lib64/libQtCore.so.4
#33 0x00007fcde7b15a25 in QCoreApplication::exec ()
   from /usr/lib64/libQtCore.so.4
#34 0x0000000000404a04 in _start ()
#0  0x00007fcde224a230 in nanosleep () from /lib64/libc.so.6
Comment 1 Christophe Marin 2008-07-15 14:34:13 UTC
Please read the following page and provide a useful backtrace for this crash : http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports
Comment 2 Thomas McGuire 2008-07-15 21:53:27 UTC
Yes, we need the debugging symbols for KMail, or else the backtrace is almost useless.
Comment 3 Chris A 2008-07-15 22:23:29 UTC
This is Chris (i created the bug above). How do i get the symbols for kmail? Run kmail and when it crashes, get a backtrace? Or do i use GBD to get the symbols?
Comment 4 Thomas McGuire 2008-07-15 22:32:17 UTC
> http://bugs.kde.org/show_bug.cgi?id=166585
Read the page Christophe linked here, it has a section for getting debug symbols for all distros. When those are installed, the backtrace will contain more information next time.
Comment 5 Chris A 2008-07-16 04:06:32 UTC
OK, so i used gdb but i have not been able to get kontact to crash. It still gives the connection to the server <servername> was unexpectedly closed or timed out error but has not crashed when ok'ing that error message. Here are the logs for that problem using gdb:

[New Thread 0x7fea5f99a700 (LWP 6363)]                                          
(no debugging symbols found)                                                    

kontact(6366)/kmail KMFolderIndex::updateIndexStreamPtr: utime( "/home/ELECTRICHENDRIX/carnold/.kde4/share/apps/kmail/imap/.460142714.directory/.Trash.index.ids" , 0) failed (KMMsgDict::getFolderIdsLocation( *this ))                        
kontact(6366)/kmail KMFolderImap::account: No parent folder found for "Electrichendrix"                                                                         

Program exited normally.
(gdb)                   
(gdb) kontact(6366): Failed to lock file "/var/tmp/kdecache-ELECTRICHENDRIX\carnold/kpc/kde-icon-cache.lock" , last result = 1                                  
kontact(6366): Failed to lock file "/var/tmp/kdecache-ELECTRICHENDRIX\carnold/kpc/kde-icon-cache.lock" , last result = 1                                        
kontact(6366): Failed to lock file "/var/tmp/kdecache-ELECTRICHENDRIX\carnold/kpc/kde-icon-cache.lock" , last result = 1                                        
kontact(6366): Failed to lock file "/var/tmp/kdecache-ELECTRICHENDRIX\carnold/kpc/kde-icon-cache.lock" , last result = 1                                        
kontact(6366): Failed to lock file "/var/tmp/kdecache-ELECTRICHENDRIX\carnold/kpc/kde-icon-cache.lock" , last result = 1                                        
kontact(6366): Failed to lock file "/var/tmp/kdecache-ELECTRICHENDRIX\carnold/kpc/kde-icon-cache.lock" , last result = 1                                        
kontact(6366): Failed to lock file "/var/tmp/kdecache-ELECTRICHENDRIX\carnold/kpc/kde-icon-cache.lock" , last result = 1                                        
kontact(6366): Failed to lock file "/var/tmp/kdecache-ELECTRICHENDRIX\carnold/kpc/kde-icon-cache.lock" , last result = 1                                        
kontact(6366): Failed to lock file "/var/tmp/kdecache-ELECTRICHENDRIX\carnold/kpc/kde-icon-cache.lock" , last result = 1                                        
kontact(6366): Failed to lock file "/var/tmp/kdecache-ELECTRICHENDRIX\carnold/kpc/kde-icon-cache.lock" , last result = 1                                        
kontact(6366): Failed to lock file "/var/tmp/kdecache-ELECTRICHENDRIX\carnold/kpc/kde-icon-cache.lock" , last result = 1                                        
kontact(6366): Failed to lock file "/var/tmp/kdecache-ELECTRICHENDRIX\carnold/kpc/kde-icon-cache.lock" , last result = 1                                        
kontact(6366): Failed to lock file "/var/tmp/kdecache-ELECTRICHENDRIX\carnold/kpc/kde-icon-cache.lock" , last result = 1                                        
kontact(6366): Failed to lock file "/var/tmp/kdecache-ELECTRICHENDRIX\carnold/kpc/kde-icon-cache.lock" , last result = 1                                        
kontact(6366): Failed to lock file "/var/tmp/kdecache-ELECTRICHENDRIX\carnold/kpc/kde-icon-cache.lock" , last result = 1
kontact(6366): Failed to lock file "/var/tmp/kdecache-ELECTRICHENDRIX\carnold/kpc/kde-icon-cache.lock" , last result = 1
kontact(6366)/kdeui (KAction) KActionCollection::setComponentData: this does not work on a KActionCollection containing actions!
kontact(6366)/kdeui (KAction) KActionCollection::setComponentData: this does not work on a KActionCollection containing actions!
kontact(6366)/kdeui (KAction) KActionCollection::setComponentData: this does not work on a KActionCollection containing actions!
kontact(6366)/kdeui (KAction) KActionCollection::setComponentData: this does not work on a KActionCollection containing actions!
kontact(6366)/kdeui (KAction) KActionCollection::setComponentData: this does not work on a KActionCollection containing actions!
kontact(6366)/kdeui (KAction) KActionCollection::setComponentData: this does not work on a KActionCollection containing actions!
kontact(6366)/kdeui (KAction) KActionCollection::setComponentData: this does not work on a KActionCollection containing actions!
kontact(6366)/kdeui (KAction) KActionCollection::setComponentData: this does not work on a KActionCollection containing actions!
kontact(6366)/kdeui (KAction) KActionCollection::setComponentData: this does not work on a KActionCollection containing actions!
kontact(6366)/kdeui (KAction) KActionCollection::setComponentData: this does not work on a KActionCollection containing actions!
kontact(6366)/kdeui (KAction) KActionCollection::setComponentData: this does not work on a KActionCollection containing actions!
kontact(6366)/kdeui (KAction) KActionCollection::setComponentData: this does not work on a KActionCollection containing actions!
kontact(6366)/kdeui (KAction) KActionCollection::setComponentData: this does not work on a KActionCollection containing actions!
QGpgMEProgressTokenMapper::map( "-&36" 63 )
QGpgMEProgressTokenMapper::map( "-&36" 63 )
QGpgMEProgressTokenMapper::map( "-" 63 )
QGpgMEProgressTokenMapper::map( "-" 63 )
kontact(6366)/kdeui (KAction) KActionCollection::setComponentData: this does not work on a KActionCollection containing actions!
kontact(6366)/kdeui (KAction) KActionCollection::setComponentData: this does not work on a KActionCollection containing actions!

I also deleted the existing account and tried an account of someone else's->same problem
Comment 6 Christophe Marin 2008-11-19 13:53:26 UTC
Does kmail still crash with KDE 4.1 ? 
Comment 7 FiNeX 2009-04-04 18:42:51 UTC
I'm not able to reproduce kmail crashes if I disconnect the PC from the IMAP server (I've brutally plugged out the network cable and I've tried to change the IP of the server too).
Comment 8 Björn Ruberg 2010-01-28 00:12:53 UTC
There have been already reports of kmail in the KDE 3.5 line crashing when having a choppy connection. I'm often using kmail since KDE 4.2 with unstable connections and can just report: no crashes