Bug 261939 - kmail crashes when opening a (malformed?) message with tnef attachment
Summary: kmail crashes when opening a (malformed?) message with tnef attachment
Status: RESOLVED BACKTRACE
Alias: None
Product: kmail
Classification: Applications
Component: messageviewer (show other bugs)
Version: 1.13.5
Platform: Arch Linux Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-01-03 11:12 UTC by Simone Lazzaris
Modified: 2018-03-13 12:52 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Mail that causes the problem (73.95 KB, application/mbox)
2011-01-03 11:12 UTC, Simone Lazzaris
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Simone Lazzaris 2011-01-03 11:12:45 UTC
Created attachment 55508 [details]
Mail that causes the problem

Version:           1.13.5 (using KDE 4.5.4) 
OS:                Linux

I receive many messages composed with outlook that uses tnef attachments (winmail.dat). While I open without problems the most part of them, some are problematic.
When I click on the message to get the preview on those messages, kmail crashes. 
The message is stil marked as "not read" when I restart kmail.

I think that something is not correct in the body of the message, as even thuderbird doesn't show me the content of the tnef attachment; It doesn't crash, anyway. If I save the winmail.dat file (from tbird) and decode with the tnef command, I get the attachments.

I don't know is it's relevant, but the message is stored on a local maildir.

Reproducible: Always

Steps to Reproduce:
Click on the message line in the incoming mail

Actual Results:  
Kmail crashes

Expected Results:  
Preview of the message

I attach here the message that causes the problem. I have more messages, but bigger that this, that causes the problem. I can post them if needed
Comment 1 Christophe Marin 2011-02-14 13:35:52 UTC
Can you paste the backtrace you get when KMail crashes please ?
Comment 2 Simone Lazzaris 2011-02-14 15:59:40 UTC
This is the backtrace; I don't have the debug symbols:


Application: KMail (kmail), signal: Segmentation fault
[Current thread is 1 (Thread 0x7f81020ea760 (LWP 5493))]

Thread 2 (Thread 0x7f80e1d1f700 (LWP 5494)):
#0  0x00007f80fec5c6d3 in select () from /lib/libc.so.6
#1  0x00007f80ff54b6dd in ?? () from /usr/lib/libQtCore.so.4
#2  0x00007f80ff48252e in ?? () from /usr/lib/libQtCore.so.4
#3  0x00007f80fcb0fcb0 in start_thread () from /lib/libpthread.so.0
#4  0x00007f80fec62aed in clone () from /lib/libc.so.6
#5  0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7f81020ea760 (LWP 5493)):
[KCrash Handler]
#6  0x00007f810157d1e1 in KMimeType::iconName(KUrl const&) const () from /usr/lib/libkdecore.so.5
#7  0x00007f8100c7f3ef in ?? () from /usr/lib/libkmailprivate.so.4
#8  0x00007f8100c821cd in ?? () from /usr/lib/libkmailprivate.so.4
#9  0x00007f8100c82575 in ?? () from /usr/lib/libkmailprivate.so.4
#10 0x00007f8100c82904 in ?? () from /usr/lib/libkmailprivate.so.4
#11 0x00007f8100c821cd in ?? () from /usr/lib/libkmailprivate.so.4
#12 0x00007f8100b2846f in ?? () from /usr/lib/libkmailprivate.so.4
#13 0x00007f8100b27300 in ?? () from /usr/lib/libkmailprivate.so.4
#14 0x00007f8100b274c1 in ?? () from /usr/lib/libkmailprivate.so.4
#15 0x00007f8100b2a0c0 in ?? () from /usr/lib/libkmailprivate.so.4
#16 0x00007f80ff58031f in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/libQtCore.so.4
#17 0x00007f80ff57eea9 in QObject::event(QEvent*) () from /usr/lib/libQtCore.so.4
#18 0x00007f80ffa552b4 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#19 0x00007f80ffa59dca in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#20 0x00007f8101b20a46 in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5
#21 0x00007f80ff56ae9c in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQtCore.so.4
#22 0x00007f80ff598a2e in ?? () from /usr/lib/libQtCore.so.4
#23 0x00007f80ff595824 in ?? () from /usr/lib/libQtCore.so.4
#24 0x00007f80f691dbf3 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#25 0x00007f80f691e3d0 in ?? () from /usr/lib/libglib-2.0.so.0
#26 0x00007f80f691e66d in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#27 0x00007f80ff595f0f in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#28 0x00007f80ffafa1ae in ?? () from /usr/lib/libQtGui.so.4
#29 0x00007f80ff56a232 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#30 0x00007f80ff56a47c in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#31 0x00007f80ff56e97b in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4
#32 0x0000000000403108 in _start ()
Comment 3 Christophe Marin 2011-02-14 16:37:41 UTC
There's not much that can be done without the debug info :(
Comment 4 Simone Lazzaris 2011-02-15 10:04:37 UTC
I've downloaded from github the latest version of kdepim and kmail2 doesn't barf on the very same message, so I guess that whatever problem was present is fixed now.

How can I get (via git, I suppose) the source of the latest version on kmail1 (I'm using 1.13.6) so I can test it ?
Comment 5 Simone Lazzaris 2018-03-13 12:52:31 UTC
Closing due to inactivity