[Bug 232024] New: Kontact crashes after disconnected imap message

Rein smokingr at gmail.com
Wed Mar 24 18:15:14 GMT 2010


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

           Summary: Kontact crashes after disconnected imap message
           Product: kontact
           Version: unspecified
          Platform: Unlisted Binaries
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: crash
          Priority: NOR
         Component: general
        AssignedTo: kdepim-bugs at kde.org
        ReportedBy: smokingr at gmail.com


Application that crashed: kontact
Version of the application: 4.3.4
KDE Version: 4.3.4 (KDE 4.3.4)
Qt Version: 4.5.3
Operating System: Linux 2.6.32-3-686 i686
Distribution: Debian GNU/Linux testing (squeeze)

What I was doing when the application crashed:
I was away from my computer, when I came back I got the message that my imap
was disconnected (btw, i'm using disconnected imap). Only seconds later Kontact
completely crashed.

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

Thread 2 (Thread 0xafe9ab70 (LWP 2530)):
#0  0xb787e424 in __kernel_vsyscall ()
#1  0xb63d3591 in select () from /lib/i686/cmov/libc.so.6
#2  0xb70254a0 in QProcessManager::run (this=0x98b21c8) at
io/qprocess_unix.cpp:296
#3  0xb6f565e2 in QThreadPrivate::start (arg=0x98b21c8) at
thread/qthread_unix.cpp:188
#4  0xb4a28585 in start_thread (arg=0xafe9ab70) at pthread_create.c:300
#5  0xb63da29e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130

Thread 1 (Thread 0xb4101700 (LWP 2503)):
[KCrash Handler]
#6  KIO::Slave::deref (this=0x9942608) at ../../kio/kio/slave.cpp:242
#7  0xb5b1b6d6 in KIO::Slave::gotInput (this=0x9942608) at
../../kio/kio/slave.cpp:335
#8  0xb5b1dac3 in KIO::Slave::qt_metacall (this=0x9942608,
_c=QMetaObject::InvokeMetaMethod, _id=30, _a=0xbfa46a98) at ./slave.moc:76
#9  0xb705c303 in QMetaObject::activate (sender=0x9fb8bd8, from_signal_index=4,
to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3112
#10 0xb705cf42 in QMetaObject::activate (sender=0x9fb8bd8, m=0xb5c0c4c0,
local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3186
#11 0xb5a24fc7 in KIO::Connection::readyRead (this=0x9fb8bd8) at
./connection.moc:86
#12 0xb5a26d8e in KIO::ConnectionPrivate::dequeue (this=0x9ce03e0) at
../../kio/kio/connection.cpp:82
#13 0xb5a26ebe in KIO::Connection::qt_metacall (this=0x9fb8bd8,
_c=QMetaObject::InvokeMetaMethod, _id=5, _a=0xa5447d8) at ./connection.moc:73
#14 0xb7055b0b in QMetaCallEvent::placeMetaCall (this=0xa8620e0,
object=0x9fb8bd8) at kernel/qobject.cpp:477
#15 0xb70575e0 in QObject::event (this=0x9fb8bd8, e=0xa8620e0) at
kernel/qobject.cpp:1110
#16 0xb6686a94 in QApplicationPrivate::notify_helper (this=0x98ba6f0,
receiver=0x9fb8bd8, e=0xa8620e0) at kernel/qapplication.cpp:4065
#17 0xb668ebee in QApplication::notify (this=0xbfa472d4, receiver=0x9fb8bd8,
e=0xa8620e0) at kernel/qapplication.cpp:3605
#18 0xb7557e2a in KApplication::notify (this=0xbfa472d4, receiver=0x9fb8bd8,
event=0xa8620e0) at ../../kdeui/kernel/kapplication.cpp:302
#19 0xb70471eb in QCoreApplication::notifyInternal (this=0xbfa472d4,
receiver=0x9fb8bd8, event=0xa8620e0) at kernel/qcoreapplication.cpp:610
#20 0xb7047e2e in QCoreApplication::sendEvent (receiver=0x0, event_type=0,
data=0x9891388) at
../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#21 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0,
data=0x9891388) at kernel/qcoreapplication.cpp:1247
#22 0xb704800d in QCoreApplication::sendPostedEvents (receiver=0x0,
event_type=0) at kernel/qcoreapplication.cpp:1140
#23 0xb70724cf in QCoreApplication::sendPostedEvents (s=0x98b14d8) at
../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:218
#24 postEventSourceDispatch (s=0x98b14d8) at
kernel/qeventdispatcher_glib.cpp:276
#25 0xb4a73b38 in g_main_dispatch (context=0x98b1458) at
/build/buildd-glib2.0_2.22.4-1-i386-jRfNZE/glib2.0-2.22.4/glib/gmain.c:1960
#26 IA__g_main_context_dispatch (context=0x98b1458) at
/build/buildd-glib2.0_2.22.4-1-i386-jRfNZE/glib2.0-2.22.4/glib/gmain.c:2513
#27 0xb4a773d0 in g_main_context_iterate (context=0x98b1458, block=<value
optimized out>, dispatch=1, self=0x98afc20) at
/build/buildd-glib2.0_2.22.4-1-i386-jRfNZE/glib2.0-2.22.4/glib/gmain.c:2591
#28 0xb4a77503 in IA__g_main_context_iteration (context=0x98b1458, may_block=1)
at /build/buildd-glib2.0_2.22.4-1-i386-jRfNZE/glib2.0-2.22.4/glib/gmain.c:2654
#29 0xb7072041 in QEventDispatcherGlib::processEvents (this=0x98910d8,
flags=...) at kernel/qeventdispatcher_glib.cpp:407
#30 0xb6726305 in QGuiEventDispatcherGlib::processEvents (this=0x98910d8,
flags=...) at kernel/qguieventdispatcher_glib.cpp:202
#31 0xb704583a in QEventLoop::processEvents (this=0xbfa47250, flags=...) at
kernel/qeventloop.cpp:149
#32 0xb7045c82 in QEventLoop::exec (this=0xbfa47250, flags=...) at
kernel/qeventloop.cpp:201
#33 0xb70480d9 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#34 0xb6686917 in QApplication::exec () at kernel/qapplication.cpp:3525
#35 0x0804b4c6 in _start ()

This bug may be a duplicate of or related to bug 196862

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.



More information about the Kdepim-bugs mailing list