Bug 283817

Summary: Crash of Kontact - Kmail many times daily
Product: [Applications] kontact Reporter: soft
Component: generalAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED DUPLICATE    
Severity: crash    
Priority: NOR    
Version: 4.4.10   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description soft 2011-10-11 18:50:53 UTC
Application: kontact (4.4.10)
KDE Platform Version: 4.6.5 (4.6.5)
Qt Version: 4.7.2
Operating System: Linux 2.6.38-10-generic x86_64
Distribution: Ubuntu 11.04

-- Information about the crash:
- What I was doing when the application crashed: When it happens I mostly work with another program, this time with libreoffice. 

- Unusual behavior I noticed: It seems Kmail is looking for new emails and the response of the provider-server may last to long.

- Custom settings of the application: There are several mailboxes, IMAP and POP, but no special settings. Maybe there is a settings-file I could send, but I don't know where.

The crash can be reproduced every time.

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

Thread 3 (Thread 0x7fe363fff700 (LWP 2534)):
#0  0x00007fe388065f03 in __poll (fds=<value optimized out>, nfds=<value optimized out>, timeout=<value optimized out>) at ../sysdeps/unix/sysv/linux/poll.c:87
#1  0x00007fe381a90104 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007fe381a909f2 in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007fe3692abc44 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#4  0x00007fe381ab73e4 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x00007fe381f5bd8c in start_thread (arg=0x7fe363fff700) at pthread_create.c:304
#6  0x00007fe38807304d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#7  0x0000000000000000 in ?? ()

Thread 2 (Thread 0x7fe368972700 (LWP 2566)):
#0  0x00007fe388065f03 in __poll (fds=<value optimized out>, nfds=<value optimized out>, timeout=<value optimized out>) at ../sysdeps/unix/sysv/linux/poll.c:87
#1  0x00007fe381a90104 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007fe381a90639 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007fe3887ad446 in QEventDispatcherGlib::processEvents (this=0xaf0430, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:424
#4  0x00007fe388781882 in QEventLoop::processEvents (this=<value optimized out>, flags=...) at kernel/qeventloop.cpp:149
#5  0x00007fe388781abc in QEventLoop::exec (this=0x7fe368971db0, flags=...) at kernel/qeventloop.cpp:201
#6  0x00007fe388698924 in QThread::exec (this=<value optimized out>) at thread/qthread.cpp:492
#7  0x00007fe388763c2f in QInotifyFileSystemWatcherEngine::run (this=0x914ad0) at io/qfilesystemwatcher_inotify.cpp:248
#8  0x00007fe38869b175 in QThreadPrivate::start (arg=0x914ad0) at thread/qthread_unix.cpp:320
#9  0x00007fe381f5bd8c in start_thread (arg=0x7fe368972700) at pthread_create.c:304
#10 0x00007fe38807304d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#11 0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7fe38ac197a0 (LWP 2531)):
[KCrash Handler]
#6  KMail::ActionScheduler::actionMessage (this=0x1a82740, res=<value optimized out>) at ../../kmail/actionscheduler.cpp:675
#7  0x00007fe36c032697 in KMail::ActionScheduler::filterMessage (this=0x1a82740) at ../../kmail/actionscheduler.cpp:648
#8  0x00007fe36c032a54 in KMail::ActionScheduler::qt_metacall (this=0x1a82740, _c=QMetaObject::InvokeMetaMethod, _id=17, _a=0x7fffd1acf240) at ./actionscheduler.moc:130
#9  0x00007fe3887975f8 in QMetaObject::activate (sender=0x1523a00, m=<value optimized out>, local_signal_index=<value optimized out>, argv=0x0) at kernel/qobject.cpp:3287
#10 0x00007fe3887961c9 in QObject::event (this=0x1523a00, e=<value optimized out>) at kernel/qobject.cpp:1190
#11 0x00007fe3891419f4 in QApplicationPrivate::notify_helper (this=0x7f7b10, receiver=0x1523a00, e=0x7fffd1acf940) at kernel/qapplication.cpp:4462
#12 0x00007fe3891463ba in QApplication::notify (this=<value optimized out>, receiver=0x1523a00, e=0x7fffd1acf940) at kernel/qapplication.cpp:4341
#13 0x00007fe389e656c6 in KApplication::notify (this=0x7fffd1acfc20, receiver=0x1523a00, event=0x7fffd1acf940) at ../../kdeui/kernel/kapplication.cpp:311
#14 0x00007fe38878249c in QCoreApplication::notifyInternal (this=0x7fffd1acfc20, receiver=0x1523a00, event=0x7fffd1acf940) at kernel/qcoreapplication.cpp:731
#15 0x00007fe3887aff12 in sendEvent (this=0x7fe1f0) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#16 QTimerInfoList::activateTimers (this=0x7fe1f0) at kernel/qeventdispatcher_unix.cpp:604
#17 0x00007fe3887acd18 in timerSourceDispatch (source=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:184
#18 idleTimerSourceDispatch (source=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:231
#19 0x00007fe381a8fbcd in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#20 0x00007fe381a903a8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#21 0x00007fe381a90639 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#22 0x00007fe3887ad3ef in QEventDispatcherGlib::processEvents (this=0x79a370, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:422
#23 0x00007fe3891eb4de in QGuiEventDispatcherGlib::processEvents (this=<value optimized out>, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:204
#24 0x00007fe388781882 in QEventLoop::processEvents (this=<value optimized out>, flags=...) at kernel/qeventloop.cpp:149
#25 0x00007fe388781abc in QEventLoop::exec (this=0x7fffd1acfbb0, flags=...) at kernel/qeventloop.cpp:201
#26 0x00007fe388785ecb in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1008
#27 0x0000000000403f70 in main (argc=1, argv=<value optimized out>) at ../../../kontact/src/main.cpp:226

Possible duplicates by query: bug 278971, bug 278543, bug 278076, bug 269389, bug 269166.

Reported using DrKonqi
Comment 1 Christophe Marin 2011-10-12 15:21:32 UTC

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