Bug 214188 - kmail crashed when killed after freeze
Summary: kmail crashed when killed after freeze
Status: RESOLVED UNMAINTAINED
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: 2009-11-11 23:12 UTC by Jan Essert
Modified: 2018-09-04 18:18 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 Jan Essert 2009-11-11 23:12:33 UTC
Application that crashed: kmail
Version of the application: 1.12.3
KDE Version: 4.3.3 (KDE 4.3.3)
Qt Version: 4.5.3
Operating System: Linux 2.6.31-gentoo-r5 x86_64

What I was doing when the application crashed:
Kmail froze, reason unknown.

I killed it via "killall kmail" which led to this crash.

 -- Backtrace:
Application: KMail (kmail), signal: Aborted
The current source language is "auto; currently asm".
[KCrash Handler]
#26 0x00007f41747fdf0b in connect () at ../sysdeps/unix/syscall-template.S:82
#27 0x00007f416a3628b4 in ?? () from /usr/lib64/libfam.so.0
#28 0x00007f416a362cda in FAMOpen () from /usr/lib64/libfam.so.0
#29 0x00007f416f35f799 in KDirWatchPrivate (this=0x2270500) at /var/tmp/portage/kde-base/kdelibs-4.3.3/work/kdelibs-4.3.3/kio/kio/kdirwatch.cpp:164
#30 0x00007f416f35fc9f in createPrivate () at /var/tmp/portage/kde-base/kdelibs-4.3.3/work/kdelibs-4.3.3/kio/kio/kdirwatch.cpp:78
#31 0x00007f416f35fcd3 in KDirWatch (this=0x22704e0, parent=<value optimized out>) at /var/tmp/portage/kde-base/kdelibs-4.3.3/work/kdelibs-4.3.3/kio/kio/kdirwatch.cpp:1613
#32 0x00007f4170c77551 in KEmoticons (this=0x2215280) at /var/tmp/portage/kde-base/kdelibs-4.3.3/work/kdelibs-4.3.3/kutils/kemoticons/kemoticons.cpp:121
#33 0x00007f416ed84779 in operator-> (plainText=<value optimized out>, flags=<value optimized out>, maxUrlLen=<value optimized out>, maxAddressLen=<value optimized out>)
    at /var/tmp/portage/kde-base/kdepimlibs-4.3.3/work/kdepimlibs-4.3.3/kpimutils/linklocator.cpp:65
#34 KPIMUtils::LinkLocator::convertToHtml (plainText=<value optimized out>, flags=<value optimized out>, maxUrlLen=<value optimized out>, maxAddressLen=<value optimized out>)
    at /var/tmp/portage/kde-base/kdepimlibs-4.3.3/work/kdepimlibs-4.3.3/kpimutils/linklocator.cpp:423
#35 0x00007f41764f3b34 in strToHtml (str=..., flags=110) at /var/tmp/portage/kde-base/kmail-4.3.3/work/kmail-4.3.3/kmail/headerstyle.cpp:79
#36 0x00007f41764f7f6f in KMail::FancyHeaderStyle::format (this=<value optimized out>, message=<value optimized out>, strategy=<value optimized out>, vCardName=<value optimized out>, 
    printing=<value optimized out>, topLevel=true) at /var/tmp/portage/kde-base/kmail-4.3.3/work/kmail-4.3.3/kmail/headerstyle.cpp:563
#37 0x00007f41763968f6 in KMReaderWin::writeMsgHeader (this=0x1aa98a0, aMsg=<value optimized out>, hasVCard=false, topLevel=<value optimized out>)
    at /var/tmp/portage/kde-base/kmail-4.3.3/work/kmail-4.3.3/kmail/kmreaderwin.cpp:1791
#38 0x00007f417639e5d7 in KMReaderWin::parseMsg (this=0x1aa98a0, aMsg=0x220ec80) at /var/tmp/portage/kde-base/kmail-4.3.3/work/kmail-4.3.3/kmail/kmreaderwin.cpp:1678
#39 0x00007f417638d5fa in KMReaderWin::displayMessage (this=0x1aa98a0) at /var/tmp/portage/kde-base/kmail-4.3.3/work/kmail-4.3.3/kmail/kmreaderwin.cpp:1608
#40 0x00007f417638d7d4 in KMReaderWin::updateReaderWin (this=0x1aa98a0) at /var/tmp/portage/kde-base/kmail-4.3.3/work/kmail-4.3.3/kmail/kmreaderwin.cpp:1548
#41 0x00007f417639a88d in KMReaderWin::qt_metacall (this=0x1aa98a0, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff1f0feb60)
    at /var/tmp/portage/kde-base/kmail-4.3.3/work/kmail-4.3.3_build/kmail/kmreaderwin.moc:168
