Bug 179719 - i connect to imap and it crashed while downloading folders.
Summary: i connect to imap and it crashed while downloading folders.
Status: RESOLVED DUPLICATE of bug 179765
Alias: None
Product: kmail
Classification: Unmaintained
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-01-05 15:50 UTC by Mathieu Jobin
Modified: 2009-03-19 00:37 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mathieu Jobin 2009-01-05 15:50:53 UTC
Version:           unknown (using 4.1.85 (KDE 4.1.85 (KDE 4.2 Beta2)), Kubuntu packages)
Compiler:          cc
OS:                Linux (i686) release 2.6.27-9-generic

title says it all

i connected to IMAP and it crashed while downloading folders. 

the 150+ message boxes also made kwin slow down until my system was unusable. I have been patient simply until kmail crashed.

I wanted to attached a backtrace, but generating the backtrace actually made drkonqi crash itself.
Comment 1 Dario Andres 2009-01-05 22:25:27 UTC
Well.. if DrKonqui is crashing you can using GDB directly:

In a Konsole window
- Run "gdb kmail"
- Type "set logging on" and press Return (this will log everything to "gdb.txt", ensure that you don't have another file with the same name)
- Type "run" and press Return
KMail will open
- Reproduce the crash
KMail will crash.
- Return to the Konsole/GDB window
- Type "bt full", press Return
- Press Return until all the backtrace is loaded (you can hold Return for a while to avoid pressing it every 1 second)

Then paste the contents of the gdb.txt file here (or paste the firsts line, and then attach the full file)
Comment 2 FiNeX 2009-01-06 18:53:43 UTC
Probably a dup of bug #179825
Comment 3 Christophe Marin 2009-02-14 19:18:27 UTC
Let's assume it's a dup of bug 179765 which is fixed in KDE 4.2

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