Bug 263276 - kmail crash on start
Summary: kmail crash on start
Status: RESOLVED DUPLICATE of bug 169048
Alias: None
Product: kmail
Classification: Unmaintained
Component: general (show other bugs)
Version: 1.13.5
Platform: Debian stable Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-01-16 01:04 UTC by agaida
Modified: 2011-02-10 11:25 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description agaida 2011-01-16 01:04:59 UTC
Application: kmail (1.13.5)
KDE Platform Version: 4.5.3 (KDE 4.5.3)
Qt Version: 4.6.3
Operating System: Linux 2.6.37-trunk-amd64 x86_64
Distribution: Debian GNU/Linux 6.0 (squeeze)

-- Information about the crash:
- What I was doing when the application crashed:
Just opend kmail and try to read my IMAP account. The first time it chrashed after apply some filters. After that it chrashed on every Start

The crash can be reproduced every time.

-- Backtrace:
Application: KMail (kmail), signal: Segmentation fault
[KCrash Handler]
#6  KMail::ActionScheduler::actionMessage (this=0x2438260, res=<value optimized out>) at ../../kmail/actionscheduler.cpp:675
#7  0x00007fd3981f1d18 in KMail::ActionScheduler::filterMessage (this=0x2438260) at ../../kmail/actionscheduler.cpp:648
#8  0x00007fd3981f2644 in KMail::ActionScheduler::qt_metacall (this=0x2438260, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff76ec7f00) at ./actionscheduler.moc:130
#9  0x00007fd3979152e6 in QMetaObject::activate (sender=0x2441ed0, m=<value optimized out>, local_signal_index=<value optimized out>, argv=0x2456e58) at kernel/qobject.cpp:3295
#10 0x00007fd397911b43 in QObject::event (this=0x2441ed0, e=0x7fff76ec8650) at kernel/qobject.cpp:1212
#11 0x00007fd396ca232c in QApplicationPrivate::notify_helper (this=0x1a03950, receiver=0x2441ed0, e=0x7fff76ec8650) at kernel/qapplication.cpp:4302
#12 0x00007fd396ca880b in QApplication::notify (this=0x7fff76ec8ac0, receiver=0x2441ed0, e=0x7fff76ec8650) at kernel/qapplication.cpp:4185
#13 0x00007fd3992afef6 in KApplication::notify (this=0x7fff76ec8ac0, receiver=0x2441ed0, event=0x7fff76ec8650) at ../../kdeui/kernel/kapplication.cpp:310
#14 0x00007fd39790209c in QCoreApplication::notifyInternal (this=0x7fff76ec8ac0, receiver=0x2441ed0, event=0x7fff76ec8650) at kernel/qcoreapplication.cpp:726
#15 0x00007fd39792ee72 in sendEvent (this=0x1a07360) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#16 QTimerInfoList::activateTimers (this=0x1a07360) at kernel/qeventdispatcher_unix.cpp:603
#17 0x00007fd39792b9e8 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 0x00007fd38e05c6f2 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#20 0x00007fd38e060568 in ?? () from /lib/libglib-2.0.so.0
#21 0x00007fd38e06071c in g_main_context_iteration () from /lib/libglib-2.0.so.0
#22 0x00007fd39792b6b3 in QEventDispatcherGlib::processEvents (this=0x19c2840, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:412
#23 0x00007fd396d5219e in QGuiEventDispatcherGlib::processEvents (this=0x24426e0, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:204
#24 0x00007fd3979009c2 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149
#25 0x00007fd397900d9c in QEventLoop::exec (this=0x7fff76ec88f0, flags=) at kernel/qeventloop.cpp:201
#26 0x00007fd397905a2b in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1003
#27 0x0000000000403462 in main (argc=<value optimized out>, argv=<value optimized out>) at ../../kmail/main.cpp:156

This bug may be a duplicate of or related to bug 169048.

Possible duplicates by query: bug 248180, bug 246480, bug 245793, bug 244425, bug 242318.

Reported using DrKonqi
Comment 1 Christophe Marin 2011-02-10 11:25:18 UTC

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