[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 113329] KMail crash on startup
From:       Elan "Ruusamäe" <glen () delfi ! ee>
Date:       2006-08-29 17:16:47
Message-ID: 20060829171647.1368.qmail () ktown ! kde ! org
[Download RAW message or body]

------- 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=113329         




------- Additional Comments From glen delfi ee  2006-08-29 19:16 -------
my setup is 1 disconnected imap, 1 online imap, but i don't think the disconnected \
imap has role here as my default startup folder was online imap. changing the folder \
to open at startup "resolved" the crash. the online imap is over ssl.

it is odd that this bug has so many duplicates and reports but no actual words from \
developers who actually are willing to fix anything ;(

here's top from my kcrashdialog. note i avoided the crash by changing default startup \
folder. but if i "enter" the broke imap account the backtrace is:

Using host libthread_db library "/lib/tls/libthread_db.so.1".
[KCrash handler]
#6  0xb7294735 in QMap<KPIM::ProgressItem*, bool>::detach (this=0x887aa88)
    at /usr/include/qt/qmap.h:739
#7  0xb7294137 in QMap<KPIM::ProgressItem*, bool>::remove (this=0x887aa88, 
    k= 0xbfa63eb4) at /usr/include/qt/qmap.h:831
#8  0xb7291e21 in KPIM::ProgressItem::removeChild (this=0x887aa48, 
    kiddo=0x866dce8) at progressmanager.cpp:74
#9  0xb7291d9d in KPIM::ProgressItem::setComplete (this=0x866dce8)
    at progressmanager.cpp:60
#10 0xb7cd8393 in KMail::ImapAccountBase::removeJob (this=0x83274f0, 
    it= 0xbfa63f40) at imapaccountbase.cpp:1174
#11 0xb7c267d6 in KMail::ListJob::slotListResult (this=0x8686328, 
    job=0x86825b0) at listjob.cpp:183
#12 0xb7c27093 in KMail::ListJob::qt_invoke (this=0x8686328, _id=2, 
    _o=0xbfa64010) at listjob.moc:128

i'd be happy to provide more information to get this ProgressItem related bug \
resolved finally (i've kept the corrupted imap account for this purpose).


[prev in list] [next in list] [prev in thread] [next in thread]