Bug 175190 - kmail crash then resive mail
Summary: kmail crash then resive mail
Status: RESOLVED DUPLICATE of bug 169991
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: 2008-11-15 06:29 UTC by vecheslav
Modified: 2009-03-19 00:35 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 vecheslav 2008-11-15 06:29:58 UTC
Version:            (using KDE 3.5.9)
OS:                Linux
Installed from:    SuSE RPMs

роверка системной конфигурации при запуске выключена.

[?1034h(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 0xb56ec6d0 (LWP 4014)]
[New Thread 0xb3833b90 (LWP 4020)]
[New Thread 0xb4034b90 (LWP 4019)]
[New Thread 0xb4835b90 (LWP 4018)]
[New Thread 0xb5036b90 (LWP 4017)]
(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)
(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  0xb6d43448 in KMime::decodeRFC2047String ()
   from /opt/kde3/lib/libkmime.so.2
#7  0xb6d43534 in KMime::decodeRFC2047String ()
   from /opt/kde3/lib/libkmime.so.2
#8  0xb7edeabd in KPIM::normalizeAddressesAndDecodeIDNs ()
   from /opt/kde3/lib/libkmailprivate.so
#9  0xb7ada21c in KMMessage::from () from /opt/kde3/lib/libkmailprivate.so
#10 0xb7add9cf in KMMessage::fromStrip () from /opt/kde3/lib/libkmailprivate.so
#11 0xb7c51d0b in KMMsgBase::asIndexString ()
   from /opt/kde3/lib/libkmailprivate.so
#12 0xb7cbc9b8 in KMFolderMaildir::addMsgInternal ()
   from /opt/kde3/lib/libkmailprivate.so
#13 0xb7cbccd7 in KMFolderMaildir::addMsg ()
   from /opt/kde3/lib/libkmailprivate.so
#14 0xb7bc3b85 in KMFolder::addMsg () from /opt/kde3/lib/libkmailprivate.so
#15 0xb7b7516c in KMAccount::processNewMsg ()
   from /opt/kde3/lib/libkmailprivate.so
#16 0xb7cbf500 in KMail::PopAccount::slotProcessPendingMsgs ()
   from /opt/kde3/lib/libkmailprivate.so
#17 0xb7cc64f3 in KMail::PopAccount::qt_invoke ()
   from /opt/kde3/lib/libkmailprivate.so
#18 0xb724479a in QObject::activate_signal ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#19 0xb7246cdb in QObject::activate_signal ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#20 0xb75a9db9 in QTimer::timeout () from /usr/lib/qt3/lib/libqt-mt.so.3
#21 0xb7268f7c in QTimer::event () from /usr/lib/qt3/lib/libqt-mt.so.3
#22 0xb71df3cd in QApplication::internalNotify ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#23 0xb71e0406 in QApplication::notify () from /usr/lib/qt3/lib/libqt-mt.so.3
#24 0xb78ce892 in KApplication::notify () from /opt/kde3/lib/libkdecore.so.4
#25 0xb71d4b1b in QEventLoop::activateTimers ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#26 0xb718a591 in QEventLoop::processEvents ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#27 0xb71f7d10 in QEventLoop::enterLoop () from /usr/lib/qt3/lib/libqt-mt.so.3
#28 0xb71f7ba6 in QEventLoop::exec () from /usr/lib/qt3/lib/libqt-mt.so.3
#29 0xb71dfa5f in QApplication::exec () from /usr/lib/qt3/lib/libqt-mt.so.3
#30 0x0804a32c in ?? ()
#31 0xb6d855f5 in __libc_start_main () from /lib/libc.so.6
#32 0x0804a081 in ?? ()
Comment 1 Jaime Torres 2008-11-15 09:54:21 UTC
Even the back trace is not complete, it looks like a problem in KMime::decodeRFC2047String. 

To try to reproduce the crash, Is it possible to have a copy of the mail? 
If it contains personal information, you could try to remove the personal data, or as you wish, send it privately to me (jtamate at gmail dot com).

Thanks.
Comment 2 vecheslav 2008-11-15 10:50:59 UTC
Hi Jamie!
I send mail to jtamate at gmail dot com maibox

Comment 3 Christophe Marin 2008-11-15 10:53:50 UTC

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