Bug 233574 - KMail crashed after clicking the reply button
Summary: KMail crashed after clicking the reply button
Status: RESOLVED BACKTRACE
Alias: None
Product: kmail2
Classification: Applications
Component: general (show other bugs)
Version: 4.7
Platform: Fedora RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
: 233721 241889 262538 265789 287953 (view as bug list)
Depends on:
Blocks:
 
Reported: 2010-04-07 09:10 UTC by Volker Fröhlich
Modified: 2012-08-27 22:33 UTC (History)
7 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
New crash information added by DrKonqi (3.21 KB, text/plain)
2012-08-24 20:38 UTC, Frank Schneider
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Volker Fröhlich 2010-04-07 09:10:34 UTC
Application: kmail (1.13.1)
KDE Platform Version: 4.4.1 (KDE 4.4.1)
Qt Version: 4.6.2
Operating System: Linux 2.6.32.10-90.fc12.x86_64 x86_64
Distribution: "Fedora release 12 (Constantine)"

-- Information about the crash:
I clicked "reply" for a message I read in the preview pane.

The crash does not seem to be reproducible.

 -- Backtrace:
Application: KMail (kmail), signal: Segmentation fault
82	T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS)
[KCrash Handler]
#5  0x00007f49d599467f in KMCommand::slotStart (this=0x2dcefb0) at /usr/src/debug/kdepim-4.4.1/kmail/kmcommands.cpp:262
#6  0x00007f49d598cf06 in KMCommand::qt_metacall (this=0x2dcefb0, _c=InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff09b03000)
    at /usr/src/debug/kdepim-4.4.1/x86_64-redhat-linux-gnu/kmail/kmcommands.moc:92
#7  0x000000360bd6a2af in QMetaObject::activate (sender=0x2ae4be0, m=<value optimized out>, local_signal_index=<value optimized out>, argv=0x0) at kernel/qobject.cpp:3293
#8  0x000000360bd6f97f in QSingleShotTimer::timerEvent (this=0x2ae4be0) at kernel/qtimer.cpp:308
#9  0x000000360bd6663e in QObject::event (this=0x2ae4be0, e=0x7fff09b03760) at kernel/qobject.cpp:1212
#10 0x000000368abaa9dc in QApplicationPrivate::notify_helper (this=0x1f610f0, receiver=0x2ae4be0, e=0x7fff09b03760) at kernel/qapplication.cpp:4300
#11 0x000000368abb0aab in QApplication::notify (this=<value optimized out>, receiver=0x2ae4be0, e=0x7fff09b03760) at kernel/qapplication.cpp:4183
#12 0x000000368c006846 in KApplication::notify (this=0x7fff09b03bd0, receiver=0x2ae4be0, event=0x7fff09b03760) at /usr/src/debug/kdelibs-4.4.1/kdeui/kernel/kapplication.cpp:302
#13 0x000000360bd5774c in QCoreApplication::notifyInternal (this=0x7fff09b03bd0, receiver=0x2ae4be0, event=0x7fff09b03760) at kernel/qcoreapplication.cpp:704
#14 0x000000360bd7fe02 in sendEvent (this=0x1f649e0) at kernel/qcoreapplication.h:215
#15 QTimerInfoList::activateTimers (this=0x1f649e0) at kernel/qeventdispatcher_unix.cpp:603
#16 0x000000360bd7d374 in timerSourceDispatch (source=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:184
#17 0x0000003c4f83923e in g_main_dispatch (context=0x1f63920) at gmain.c:1960
#18 IA__g_main_context_dispatch (context=0x1f63920) at gmain.c:2513
#19 0x0000003c4f83cc28 in g_main_context_iterate (context=0x1f63920, block=<value optimized out>, dispatch=<value optimized out>, self=<value optimized out>) at gmain.c:2591
#20 0x0000003c4f83cd4a in IA__g_main_context_iteration (context=0x1f63920, may_block=1) at gmain.c:2654
#21 0x000000360bd7d063 in QEventDispatcherGlib::processEvents (this=0x1f1fc00, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:412
#22 0x000000368ac49a4e in QGuiEventDispatcherGlib::processEvents (this=<value optimized out>, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:204
#23 0x000000360bd56192 in QEventLoop::processEvents (this=<value optimized out>, flags=...) at kernel/qeventloop.cpp:149
#24 0x000000360bd5645c in QEventLoop::exec (this=0x7fff09b03a00, flags=...) at kernel/qeventloop.cpp:201
#25 0x000000360bd58749 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:981
#26 0x00000000004032d2 in main (argc=<value optimized out>, argv=<value optimized out>) at /usr/src/debug/kdepim-4.4.1/kmail/main.cpp:156

Possible duplicates by query: bug 232936, bug 231756, bug 231225, bug 230571, bug 230458.

Reported using DrKonqi
Comment 1 FiNeX 2010-04-10 00:42:37 UTC
Does the original email contains one or more attachment?
Comment 2 Volker Fröhlich 2010-04-10 09:08:50 UTC
I can't recall a 100% which E-mail it was, but most likely it didn't.
Comment 3 Björn Ruberg 2010-04-14 23:18:24 UTC
*** Bug 233721 has been marked as a duplicate of this bug. ***
Comment 4 Nicolas L. 2010-06-17 10:43:47 UTC
*** Bug 241889 has been marked as a duplicate of this bug. ***
Comment 5 Christophe Marin 2011-02-14 17:15:15 UTC
*** Bug 262538 has been marked as a duplicate of this bug. ***
Comment 6 Christophe Marin 2011-05-04 19:38:12 UTC
*** Bug 265789 has been marked as a duplicate of this bug. ***
Comment 7 Christophe Marin 2011-12-04 10:52:32 UTC
*** Bug 287953 has been marked as a duplicate of this bug. ***
Comment 8 Myriam Schweingruber 2012-08-19 10:50:31 UTC
Thank you for your report. Kmail1 is currently unmaintained and the code has changed sufficiently in Kmail2 so the backtraces are not really useful anymore. Should you experience the same crash in Kmail 4.8.5 or later, please open a new report for Kmail2. Thank you for your understanding
Comment 9 Frank Schneider 2012-08-24 20:38:48 UTC
Created attachment 73448 [details]
New crash information added by DrKonqi

kontact (4.4.11) on KDE Platform 4.6.5 (4.6.5) using Qt 4.7.4

- What I was doing when the application crashed: I tried to reply a message. Before I copied a weblink.

-- Backtrace (Reduced):
#6  0x00007fe69d2b5d33 in KMCommand::slotStart() () from /usr/lib64/libkmailprivate.so.4
#7  0x00007fe69d2c0bd6 in KMCommand::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib64/libkmailprivate.so.4
#8  0x00007fe6b82118ba in QObject::event(QEvent*) () from /usr/lib64/libQtCore.so.4
#9  0x00007fe6b8bbf794 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4
#10 0x00007fe6b8bc436a in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4
Comment 10 Myriam Schweingruber 2012-08-27 22:33:53 UTC
Frank: your backtrace is lacking debugging symbols,please install those an provide a better backtrace. Please also make sure to paste the backtrace directly in the comment and check the duplicates mentioned at the bottom of the backtrace.

See also http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports