[Bug 252408] New: Accessing email on an imap server elsewhere causes local kmail instance to eventually crash.

[Con Kolivas]

https://bugs.kde.org/show_bug.cgi?id=252408

           Summary: Accessing email on an imap server elsewhere causes
                    local kmail instance to eventually crash.
           Product: kmail
           Version: 1.13.5
          Platform: Debian testing
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: crash
          Priority: NOR
         Component: general
        AssignedTo: kdepim-bugs at kde.org
        ReportedBy: kde at kolivas.org


Application: kmail (1.13.5)
KDE Platform Version: 4.4.5 (KDE 4.4.5)
Qt Version: 4.6.3
Operating System: Linux 2.6.35.5-ck1 x86_64
Distribution: Debian GNU/Linux testing (squeeze)

-- Information about the crash:
Leaving kmail open locally regularly checking an imap account and then
accessing that same imap account from another PC makes the local kmail fail to
ever update the inbox. It keeps checking indefinitely and never successfully
reattaches to the imap account (after the other machine has stopped accessing
the imap account). The local kmail instance does one of two things: it either
just makes each email disappear as I click on it leaving an apparently empty
inbox, or it fails to ever show the email. On the latter scenario, if I keep
trying to do something to the email (open it, reply, forward) it will
eventually crash and the crash is the attached one.

The crash can be reproduced some of the time.

 -- Backtrace:
Application: KMail (kmail), signal: Segmentation fault
The current source language is "auto; currently asm".
[Current thread is 1 (Thread 0x7f97f9e2f760 (LWP 3725))]

Thread 2 (Thread 0x7f97d4eb1710 (LWP 17293)):
#0  0x00007f97f68fe113 in *__GI___poll (fds=<value optimized out>, nfds=<value
optimized out>, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:87
#1  0x00007f97ee5002c9 in ?? () from /lib/libglib-2.0.so.0
#2  0x00007f97ee50071c in g_main_context_iteration () from
/lib/libglib-2.0.so.0
#3  0x00007f97f7f46726 in QEventDispatcherGlib::processEvents (this=0x1053360,
flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:414
#4  0x00007f97f7f1b9e2 in QEventLoop::processEvents (this=<value optimized
out>, flags=) at kernel/qeventloop.cpp:149
#5  0x00007f97f7f1bdbc in QEventLoop::exec (this=0x7f97d4eb0de0, flags=) at
kernel/qeventloop.cpp:201
#6  0x00007f97f7e2b77b in QThread::exec (this=<value optimized out>) at
thread/qthread.cpp:487
#7  0x00007f97f7efc338 in QInotifyFileSystemWatcherEngine::run (this=0x12fdef0)
at io/qfilesystemwatcher_inotify.cpp:248
#8  0x00007f97f7e2de15 in QThreadPrivate::start (arg=0x12fdef0) at
thread/qthread_unix.cpp:248
#9  0x00007f97f121a8ba in start_thread (arg=<value optimized out>) at
pthread_create.c:300
#10 0x00007f97f690902d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#11 0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7f97f9e2f760 (LWP 3725)):
[KCrash Handler]
#5  0x00007f97f898271f in KMCommand::slotStart (this=0x65bcf0) at
../../kmail/kmcommands.cpp:261
#6  0x00007f97f897ab06 in KMCommand::qt_metacall (this=0x65bcf0,
_c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff93b27c80)
at ./kmcommands.moc:92
#7  0x00007f97f7f30306 in QMetaObject::activate (sender=0x1b63570, m=<value
optimized out>, local_signal_index=<value optimized out>, argv=0x162b7f8) at
kernel/qobject.cpp:3295
#8  0x00007f97f7f3780f in QSingleShotTimer::timerEvent (this=0x1b63570) at
kernel/qtimer.cpp:308
#9  0x00007f97f7f2cb63 in QObject::event (this=0x1b63570, e=0x7fff93b283e0) at
kernel/qobject.cpp:1212
#10 0x00007f97f72bd32c in QApplicationPrivate::notify_helper (this=0x6619e0,
receiver=0x1b63570, e=0x7fff93b283e0) at kernel/qapplication.cpp:4302
#11 0x00007f97f72c380b in QApplication::notify (this=0x7fff93b28850,
receiver=0x1b63570, e=0x7fff93b283e0) at kernel/qapplication.cpp:4185
#12 0x00007f97f9858836 in KApplication::notify (this=0x7fff93b28850,
receiver=0x1b63570, event=0x7fff93b283e0) at
../../kdeui/kernel/kapplication.cpp:302
#13 0x00007f97f7f1d0bc in QCoreApplication::notifyInternal
(this=0x7fff93b28850, receiver=0x1b63570, event=0x7fff93b283e0) at
kernel/qcoreapplication.cpp:726
#14 0x00007f97f7f49e92 in QCoreApplication::sendEvent (this=0x665320) at
../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#15 QTimerInfoList::activateTimers (this=0x665320) at
kernel/qeventdispatcher_unix.cpp:603
#16 0x00007f97f7f469e4 in timerSourceDispatch (source=<value optimized out>) at
kernel/qeventdispatcher_glib.cpp:184
#17 0x00007f97ee4fc6f2 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#18 0x00007f97ee500568 in ?? () from /lib/libglib-2.0.so.0
#19 0x00007f97ee50071c in g_main_context_iteration () from
/lib/libglib-2.0.so.0
#20 0x00007f97f7f466d3 in QEventDispatcherGlib::processEvents (this=0x60c840,
flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:412
#21 0x00007f97f736d18e in QGuiEventDispatcherGlib::processEvents
(this=0xf9e460, flags=<value optimized out>) at
kernel/qguieventdispatcher_glib.cpp:204
#22 0x00007f97f7f1b9e2 in QEventLoop::processEvents (this=<value optimized
out>, flags=) at kernel/qeventloop.cpp:149
#23 0x00007f97f7f1bdbc in QEventLoop::exec (this=0x7fff93b28680, flags=) at
kernel/qeventloop.cpp:201
#24 0x00007f97f7f20a4b in QCoreApplication::exec () at
kernel/qcoreapplication.cpp:1003
#25 0x0000000000403452 in main (argc=<value optimized out>, argv=<value
optimized out>) at ../../kmail/main.cpp:156
The current source language is "auto; currently c".
The current source language is "auto; currently asm".

Possible duplicates by query: bug 252022, bug 249381, bug 248835, bug 247524,
bug 247512.

Reported using DrKonqi

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.