Bug 235828 - kontact crashed after clicking on IMAP e-mail
Summary: kontact crashed after clicking on IMAP e-mail
Status: RESOLVED DUPLICATE of bug 219242
Alias: None
Product: kmail
Classification: Applications
Component: IMAP (show other bugs)
Version: 1.13.2
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-04-30 18:10 UTC by Johannes Schwall
Modified: 2010-08-09 01:00 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Johannes Schwall 2010-04-30 18:10:22 UTC
Application: kontact (4.4.2)
KDE Platform Version: 4.4.2 (KDE 4.4.2)
Qt Version: 4.6.2
Operating System: Linux 2.6.32-21-generic x86_64
Distribution: Ubuntu 10.04 LTS

-- Information about the crash:
kontact crashed when I clicked on an e-mail in an IMAP folder. The mail had previously been marked as replied to when I was working on another machine. There I had used evolution but was for some reason unable to send the reply. So the replied-to marker was set although the reply had not been sent.

 -- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
[Current thread is 1 (Thread 0x7fdfb0674780 (LWP 2422))]

Thread 2 (Thread 0x7fdf8d278710 (LWP 2525)):
#0  0x00007fdfad74ff53 in *__GI___poll (fds=<value optimized out>, nfds=<value optimized out>, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:87
#1  0x00007fdfa62854a9 in g_main_context_poll (context=0x166a250, block=<value optimized out>, dispatch=<value optimized out>, self=<value optimized out>)
    at /build/buildd/glib2.0-2.24.0/glib/gmain.c:2904
#2  g_main_context_iterate (context=0x166a250, block=<value optimized out>, dispatch=<value optimized out>, self=<value optimized out>) at /build/buildd/glib2.0-2.24.0/glib/gmain.c:2586
#3  0x00007fdfa62858fc in IA__g_main_context_iteration (context=0x166a250, may_block=1) at /build/buildd/glib2.0-2.24.0/glib/gmain.c:2654
#4  0x00007fdfaeb3a566 in QEventDispatcherGlib::processEvents (this=0xd22a50, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:414
#5  0x00007fdfaeb0f992 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149
#6  0x00007fdfaeb0fd6c in QEventLoop::exec (this=0x7fdf8d277d90, flags=) at kernel/qeventloop.cpp:201
#7  0x00007fdfaea19d59 in QThread::exec (this=<value optimized out>) at thread/qthread.cpp:487
#8  0x00007fdfaeaf0178 in QInotifyFileSystemWatcherEngine::run (this=0x166a6f0) at io/qfilesystemwatcher_inotify.cpp:248
#9  0x00007fdfaea1c775 in QThreadPrivate::start (arg=0x166a6f0) at thread/qthread_unix.cpp:248
#10 0x00007fdfa87fb9ca in start_thread (arg=<value optimized out>) at pthread_create.c:300
#11 0x00007fdfad75c69d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#12 0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7fdfb0674780 (LWP 2422)):
[KCrash Handler]
#5  0x00007fdf9648487f in KMCommand::slotStart (this=0x16cf000) at ../../kmail/kmcommands.cpp:261
#6  0x00007fdf9647cc66 in KMCommand::qt_metacall (this=0x16cf000, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff7a923ed0) at ./kmcommands.moc:92
#7  0x00007fdfaeb23e3f in QMetaObject::activate (sender=0x171fc30, m=<value optimized out>, local_signal_index=<value optimized out>, argv=0x1879908) at kernel/qobject.cpp:3293
#8  0x00007fdfaeb2b65f in QSingleShotTimer::timerEvent (this=0x171fc30) at kernel/qtimer.cpp:308
#9  0x00007fdfaeb20a63 in QObject::event (this=0x171fc30, e=0x7fff7a924630) at kernel/qobject.cpp:1212
#10 0x00007fdfadeca22c in QApplicationPrivate::notify_helper (this=0x6a17f0, receiver=0x171fc30, e=0x7fff7a924630) at kernel/qapplication.cpp:4300
#11 0x00007fdfaded06fb in QApplication::notify (this=0x7fff7a924a60, receiver=0x171fc30, e=0x7fff7a924630) at kernel/qapplication.cpp:4183
#12 0x00007fdfaf4f9526 in KApplication::notify (this=0x7fff7a924a60, receiver=0x171fc30, event=0x7fff7a924630) at ../../kdeui/kernel/kapplication.cpp:302
#13 0x00007fdfaeb1106c in QCoreApplication::notifyInternal (this=0x7fff7a924a60, receiver=0x171fc30, event=0x7fff7a924630) at kernel/qcoreapplication.cpp:704
#14 0x00007fdfaeb3dd42 in QCoreApplication::sendEvent (this=0x6a6ce0) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#15 QTimerInfoList::activateTimers (this=0x6a6ce0) at kernel/qeventdispatcher_unix.cpp:603
#16 0x00007fdfaeb3a824 in timerSourceDispatch (source=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:184
#17 0x00007fdfa62818c2 in g_main_dispatch (context=0x69c520) at /build/buildd/glib2.0-2.24.0/glib/gmain.c:1960
#18 IA__g_main_context_dispatch (context=0x69c520) at /build/buildd/glib2.0-2.24.0/glib/gmain.c:2513
#19 0x00007fdfa6285748 in g_main_context_iterate (context=0x69c520, block=<value optimized out>, dispatch=<value optimized out>, self=<value optimized out>)
    at /build/buildd/glib2.0-2.24.0/glib/gmain.c:2591
#20 0x00007fdfa62858fc in IA__g_main_context_iteration (context=0x69c520, may_block=1) at /build/buildd/glib2.0-2.24.0/glib/gmain.c:2654
#21 0x00007fdfaeb3a513 in QEventDispatcherGlib::processEvents (this=0x65ad70, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:412
#22 0x00007fdfadf7a46e in QGuiEventDispatcherGlib::processEvents (this=0x189f330, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:204
#23 0x00007fdfaeb0f992 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149
#24 0x00007fdfaeb0fd6c in QEventLoop::exec (this=0x7f9c20, flags=) at kernel/qeventloop.cpp:201
#25 0x00007fdfaf9ca411 in Akonadi::Control::Private::exec (this=0x7e18f0) at ../../akonadi/control.cpp:137
#26 0x00007fdfaf9cab75 in Akonadi::Control::start (parent=0x0) at ../../akonadi/control.cpp:233
#27 0x0000000000403e72 in main (argc=<value optimized out>, argv=<value optimized out>) at ../../../kontact/src/main.cpp:204

Possible duplicates by query: bug 235520, bug 234968, bug 234577, bug 234515, bug 233721.

Reported using DrKonqi
Comment 1 Björn Ruberg 2010-08-09 01:00:57 UTC

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