Bug 203295 - It suddenly crashed, when I clicked on the kmail button "mark as important".
Summary: It suddenly crashed, when I clicked on the kmail button "mark as important".
Status: RESOLVED DUPLICATE of bug 202108
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-08-10 11:17 UTC by Martin Caj
Modified: 2009-11-16 14:17 UTC (History)
2 users (show)

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 Martin Caj 2009-08-10 11:17:13 UTC
Application that crashed: kontact
Version of the application: 4.3.0
KDE Version: 4.3.00 (KDE 4.3.0) "release 152"
Qt Version: 4.5.2
Operating System: Linux 2.6.27.25-0.1-pae i686

 -- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
[KCrash Handler]
#6  0xb0edffc7 in KMCommand::slotStart (this=0x8efbda0) at /usr/src/debug/kdepim-4.3.0/kmail/kmcommands.cpp:235
#7  0xb0ed04a3 in KMCommand::qt_metacall (this=0x8efbda0, _c=QMetaObject::InvokeMetaMethod, _id=4, _a=0xbf91fb58) at /usr/src/debug/kdepim-4.3.0/build/kmail/kmcommands.moc:86
#8  0xb0ed0882 in KMSetStatusCommand::qt_metacall (this=0x8efbda0, _c=QMetaObject::InvokeMetaMethod, _id=8, _a=0xbf91fb58) at /usr/src/debug/kdepim-4.3.0/build/kmail/kmcommands.moc:1360
#9  0xb66aa788 in QMetaObject::activate (sender=0x8aa8320, from_signal_index=4, to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3113
#10 0xb66ab412 in QMetaObject::activate (sender=0x8aa8320, m=0xb678b908, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3187
#11 0xb66b05b7 in QSingleShotTimer::timeout (this=0x8aa8320) at .moc/release-shared/qtimer.moc:76
#12 0xb66b06dc in QSingleShotTimer::timerEvent (this=0x8aa8320) at kernel/qtimer.cpp:298
#13 0xb66a572f in QObject::event (this=0x8aa8320, e=0xbf920000) at kernel/qobject.cpp:1075
#14 0xb5b6c7fc in QApplicationPrivate::notify_helper (this=0x8081068, receiver=0x8aa8320, e=0xbf920000) at kernel/qapplication.cpp:4056
#15 0xb5b74aee in QApplication::notify (this=0xbf9202d8, receiver=0x8aa8320, e=0xbf920000) at kernel/qapplication.cpp:3603
#16 0xb6c7e27d in KApplication::notify (this=0xbf9202d8, receiver=0x8aa8320, event=0xbf920000) at /usr/src/debug/kdelibs-4.3.0/kdeui/kernel/kapplication.cpp:302
#17 0xb669516b in QCoreApplication::notifyInternal (this=0xbf9202d8, receiver=0x8aa8320, event=0xbf920000) at kernel/qcoreapplication.cpp:610
#18 0xb66c45f6 in QTimerInfoList::activateTimers (this=0x8074704) at kernel/qcoreapplication.h:213
#19 0xb66c0980 in timerSourceDispatch (source=0x80746d0) at kernel/qeventdispatcher_glib.cpp:165
#20 0xb4e319c8 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#21 0xb4e35083 in ?? () from /usr/lib/libglib-2.0.so.0
#22 0xb4e35241 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#23 0xb66c08d8 in QEventDispatcherGlib::processEvents (this=0x8053fb0, flags={i = -1080950360}) at kernel/qeventdispatcher_glib.cpp:327
#24 0xb5c0cce5 in QGuiEventDispatcherGlib::processEvents (this=0x8053fb0, flags={i = -1080950312}) at kernel/qguieventdispatcher_glib.cpp:202
#25 0xb669378a in QEventLoop::processEvents (this=0xbf920250, flags={i = -1080950248}) at kernel/qeventloop.cpp:149
#26 0xb6693bd2 in QEventLoop::exec (this=0xbf920250, flags={i = -1080950184}) at kernel/qeventloop.cpp:201
#27 0xb6696079 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#28 0xb5b6c677 in QApplication::exec () at kernel/qapplication.cpp:3525
#29 0x0804c04f in main (argc=3, argv=0xbf9205d4) at /usr/src/debug/kdepim-4.3.0/kontact/src/main.cpp:218

Reported using DrKonqi
Comment 1 Dario Andres 2009-08-11 16:15:54 UTC
Similar backtrace as bug 202108. Thanks
Comment 2 Christophe Marin 2009-11-16 14:17:10 UTC

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