Bug 214924 - Crash with 2 IMAP accounts open
Summary: Crash with 2 IMAP accounts open
Status: RESOLVED DUPLICATE of bug 169048
Alias: None
Product: kontact
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Unlisted Binaries Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-11-17 06:31 UTC by Angus Ainslie
Modified: 2009-11-17 07:09 UTC (History)
0 users

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 Angus Ainslie 2009-11-17 06:31:29 UTC
Application that crashed: kontact
Version of the application: 4.3.2
KDE Version: 4.3.2 (KDE 4.3.2)
Qt Version: 4.5.2
Operating System: Linux 2.6.31-14-generic i686
Distribution: Ubuntu 9.10

What I was doing when the application crashed:
Changing from one IMAP account to the other. The status bar said something about filtering right before the crash

 -- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
[KCrash Handler]
#6  KMail::ActionScheduler::actionMessage (this=0xad9d080, res=KMFilterAction::GoOn) at ../../kmail/actionscheduler.cpp:675
#7  0xb465de7c in KMail::ActionScheduler::filterMessage (this=0xad9d080) at ../../kmail/actionscheduler.cpp:648
#8  0xb465e2b4 in KMail::ActionScheduler::qt_metacall (this=0xad9d080, _c=QMetaObject::InvokeMetaMethod, _id=17, _a=0xbfa7a47c) at ./actionscheduler.moc:124
#9  0x00bd5263 in QMetaObject::activate (sender=0xab61598, from_signal_index=4, to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3113
#10 0x00bd5ec2 in QMetaObject::activate (sender=0xab61598, m=0xcb0904, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3187
#11 0x00c0f667 in QTimer::timeout (this=0xab61598) at .moc/release-shared/moc_qtimer.cpp:128
#12 0x00bda9ae in QTimer::timerEvent (this=0xab61598, e=0xbfa7a910) at kernel/qtimer.cpp:261
#13 0x00bcf3bf in QObject::event (this=0xab61598, e=0xbfa7a910) at kernel/qobject.cpp:1075
#14 0x00e07f54 in QApplicationPrivate::notify_helper (this=0x9bc46f0, receiver=0xab61598, e=0xbfa7a910) at kernel/qapplication.cpp:4056
#15 0x00e0f67c in QApplication::notify (this=0xbfa7ac74, receiver=0xab61598, e=0xbfa7a910) at kernel/qapplication.cpp:3603
#16 0x00678bfa in KApplication::notify (this=0xbfa7ac74, receiver=0xab61598, event=0xbfa7a910) at ../../kdeui/kernel/kapplication.cpp:302
#17 0x00bbf6cb in QCoreApplication::notifyInternal (this=0xbfa7ac74, receiver=0xab61598, event=0xbfa7a910) at kernel/qcoreapplication.cpp:610
#18 0x00bec7ce in QCoreApplication::sendEvent (this=0x9bbcf34) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#19 QTimerInfoList::activateTimers (this=0x9bbcf34) at kernel/qeventdispatcher_unix.cpp:572
#20 0x00bea0e0 in timerSourceDispatch (source=0x9bbcf00) at kernel/qeventdispatcher_glib.cpp:165
#21 0x0727ae78 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#22 0x0727e720 in ?? () from /lib/libglib-2.0.so.0
#23 0x0727e853 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#24 0x00bea02c in QEventDispatcherGlib::processEvents (this=0x9b949f8, flags=...) at kernel/qeventdispatcher_glib.cpp:327
#25 0x00ea8be5 in QGuiEventDispatcherGlib::processEvents (this=0x9b949f8, flags=...) at kernel/qguieventdispatcher_glib.cpp:202
#26 0x00bbdc79 in QEventLoop::processEvents (this=0xbfa7abd4, flags=) at kernel/qeventloop.cpp:149
#27 0x00bbe0ca in QEventLoop::exec (this=0xbfa7abd4, flags=...) at kernel/qeventloop.cpp:201
#28 0x00bc053f in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#29 0x00e07dd7 in QApplication::exec () at kernel/qapplication.cpp:3525
#30 0x0804b4e6 in main (argc=1, argv=0xbfa7ae94) at ../../../kontact/src/main.cpp:218

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

Reported using DrKonqi
Comment 1 Christophe Marin 2009-11-17 07:09:01 UTC

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