Summary: | Kontact crashed upon print preview | ||
---|---|---|---|
Product: | [Applications] kontact | Reporter: | Christopher Yeleighton <giecrilj> |
Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED UNMAINTAINED | ||
Severity: | crash | CC: | barnie, giuseppe.vinci |
Priority: | NOR | Keywords: | drkonqi |
Version: | 4.11.3 | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | New crash information added by DrKonqi |
Description
Christopher Yeleighton
2013-12-12 23:57:41 UTC
Created attachment 85209 [details]
New crash information added by DrKonqi
kontact (4.12.2) on KDE Platform 4.12.2 using Qt 4.8.5
What I was doing when the application crashed:
1. Show print preview, using menu command.
2. Program crashed after executing command from main manu.
3. Print Preview executed when message preview was not shown (main list of mesages).
-- Backtrace (Reduced):
#5 0x0000003014f68480 in KMail::MessageActions::printMessage(bool) () from /lib64/libkmailprivate.so.4
[...]
#7 0x00000032605c3782 in QAction::triggered(bool) () from /lib64/libQtGui.so.4
#8 0x00000032605c5337 in QAction::activate(QAction::ActionEvent) () from /lib64/libQtGui.so.4
#9 0x0000003260a0e2bd in QMenuPrivate::activateCausedStack(QList<QPointer<QWidget> > const&, QAction*, QAction::ActionEvent, bool) () from /lib64/libQtGui.so.4
#10 0x0000003260a12b49 in QMenuPrivate::activateAction(QAction*, QAction::ActionEvent, bool) () from /lib64/libQtGui.so.4
*** Bug 331267 has been marked as a duplicate of this bug. *** *** Bug 335410 has been marked as a duplicate of this bug. *** This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present? If noone confirms this bug for a Framework-based version of kontact (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months. Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input. |