#42 0x00007f4175ba30da in QMetaObject::activate (sender=<value optimized out>, from_signal_index=<value optimized out>, to_signal_index=<value optimized out>, argv=0xffffffffffffffff)
    at kernel/qobject.cpp:3101
#43 0x00007f4175b9f993 in QObject::event (this=0x1aa9948, e=0x7fff1f0f2f70) at kernel/qobject.cpp:1066
#44 0x00007f4175156bdc in QApplicationPrivate::notify_helper (this=0x1686e90, receiver=0x1aa9948, e=0x7fff1f0ff180) at kernel/qapplication.cpp:4065
#45 0x00007f417515c488 in QApplication::notify (this=0x7fff1f0ff5d0, receiver=0x1aa9948, e=0x7fff1f0ff180) at kernel/qapplication.cpp:4030
#46 0x00007f417720f6b6 in KApplication::notify (this=0x7fff1f0ff5d0, receiver=0x1aa9948, event=0x7fff1f0ff180)
    at /var/tmp/portage/kde-base/kdelibs-4.3.3/work/kdelibs-4.3.3/kdeui/kernel/kapplication.cpp:302
#47 0x00007f4175b919fb in QCoreApplication::notifyInternal (this=0x7fff1f0ff5d0, receiver=0x1aa9948, event=0x7fff1f0ff180) at kernel/qcoreapplication.cpp:606
#48 0x00007f4175bb871a in QCoreApplication::sendEvent (this=0x168a700) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#49 QTimerInfoList::activateTimers (this=0x168a700) at kernel/qeventdispatcher_unix.cpp:580
#50 0x00007f4175bb61ad in timerSourceDispatch (source=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:165
#51 0x00007f416cfba53d in g_main_dispatch (context=0x1689520) at gmain.c:1960
#52 IA__g_main_context_dispatch (context=0x1689520) at gmain.c:2513
#53 0x00007f416cfbdef8 in g_main_context_iterate (context=0x1689520, block=<value optimized out>, dispatch=<value optimized out>, self=<value optimized out>) at gmain.c:2591
#54 0x00007f416cfbe020 in IA__g_main_context_iteration (context=0x1689520, may_block=1) at gmain.c:2654
#55 0x00007f4175bb60f6 in QEventDispatcherGlib::processEvents (this=0x16862a0, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:327
#56 0x00007f41751dbc8e in QGuiEventDispatcherGlib::processEvents (this=0x17, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202
#57 0x00007f4175b90422 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149
#58 0x00007f4175b905bd in QEventLoop::exec (this=0x7fff1f0ff420, flags=) at kernel/qeventloop.cpp:197
#59 0x00007f4175b923a9 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#60 0x0000000000403049 in main (argc=<value optimized out>, argv=<value optimized out>) at /var/tmp/portage/kde-base/kmail-4.3.3/work/kmail-4.3.3/kmail/main.cpp:146

Reported using DrKonqi
Comment 1 Christophe Marin 2009-11-12 09:49:48 UTC
Unfortunately, we can't conclude anything from your backtrace.

If you experience this freeze again, you may try that:

- find the process id of kmail: pidof kmail
- attach gdb to this process: gdb kmail pid (where 'pid' is the number you got above)
- When the debug symbols are loaded: thread apply all backtrace

More details on this page: http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_with_GDB

Also, 'reason unknown' is not very helpful. What were you doing before? How did you see that KMail froze? Any clue is important.

Thanks.

Changing the bug status, please change it back to 'unconfirmed' if you get more informations.
Comment 2 Andrew Crouthamel 2018-09-04 18:18:40 UTC
Hello! Sorry to be the bearer of bad news, but this version of Kmail has been unmaintained for many years so I am closing this bug. Please try using the latest version of Kmail to see if your issue persists. If it does, please submit a new bug in "kmail2". Thank you!