Bug 124455 - copy encapsulated message to folder succeeds but crashes kmail
Summary: copy encapsulated message to folder succeeds but crashes kmail
Status: RESOLVED WORKSFORME
Alias: None
Product: kmail
Classification: Applications
Component: general (show other bugs)
Version: 1.7.2
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-03-28 23:23 UTC by Alexandros Papadopoulos
Modified: 2007-09-14 12:17 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 Alexandros Papadopoulos 2006-03-28 23:23:31 UTC
Version:           1.7.2 (using KDE 3.3.2,  (3.1))
Compiler:          gcc version 3.3.5 (Debian 1:3.3.5-13)
OS:                Linux (i686) release 2.4.25-1-386

I open an email message that contains (an) encapsulated message(s). Clicking on any "Encapsulated Message" heading displays a new kmail window with the encapsulated message on its own. This is normal.

Now, right-clicking anywhere in that message and selecting "Copy To..." and any destination folder, results in a crash.

After re-running kmail the message is where I told it to be copied, so the copy itself is successful, although kmail crashes.

100% reproducable on my system, with different email messages containing different encapsulated messages.

This is the backtrace:
==============================================================================
(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[...]
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 16384 (LWP 3838)]
(no debugging symbols found)
[...]
(no debugging symbols found)
[KCrash handler]
#5  0x41136571 in QGList::append () from /usr/lib/libqt-mt.so.3
#6  0x40e2281f in QApplication::postEvent () from /usr/lib/libqt-mt.so.3
#7  0x40e7e385 in QObject::deleteLater () from /usr/lib/libqt-mt.so.3
#8  0x4210d938 in KMail::MaildirJob::startJob ()
   from /usr/lib/libkmailprivate.so.0
#9  0x4210db78 in KMail::MaildirJob::qt_invoke ()
   from /usr/lib/libkmailprivate.so.0
#10 0x40e7e71c in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#11 0x411bd62a in QSignal::signal () from /usr/lib/libqt-mt.so.3
#12 0x40e9891d in QSignal::activate () from /usr/lib/libqt-mt.so.3
#13 0x40ea0253 in QSingleShotTimer::event () from /usr/lib/libqt-mt.so.3
#14 0x40e21e1f in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3
#15 0x40e2141e in QApplication::notify () from /usr/lib/libqt-mt.so.3
#16 0x40a51ec3 in KApplication::notify () from /usr/lib/libkdecore.so.4
#17 0x40e11645 in QEventLoop::activateTimers () from /usr/lib/libqt-mt.so.3
#18 0x40dcacfb in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3
#19 0x40e341d8 in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
#20 0x40e34088 in QEventLoop::exec () from /usr/lib/libqt-mt.so.3
#21 0x40e22071 in QApplication::exec () from /usr/lib/libqt-mt.so.3
#22 0x0805919b in ?? ()
#23 0xbffff820 in ?? ()
#24 0x00000001 in ?? ()
#25 0x00000001 in ?? ()
#26 0x00000000 in ?? ()
#27 0x00000000 in ?? ()
#28 0x00000001 in ?? ()
#29 0x08066560 in _IO_stdin_used ()
#30 0x00000000 in ?? ()
#31 0x08065a56 in _IO_stdin_used ()
#32 0x08065a42 in _IO_stdin_used ()
#33 0xbffff848 in ?? ()
#34 0x4023b2fe in operator new () from /usr/lib/libstdc++.so.5
#35 0x402a3e36 in __libc_start_main () from /lib/libc.so.6
#36 0x08058951 in ?? ()
==============================================================================
Comment 1 Alexandros Papadopoulos 2006-03-31 18:29:46 UTC
Wait, it isn't 100% reproducable after all. Perhaps 80% of the time kmail crashes, and 20% it does its job properly. Sorry for the confusion.
Comment 2 Philip Rodrigues 2006-09-19 23:21:05 UTC
Can you reproduce this problem with the KMail form KDE 3.5?
Comment 3 Alexandros Papadopoulos 2006-10-05 22:18:26 UTC
Negative.

Thank you people! :-)