| Summary: | Crash when doing ctrl+j | ||
|---|---|---|---|
| Product: | [Unmaintained] kmail | Reporter: | envite |
| Component: | filtering | Assignee: | kdepim bugs <kdepim-bugs> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | crash | CC: | andresbajotierra, bjoern, wolf.behrenhoff |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Debian testing | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
envite
2009-02-02 17:57:05 UTC
This may be related to bug 156991 / bug 176571 (same assert, but the situation that triggers it may be different) Hello, here I can reproduce a crash of kmail: I mark a certain massage and hit Ctrl-J to filter it. Strage enough, the crash occurs reproducible only for a certain message. I could not reproduce it with other messages. In difference to the existing bug report, this is KDE 4.3.4 / Kubuntu. Application: Kontact (kontact), signal: Segmentation fault [KCrash Handler] #6 KMail::ActionScheduler::actionMessage (this=0xa05c0c0, res=KMFilterAction::GoOn) at ../../kmail/actionscheduler.cpp:675 #7 0xb43e003c in KMail::ActionScheduler::filterMessage (this=0xa05c0c0) at ../../kmail/actionscheduler.cpp:648 #8 0xb43e0474 in KMail::ActionScheduler::qt_metacall (this=0xa05c0c0, _c=QMetaObject::InvokeMetaMethod, _id=17, _a=0xbfd817cc) at ./actionscheduler.moc:124 #9 0x04ab8263 in QMetaObject::activate (sender=0xa0615d0, from_signal_index=4, to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3113 #10 0x04ab8ec2 in QMetaObject::activate (sender=0xa0615d0, m=0x4b93904, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3187 #11 0x04af2667 in QTimer::timeout (this=0xa0615d0) at .moc/release-shared/moc_qtimer.cpp:128 #12 0x04abd9ae in QTimer::timerEvent (this=0xa0615d0, e=0xbfd81c60) at kernel/qtimer.cpp:261 #13 0x04ab23bf in QObject::event (this=0xa0615d0, e=0xbfd81c60) at kernel/qobject.cpp:1075 #14 0x00ba9f54 in QApplicationPrivate::notify_helper (this=0x91547a0, receiver=0xa0615d0, e=0xbfd81c60) at kernel/qapplication.cpp:4056 #15 0x00bb167c in QApplication::notify (this=0xbfd81fc4, receiver=0xa0615d0, e=0xbfd81c60) at kernel/qapplication.cpp:3603 #16 0x008c91aa in KApplication::notify (this=0xbfd81fc4, receiver=0xa0615d0, event=0xbfd81c60) at ../../kdeui/kernel/kapplication.cpp:302 #17 0x04aa26cb in QCoreApplication::notifyInternal (this=0xbfd81fc4, receiver=0xa0615d0, event=0xbfd81c60) at kernel/qcoreapplication.cpp:610 #18 0x04acf7ce in QCoreApplication::sendEvent (this=0x915bf34) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213 #19 QTimerInfoList::activateTimers (this=0x915bf34) at kernel/qeventdispatcher_unix.cpp:572 #20 0x04acd0e0 in timerSourceDispatch (source=0x915bf00) at kernel/qeventdispatcher_glib.cpp:165 #21 0x01a11e78 in g_main_context_dispatch () from /lib/libglib-2.0.so.0 #22 0x01a15720 in ?? () from /lib/libglib-2.0.so.0 #23 0x01a15853 in g_main_context_iteration () from /lib/libglib-2.0.so.0 #24 0x04acd02c in QEventDispatcherGlib::processEvents (this=0x912e9f8, flags=...) at kernel/qeventdispatcher_glib.cpp:327 #25 0x00c4abe5 in QGuiEventDispatcherGlib::processEvents (this=0x912e9f8, flags=...) at kernel/qguieventdispatcher_glib.cpp:202 #26 0x04aa0c79 in QEventLoop::processEvents (this=0xbfd81f24, flags=) at kernel/qeventloop.cpp:149 #27 0x04aa10ca in QEventLoop::exec (this=0xbfd81f24, flags=...) at kernel/qeventloop.cpp:201 #28 0x04aa353f in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888 #29 0x00ba9dd7 in QApplication::exec () at kernel/qapplication.cpp:3525 #30 0x0804b4e6 in main (argc=1, argv=0xbfd821e4) at ../../../kontact/src/main.cpp:218 *** This bug has been marked as a duplicate of bug 176571 *** |