Summary: | Crash after IMAP connection doesn't get re-etablished | ||
---|---|---|---|
Product: | [Unmaintained] kmail | Reporter: | Chris A <carnold5> |
Component: | IMAP | Assignee: | 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
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 Yes, we need the debugging symbols for KMail, or else the backtrace is almost useless. 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? > 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.
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 Does kmail still crash with KDE 4.1 ? 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). 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 |