Version: 1.3 (using KDE 4.1.4) OS: Linux Installed from: Ubuntu Packages Program: Kontact (kontact), signal‚ SIGSEGV Thread 1 (Thread 0xb4d4b6c0 (LWP 13123)): [KCrash Handler] #6 0xb176c659 in ?? () from /usr/lib/libkmailprivate.so.4 #7 0xb194f8bc in KMCommand::keepFolderOpen () from /usr/lib/libkmailprivate.so.4 #8 0xb19658b0 in KMCommand::slotStart () from /usr/lib/libkmailprivate.so.4 #9 0xb19565f3 in KMCommand::qt_metacall () from /usr/lib/libkmailprivate.so.4 #10 0xb1956bc2 in ?? () from /usr/lib/libkmailprivate.so.4 #11 0xb7834a60 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #12 0xb78357e2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #13 0xb783adb7 in ?? () from /usr/lib/libQtCore.so.4 #14 0xb783aedc in ?? () from /usr/lib/libQtCore.so.4 #15 0xb782f53f in QObject::event () from /usr/lib/libQtCore.so.4 #16 0xb6f108ec in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4 #17 0xb6f1872e in QApplication::notify () from /usr/lib/libQtGui.so.4 #18 0xb7ceed1d in KApplication::notify () from /usr/lib/libkdeui.so.5 #19 0xb781fe61 in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4 #20 0xb784dd81 in ?? () from /usr/lib/libQtCore.so.4 #21 0xb784a520 in ?? () from /usr/lib/libQtCore.so.4 #22 0xb56396f8 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #23 0xb563cda3 in ?? () from /usr/lib/libglib-2.0.so.0 #24 0xb563cf61 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #25 0xb784a478 in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4 #26 0xb6faaea5 in ?? () from /usr/lib/libQtGui.so.4 #27 0xb781e52a in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4 #28 0xb781e6ea in QEventLoop::exec () from /usr/lib/libQtCore.so.4 #29 0xb7820da5 in QCoreApplication::exec () from /usr/lib/libQtCore.so.4 #30 0xb6f10767 in QApplication::exec () from /usr/lib/libQtGui.so.4 #31 0x0804bf52 in _start ()
What were you doing when the application crashed ? If you can reproduce the crash at will, may you read http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports and post a complete backtrace here? You need to install the "kdepim-dbg" package Thanks :) This may be related to bug 176845 / bug 117415
Marking as NEEDSINFO
Created attachment 33020 [details] Plasms Crash report This is the report that Plasma produced as a result of the crash and subsequent restart of plasma.
Comment on attachment 33020 [details] Plasms Crash report This is KDE version 4.2.2 on a fresh install
I have the latest updates installed from launchpad. After marking a to-do completed ( feature add journal entry enabled), noticed that to-do data was entered to a journal entry created earlier in the day, instead of a new entry. After this, trying to edit ANY previous journal entry crashes with a signal 11. Creating a new Journal entry does not cause a crash, only on re-edit. All other modules work as expected. Like before, a symbol, or index tag in the *.ics file got corrupted on write. I looked at the *.ics file with an editor, and could not see any VJOURNAL tags mismatched. Would any html tags in the journal body be causing this? I copy and paste from web pages text to the journal as supporting to correspondence I receive. The rich text toggle is off. I believe that there were problems earlier with corruption on load when reading in the VJOURNAL sections. The fix then was to remove the entries from the *.ics file, save, then Kontact would load ok. I also could not get the Knotes module in Kontact to see older Knotes VJOURNAL entries I restored in the Knotes directory. This must be not recognizing the tokens from Kontact in 8.04 after a clean install to 9.04 on my laptop.
comment #5 indicates a bug in korganizer. but the backtrace from the original report indicates a KMail bug (from an old version). I think we should INVALIDate this bug and start a new one for the problem indicated in comment#5
This bug is already as NEEDSINFO. @harryl@owc.net: please file a new bug for the comment 5 description Thanks!
Created attachment 33893 [details] KDE Crash Handler Output
The last crash (comment 8) is unrelated
Harry of comment 5 sent me an email: a KDE update (launchpad packages) fixed the issue for him.