| Summary: | Crash if pressing answer when no mail is selected | ||
|---|---|---|---|
| Product: | [Unmaintained] kmail | Reporter: | Frederik Schwarzer <schwarzer> |
| Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
| Status: | RESOLVED FIXED | ||
| Severity: | crash | CC: | andresbajotierra, bjoern |
| Priority: | NOR | ||
| Version: | 1.11.2 | ||
| Target Milestone: | --- | ||
| Platform: | Debian testing | ||
| OS: | Unspecified | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
This could be related/dupe of bug 182629 / bug 176845 / bug 180989. Thanks I think it is not possible anymore to trigger this bug because the reply action is deactivated when no mail is selected. Am I right? This bug is no longer reproducable. I cannot get a situation where no mail is selected. |
Version: 1.11.2 (using KDE 4.2.2) Installed from: Debian testing/unstable Packages Sometimes if I remove a thread (Ctrl+Del) no mail is selected afterwards. If I then press Reply, KMail crashes with the following backtrace. The case is cleanly reproducable here. Anwendung: KMail (kmail), Signal SIGSEGV 0x00007f3951ad7831 in nanosleep () from /lib/libc.so.6 Current language: auto; currently c Thread 1 (Thread 0x7f3954bbc760 (LWP 6293)): [KCrash Handler] #5 0x0000000001219830 in ?? () #6 0x00007f3953a4053e in KMCommand::slotStart (this=0x1525b10) at ../../kmail/kmcommands.cpp:249 #7 0x00007f3953a30e82 in KMCommand::qt_metacall (this=0x1525b10, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff5ccff510) at ./kmcommands.moc:85 #8 0x00007f3953065862 in QMetaObject::activate (sender=0x1565110, from_signal_index=<value optimized out>, to_signal_index=4, argv=0x152e390) at kernel/qobject.cpp:3120 #9 0x00007f395306ab9f in QSingleShotTimer::timerEvent (this=0x1565110) at kernel/qtimer.cpp:298 #10 0x00007f395305fb43 in QObject::event (this=0x1565110, e=0x0) at kernel/qobject.cpp:1082 #11 0x00007f395248d4fd in QApplicationPrivate::notify_helper (this=0x642db0, receiver=0x1565110, e=0x7fff5ccffbd0) at kernel/qapplication.cpp:4057 #12 0x00007f395249577a in QApplication::notify (this=0x7fff5cd00030, receiver=0x1565110, e=0x7fff5ccffbd0) at kernel/qapplication.cpp:4022 #13 0x00007f39546f555b in KApplication::notify (this=0x7fff5cd00030, receiver=0x1565110, event=0x7fff5ccffbd0) at ../../kdeui/kernel/kapplication.cpp:307 #14 0x00007f395304fe4c in QCoreApplication::notifyInternal (this=0x7fff5cd00030, receiver=0x1565110, event=0x7fff5ccffbd0) at kernel/qcoreapplication.cpp:610 #15 0x00007f395307d036 in QTimerInfoList::activateTimers (this=0x63b330) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213 #16 0x00007f395307955d in timerSourceDispatch (source=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:164 #17 0x00007f394a427f7a in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #18 0x00007f394a42b640 in ?? () from /usr/lib/libglib-2.0.so.0 #19 0x00007f394a42b7dc in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #20 0x00007f39530794bf in QEventDispatcherGlib::processEvents (this=0x61a900, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:324 #21 0x00007f3952525c7f in QGuiEventDispatcherGlib::processEvents (this=0x1356040, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202 #22 0x00007f395304e6f2 in QEventLoop::processEvents (this=<value optimized out>, flags={i = 1557134912}) at kernel/qeventloop.cpp:149 #23 0x00007f395304eabd in QEventLoop::exec (this=0x7fff5ccffe80, flags={i = 1557134992}) at kernel/qeventloop.cpp:200 #24 0x00007f3953050d84 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888 #25 0x0000000000402f8b in main (argc=<value optimized out>, argv=<value optimized out>) at ../../kmail/main.cpp:146