If you can reproduce the crash at will, can you read http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports and post a complete backtrace here? Thanks :)

Hi,

after installing some -dbg packets the crash produced the output below. Oh, by the way: I have a AMD 64 bit system.

Anwendung: KMail (kmail), Signal SIGSEGV
[Thread debugging using libthread_db enabled]
[New Thread 0x7fc5144456f0 (LWP 12863)]
[KCrash handler]
#5  0x0000000002acc040 in ?? ()
#6  0x00007fc51331252b in KMFolderImap::seenFlagToStatus (msg=0x2ae1670, 
    flags=129, newMsg=false)
    at /build/buildd/kdepim-4.1.3/kmail/kmfolderimap.cpp:1496
#7  0x00007fc5133126f0 in KMFolderImap::flagsToStatus (msg=0x2ae1670, 
    flags=129, newMsg=false, supportedFlags=2015)
    at /build/buildd/kdepim-4.1.3/kmail/kmfolderimap.cpp:1489
#8  0x00007fc513342ba6 in KMFolderCachedImap::slotGetMessagesData (
    this=0x23a2210, job=0x2a88450, data=@0x7fff1c487c10)
    at /build/buildd/kdepim-4.1.3/kmail/kmfoldercachedimap.cpp:1725
#9  0x00007fc51334522b in KMFolderCachedImap::qt_metacall (this=0x23a2210, 
    _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, 
    _a=0x7fff1c487850)
    at /build/buildd/kdepim-4.1.3/obj-x86_64-linux-gnu/kmail/kmfoldercachedimap.moc:195
#10 0x00007fc513f97134 in QMetaObject::activate ()
   from /usr/lib/libQtCore.so.4
#11 0x00007fc50c6dfc34 in KIO::TransferJob::data (this=0x2ae1670, 
    _t1=0x2a88450, _t2=<value optimized out>)
    at /build/buildd/kde4libs-4.1.3/obj-x86_64-linux-gnu/kio/jobclasses.moc:356
#12 0x00007fc50c6ea2b9 in KIO::TransferJob::qt_metacall (this=0x2a88450, 
    _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, 
    _a=0x7fff1c487980)
    at /build/buildd/kde4libs-4.1.3/obj-x86_64-linux-gnu/kio/jobclasses.moc:337
#13 0x00007fc513f97134 in QMetaObject::activate ()
   from /usr/lib/libQtCore.so.4
#14 0x00007fc50c79df62 in KIO::SlaveInterface::data (this=0x2ae1670, 
    _t1=<value optimized out>)
    at /build/buildd/kde4libs-4.1.3/obj-x86_64-linux-gnu/kio/slaveinterface.moc:136
#15 0x00007fc50c7a1728 in KIO::SlaveInterface::dispatch (this=0x2a98090, 
    _cmd=100, rawdata=<value optimized out>)
    at /build/buildd/kde4libs-4.1.3/kio/kio/slaveinterface.cpp:162
#16 0x00007fc50c79e462 in KIO::SlaveInterface::dispatch (this=0x2a98090)
    at /build/buildd/kde4libs-4.1.3/kio/kio/slaveinterface.cpp:90
#17 0x00007fc50c78f4b3 in KIO::Slave::gotInput (this=0x2a98090)
    at /build/buildd/kde4libs-4.1.3/kio/kio/slave.cpp:322
#18 0x00007fc50c791bd8 in KIO::Slave::qt_metacall (this=0x2a98090, 
    _c=QMetaObject::InvokeMetaMethod, _id=44866496, _a=0x7fff1c487d70)
    at /build/buildd/kde4libs-4.1.3/obj-x86_64-linux-gnu/kio/slave.moc:75
#19 0x00007fc513f97134 in QMetaObject::activate ()
   from /usr/lib/libQtCore.so.4
#20 0x00007fc50c6b3a50 in KIO::ConnectionPrivate::dequeue (this=0x2aaebc0)
    at /build/buildd/kde4libs-4.1.3/kio/kio/connection.cpp:82
#21 0x00007fc50c6b3b8a in KIO::Connection::qt_metacall (this=0x2aaeee0, 
    _c=QMetaObject::InvokeMetaMethod, _id=44866496, _a=0x2acab50)
    at /build/buildd/kde4libs-4.1.3/obj-x86_64-linux-gnu/kio/connection.moc:72
#22 0x00007fc513f91da5 in QObject::event () from /usr/lib/libQtCore.so.4
#23 0x00007fc511d70c3d in QApplicationPrivate::notify_helper ()
   from /usr/lib/libQtGui.so.4
#24 0x00007fc511d789ba in QApplication::notify () from /usr/lib/libQtGui.so.4
#25 0x00007fc512916fcb in KApplication::notify (this=0x7fff1c4888e0, 
    receiver=0x2aaeee0, event=0x2acb8c0)
    at /build/buildd/kde4libs-4.1.3/kdeui/kernel/kapplication.cpp:311
#26 0x00007fc513f82d61 in QCoreApplication::notifyInternal ()
   from /usr/lib/libQtCore.so.4
#27 0x00007fc513f839fa in QCoreApplicationPrivate::sendPostedEvents ()
   from /usr/lib/libQtCore.so.4
#28 0x00007fc513fab4d3 in ?? () from /usr/lib/libQtCore.so.4
#29 0x00007fc510a5dd3b in g_main_context_dispatch ()
   from /usr/lib/libglib-2.0.so.0
#30 0x00007fc510a6150d in ?? () from /usr/lib/libglib-2.0.so.0
#31 0x00007fc510a616cb in g_main_context_iteration ()
   from /usr/lib/libglib-2.0.so.0
#32 0x00007fc513fab15f in QEventDispatcherGlib::processEvents ()
   from /usr/lib/libQtCore.so.4
#33 0x00007fc511e02a6f in ?? () from /usr/lib/libQtGui.so.4
#34 0x00007fc513f81682 in QEventLoop::processEvents ()
   from /usr/lib/libQtCore.so.4
#35 0x00007fc513f8180d in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#36 0x00007fc513f83cbd in QCoreApplication::exec ()
   from /usr/lib/libQtCore.so.4
#37 0x0000000000402fcb in main (argc=<value optimized out>, 
    argv=<value optimized out>)
    at /build/buildd/kdepim-4.1.3/kmail/main.cpp:146
#0  0x00007fc5113b75f0 in __nanosleep_nocancel () from /lib/libc.so.6

(In reply to comment #0)

> One diconnected IMAP folder. Nothing else.
> 
> 1) Start kmail
> 2) Press "Get Mail"
> 3) kmail starts to sync to server
> 4) and crashes with "The application Kontact (kontact) crashed and caused the
> signal 11 (SIGSEGV)."


i'm getting a similar error when connecting to a large IMAP folder (gmail, 8.000+ messages), using:

KMail: 1.10.92
KDE 4.1.87 (unstable)
openSUSE 11.0. 

(this did not happen with KDE 4.1 stable.)

opening smaller IMAP folders Kmail doesn't crash. it's also noteworthy, perhaps, that my internet connection is pretty slow (256 kb/s) and often unreliable. 

i don't have any extra debugging packages installed, and the KDE crash handler claims it can't generate a useful report. still, the following lines make me think it's got something to do with things not happening fast enough for the KDE interface:

0xffffe430 in __kernel_vsyscall ()
[Current thread is 0 (process 3344)]

Thread 1 (Thread 0xb41036d0 (LWP 3344)):
#0 0xffffe430 in __kernel_vsyscall ()
#1 0xb5fcc0c6 in nanosleep () from /lib/libc.so.6
#2 0xb5fcbeae in sleep () from /lib/libc.so.6
#3 0xb7f82520 in ?? () from /usr/lib/libkdeui.so.5
#4 0xb7f82ee4 in KCrash::defaultCrashHandler () from /usr/lib/libkdeui.so.5
#5 <signal handler called>

if you think it'll help i can follow the instructions above, install some debugging packages, and reproduce the error--tomorrow.

*** Bug 179825 has been marked as a duplicate of this bug. ***

I have the same error with kmail from KDE 4.1.96 which is shown as version 1.11.0.

The strange thing about it is that it only crashs on one of my imap accounts. Its the one from my university (gmail is just fine). Additionally I have figured out that it only happens when I open the inbox. It works perfectly for every other folder in this account.

This may be related to bug 179765, but it's a different backtrace.

@Michael: Can you still reproduce with a very recent version of kmail? I'd prefer testing with a version more recent than kde 4.2 rc1 if possible.

@Jack Black and phanisvara das: Is the backtrace that you get the same as in comment 2 or the same as in bug 179765? In any case, bug 179765 has been fixed after kde 4.2 rc1, so this may just work with a very recent version... Please retest if you can.

Thanks.

I'm not completely sure if its the same or not. But it looks like those bugs that have been fixed. Sadly my distro does not provide any debug packages for kde 4.2 rc1 so I guess my backtrace is pretty useless. Ill try to test the recent version.

Thank you

> @Jack Black and phanisvara das: Is the backtrace that you get the same as in
> comment 2 or the same as in bug 179765? In any case, bug 179765 has been fixed
> after kde 4.2 rc1, so this may just work with a very recent version... Please
> retest if you can.

my backtrace claimed it was useless, but nevertheless looked very similar to the one in bug 179765.

------------
This backtrace appears to be of no use.
This is probably because your packages are built in a way which prevents creation of proper backtraces, or the stack frame was seriously corrupted in the crash.
------------

after ugrading to a more recent KDE version (Version 4.2.60 (KDE 4.2.60 (KDE 4.3 >= 20090116)) "release 1.5")) though, the crash doesn't happen anymore, everything works fine. must have been the bug fixed after rc1, therefore.

thanks, phani.

So this bug has been quiet for nearly two months now. Is anybody still able to reproduce that crash with a recent version?

Works for me now. I have KMail 1.10.4
Michael.

same here. i haven't had any trouble since upgrading to KDE 4.3; using KMail 1.11.90 now.

phani.

Marking as WORKSFORME as the reporter and many other people confirmed that this doesn't cause a crash anymore. Thanks