[Bug 159079] New: crash upon a certain imap message copy

[Alan Braslau]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=159079         
           Summary: crash upon a certain imap message copy
           Product: kmail
           Version: 1.9.9
          Platform: Debian testing
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: crash
          Priority: NOR
         Component: general
        AssignedTo: kdepim-bugs kde org
        ReportedBy: alan.braslau cea fr


Version:           1.9.9 (using KDE 3.5.9)
Installed from:    Debian testing/unstable Packages

I'm sorry but this bug/crash report will not be very useful for the maintainers as I cannot provide a decent description and recipe to reproduce. Nevertheless, I am reporting it to signal the problem...

A certain simple email message:
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"
MIME-Version: 1.0
repeatedly and systematically caused kmail to crash upon attempts to copy from the inbox to another folder, either local or remote imap. (I am using maildir format if this be of any help...). Following is a detailed backtrace:

(no debugging symbols found)
Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb57c36c0 (LWP 18004)]
[New Thread 0xb3995b90 (LWP 18018)]
[New Thread 0xb4196b90 (LWP 18016)]
[New Thread 0xb4997b90 (LWP 18015)]
[New Thread 0xb5198b90 (LWP 18014)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[KCrash handler]
#6  0xb7ba5109 in KMFolder::open () from /usr/lib/libkmailprivate.so
#7  0xb7d0e45b in KMMoveCommand::execute () from /usr/lib/libkmailprivate.so
#8  0xb7cfcd69 in KMCommand::slotPostTransfer ()
   from /usr/lib/libkmailprivate.so
#9  0xb7d076c2 in KMCommand::qt_invoke () from /usr/lib/libkmailprivate.so
#10 0xb7d07a8b in KMMenuCommand::qt_invoke () from /usr/lib/libkmailprivate.so
#11 0xb7d07aeb in KMMoveCommand::qt_invoke () from /usr/lib/libkmailprivate.so
#12 0xb6fef00d in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#13 0xb7cfb0cf in KMCommand::messagesTransfered ()
   from /usr/lib/libkmailprivate.so
#14 0xb7d08859 in KMCommand::transferSelectedMsgs ()
   from /usr/lib/libkmailprivate.so
#15 0xb7d08a17 in KMCommand::slotStart () from /usr/lib/libkmailprivate.so
#16 0xb7d076a7 in KMCommand::qt_invoke () from /usr/lib/libkmailprivate.so
#17 0xb7d07a8b in KMMenuCommand::qt_invoke () from /usr/lib/libkmailprivate.so
#18 0xb7d07aeb in KMMoveCommand::qt_invoke () from /usr/lib/libkmailprivate.so
#19 0xb6fef00d in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#20 0xb73191be in QSignal::signal () from /usr/lib/libqt-mt.so.3
#21 0xb700a967 in QSignal::activate () from /usr/lib/libqt-mt.so.3
#22 0xb7011a33 in QSingleShotTimer::event () from /usr/lib/libqt-mt.so.3
#23 0xb6f911ca in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3
#24 0xb6f91fb6 in QApplication::notify () from /usr/lib/libqt-mt.so.3
#25 0xb7641ec2 in KApplication::notify () from /usr/lib/libkdecore.so.4
#26 0xb6f865ae in QEventLoop::activateTimers () from /usr/lib/libqt-mt.so.3
#27 0xb6f40388 in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3
#28 0xb6fa7bc0 in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
#29 0xb6fa7a56 in QEventLoop::exec () from /usr/lib/libqt-mt.so.3
#30 0xb6f90d3f in QApplication::exec () from /usr/lib/libqt-mt.so.3
#31 0x0804a2ed in ?? ()
#32 0xbfae9a20 in ?? ()
#33 0xbfae9c10 in ?? ()
#34 0x00000000 in ?? ()


My solution was to save the message to a file using mutt. Kmail then has no problem then accessing the saved message.

Sorry again if I cannot provide more information. It is a quirky bug that will probably be very hard to attack. The maintainers will most likely want to close this bug as there is no further means of testing since the offending message has been resolved.

Keep up the work to get kmail to be more and more robust (and to get it into kde4). Thanks.

Alan