Bug 237258 - Crash on setting message flag
Summary: Crash on setting message flag
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-05-11 16:53 UTC by Erik Hensema
Modified: 2012-08-19 11:04 UTC (History)
0 users

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 Erik Hensema 2010-05-11 16:53:01 UTC
Version:            (using KDE 4.3.5)
OS:                Linux
Installed from:    openSUSE RPMs

Application that crashed: kontact
Version of the application: 4.3.5
KDE Version: 4.3.5 (KDE 4.3.5) "release 3"
Qt Version: 4.5.3
Operating System: Linux 2.6.27.45-0.1-default x86_64
Distribution: "openSUSE 11.1 (x86_64)"


* Open offline imap folder
* Double click on a message, opening it in a new window
* Try to set a message flag

Most of the time kmail will crash. See backtrace below.


 -- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
[KCrash Handler]
#5  0x00007f3a8b2fdfbc in KMSetStatusCommand::execute() () from /usr/lib64/libkmailprivate.so.4
#6  0x00007f3a8b2f80e2 in KMCommand::slotPostTransfer(KMCommand::Result) () from /usr/lib64/libkmailprivate.so.4
#7  0x00007f3a8b3020ce in KMCommand::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib64/libkmailprivate.so.4
#8  0x00007f3a9ee0dee2 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib64/libQtCore.so.4
#9  0x00007f3a8b2f52be in KMCommand::messagesTransfered(KMCommand::Result) () from /usr/lib64/libkmailprivate.so.4
#10 0x00007f3a8b311388 in KMCommand::transferSelectedMsgs() () from /usr/lib64/libkmailprivate.so.4
#11 0x00007f3a8b3115b6 in KMCommand::slotStart() () from /usr/lib64/libkmailprivate.so.4
#12 0x00007f3a8b3020e2 in KMCommand::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib64/libkmailprivate.so.4
#13 0x00007f3a9ee0dee2 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib64/libQtCore.so.4
#14 0x00007f3a9ee13c1f in ?? () from /usr/lib64/libQtCore.so.4
#15 0x00007f3a9ee08d33 in QObject::event(QEvent*) () from /usr/lib64/libQtCore.so.4
#16 0x00007f3a9db16aad in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4
#17 0x00007f3a9db1ed3a in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4
#18 0x00007f3a9fc3f1db in KApplication::notify(QObject*, QEvent*) () from /usr/lib64/libkdeui.so.5
#19 0x00007f3a9edf915c in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib64/libQtCore.so.4
#20 0x00007f3a9ee26680 in ?? () from /usr/lib64/libQtCore.so.4
#21 0x00007f3a9ee22838 in ?? () from /usr/lib64/libQtCore.so.4
#22 0x00007f3a984670fb in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0
#23 0x00007f3a9846a8cd in ?? () from /usr/lib64/libglib-2.0.so.0
#24 0x00007f3a9846aa8b in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#25 0x00007f3a9ee2256c in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#26 0x00007f3a9dbae03f in ?? () from /usr/lib64/libQtGui.so.4
#27 0x00007f3a9edf79e2 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#28 0x00007f3a9edf7db4 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#29 0x00007f3a9edfa0a4 in QCoreApplication::exec() () from /usr/lib64/libQtCore.so.4
#30 0x0000000000404995 in _start ()
Comment 1 Myriam Schweingruber 2012-08-19 11:04:10 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