Bug 228505 - Trying to edit a message in draft folder
Summary: Trying to edit a message in draft folder
Status: RESOLVED DUPLICATE of bug 241769
Alias: None
Product: kmail
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: 2010-02-25 19:04 UTC by Martin L ü c h e m
Modified: 2010-11-22 17:32 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 L ü c h e m 2010-02-25 19:04:04 UTC
Application that crashed: kmail
Version of the application: 1.12.4
KDE Version: 4.3.4 (KDE 4.3.4)
Qt Version: 4.5.3
Operating System: Linux 2.6.30-2-amd64 x86_64
Distribution: Debian GNU/Linux 5.0.4 (lenny)

What I was doing when the application crashed:
Trying to edit a message in the kmail draft folder. KMail crashes with double click.

 -- Backtrace:
Application: KMail (kmail), signal: Aborted
The current source language is "auto; currently c".
[KCrash Handler]
#27 KMFolderNode::parent (this=0x27b0ae0) at ../../kmail/kmfoldernode.cpp:43
#28 0x00007fdae840a713 in KMFolder::idString (this=0x7fdae6979008) at ../../kmail/kmfolder.cpp:758
#29 0x00007fdae853829b in KMKernel::folderIsDrafts (this=0x7fff4dae91a0, folder=0x7fdae6979008) at ../../kmail/kmkernel.cpp:2031
#30 0x00007fdae871494b in KMail::MessageActions::editCurrentMessage (this=0x3a07b40) at ../../kmail/messageactions.cpp:360
#31 0x00007fdae85f1edc in KMMainWidget::slotMsgActivated (this=0x3477750, msg=0x4ab01f0) at ../../kmail/kmmainwidget.cpp:3355
#32 0x00007fdae860c17c in KMMainWidget::qt_metacall (this=0x3477750, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff4dae6530) at ./kmmainwidget.moc:361
#33 0x00007fdae7c16df2 in QMetaObject::activate (sender=0x3478820, from_signal_index=<value optimized out>, to_signal_index=69, argv=0x7fff4dae6530) at kernel/qobject.cpp:3112
#34 0x00007fdae8331002 in KMail::MessageListView::Pane::messageActivated (this=0x27b0ae0, _t1=0x4ab01f0) at moc_pane.cpp:133
#35 0x00007fdae833198c in KMail::MessageListView::Pane::qt_metacall (this=0x3478820, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff4dae6660) at moc_pane.cpp:109
#36 0x00007fdae7c16df2 in QMetaObject::activate (sender=0x347c980, from_signal_index=<value optimized out>, to_signal_index=49, argv=0x7fff4dae6530) at kernel/qobject.cpp:3112
#37 0x00007fdae8330ea2 in KMail::MessageListView::Widget::messageActivated (this=0x27b0ae0, _t1=0x4ab01f0) at moc_widget.cpp:103
#38 0x00007fdae70cb1fe in QWidget::event (this=0x34a2640, event=0x7fff4dae7440) at kernel/qwidget.cpp:7558
#39 0x00007fdae743392b in QFrame::event (this=0x34a2640, e=0x7fff4dae7440) at widgets/qframe.cpp:559
#40 0x00007fdae756598b in QAbstractItemView::viewportEvent (this=0x34a2640, event=0x7fff4dae7440) at itemviews/qabstractitemview.cpp:1476
#41 0x00007fdae759d689 in QTreeView::viewportEvent (this=0x34a2640, event=0x7fff4dae7440) at itemviews/qtreeview.cpp:1266
#42 0x00007fdae7c00fb8 in QCoreApplicationPrivate::sendThroughObjectEventFilters (this=<value optimized out>, receiver=0x34d6660, event=0x7fff4dae7440) at kernel/qcoreapplication.cpp:726
#43 0x00007fdae707afec in QApplicationPrivate::notify_helper (this=0x22fd120, receiver=0x34d6660, e=0x7fff4dae7440) at kernel/qapplication.cpp:4061
#44 0x00007fdae70837ca in QApplication::notify (this=<value optimized out>, receiver=0x34d6660, e=0x7fff4dae7440) at kernel/qapplication.cpp:3767
#45 0x00007fdae92a1e06 in KApplication::notify (this=0x7fff4dae92f0, receiver=0x34d6660, event=0x7fff4dae7440) at ../../kdeui/kernel/kapplication.cpp:302
#46 0x00007fdae7c01c9c in QCoreApplication::notifyInternal (this=0x7fff4dae92f0, receiver=0x34d6660, event=0x7fff4dae7440) at kernel/qcoreapplication.cpp:610
#47 0x00007fdae7082a78 in QCoreApplication::sendSpontaneousEvent (receiver=0x34d6660, event=0x7fff4dae7440, alienWidget=0x34d6660, nativeWidget=0x3477750, buttonDown=<value optimized out>, 
    lastMouseReceiver=...) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:216
#48 QApplicationPrivate::sendMouseEvent (receiver=0x34d6660, event=0x7fff4dae7440, alienWidget=0x34d6660, nativeWidget=0x3477750, buttonDown=<value optimized out>, lastMouseReceiver=...)
    at kernel/qapplication.cpp:2924
#49 0x00007fdae70eb659 in QETWidget::translateMouseEvent (this=0x3477750, event=<value optimized out>) at kernel/qapplication_x11.cpp:4411
#50 0x00007fdae70ea40f in QApplication::x11ProcessEvent (this=0x7fff4dae92f0, event=0x7fff4dae8e10) at kernel/qapplication_x11.cpp:3552
#51 0x00007fdae711276c in x11EventSourceDispatch (s=0x2300a70, callback=0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146
#52 0x00007fdadeb7990e in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#53 0x00007fdadeb7d2c8 in ?? () from /lib/libglib-2.0.so.0
#54 0x00007fdadeb7d3f0 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#55 0x00007fdae7c2a39c in QEventDispatcherGlib::processEvents (this=0x22aab40, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:407
#56 0x00007fdae7111f1f in QGuiEventDispatcherGlib::processEvents (this=0x27b0ae0, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202
#57 0x00007fdae7c00562 in QEventLoop::processEvents (this=<value optimized out>, flags=...) at kernel/qeventloop.cpp:149
#58 0x00007fdae7c00934 in QEventLoop::exec (this=0x7fff4dae9140, flags=...) at kernel/qeventloop.cpp:201
#59 0x00007fdae7c02ba4 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#60 0x0000000000402fa9 in main (argc=<value optimized out>, argv=<value optimized out>) at ../../kmail/main.cpp:146

Reported using DrKonqi
Comment 1 Martin L ü c h e m 2010-02-25 22:13:21 UTC
just happened again!
Comment 2 Martin Koller 2010-02-26 19:56:51 UTC
Does it always happen or only with specific mails being in the drafts folder ?
When it happens always, can you run kmail inside valgrind,
e.g.
valgrind kmail --nofork > logfile
and attach the result here, please ?
Comment 3 Martin L ü c h e m 2010-02-26 20:29:41 UTC
Not always but sometimes and with different mails - unfortunately.

Martin
Comment 4 Martin L ü c h e m 2010-07-04 12:39:15 UTC
I do not know if the situation persists. Does someone work on this?
Comment 5 Dario Andres 2010-11-22 17:32:47 UTC
[Comment from a bug triager]
Even if this report is older, I'm going to merge it with the new bug 241769, which contains more information and updated backtraces, so it should be easier to track down the bug. Thanks

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