Here is a screenshot of the knotes I have. I know it just shows the notes, but maybe it will provide some additional information:

http://www.3111skyline.com/download/openSUSE_bugs/kde4/screenshots/screenshot-knotes.jpeg

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

Changing the bug status.

Unfortunately, the backtrace is not useful. If you can reproduce this bug, please read the following page and paste a better one: http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports

@David: could you try to install "kdepimlibs4-debuginfo" and
"kdepim4-debuginfo" (names may be wrong) ? Thanks

Dario,

    I have all the debuginfo packages installed:

kdelibs4-debuginfo-4.2.88svn973768-3.1
kdepim4-debuginfo-4.2.88svn973768-1.1
kdepimlibs4-debuginfo-4.2.88svn973768-1.1
libkdepimlibs4-4.2.88svn973768-85.1

    I can recreate the crash regularly. I'll go collect a few more backtraces and report back. 

    Christophe,

    I had been through http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports and that is what led me to load all the debuginfo files. I don't know why the backtrace was so short. I'll go collect more.

    Do you guys want me to report back here under 195247 or under bug 142340?

Created attachment 34276 [details]
second backtrace from the next crash

OK,

    All I had to do was open kontact, then choose "new note", then type a sentence and close the note and kontact crashed. Even with all the debuginfo files installed, I still don't think I got a full backtrace. (I'll add it as an attachment)

    After the crash, a single note appeared in kicker at the right side of where open applications are usually shown. If I clicked on the note, it would put the "Bold Italic Underline.." menu inside of kicker??? I took a screenshot because I knew you would be saying, "WTF?".

http://www.3111skyline.com/download/openSUSE_bugs/kde4/screenshots/knotes-in-kicker.jpeg

Here is the final thought for this evening. Even though kontact segfaults when a note is saved, the notes apparently are saved before the crash. When I restart kontact or korganizer, the notes that were edited are there. here is the screenshot:

http://www.3111skyline.com/download/openSUSE_bugs/kde4/screenshots/knotes-saved.jpeg

Additionally, I reinstalled all the debuginfo files and now I have a better backtrace. Here it is:

Created attachment 34278 [details]
Backtrace after debuginfo reinstall

Hopefully this is a better backtrace. Let me know what else I can send or post. Thanks.

(pasting inline)
Application: Kontact (kontact), signal: Segmentation fault
[KCrash Handler]
#5  KCal::CustomProperties::nonKDECustomProperty (this=0x2067e30, name=@0x7fffbfee4490) at /usr/include/QtCore/qmap.h:431
#6  0x00007fa0b5e731c4 in KCal::CustomProperties::customProperty (this=0x2067e30, app=<value optimized out>, key=@0x7fffbfee4610)
    at /usr/src/debug/kdepimlibs-4.2.88svn973768/kcal/customproperties.cpp:117
#7  0x00007fa0a0493b16 in KNoteTip::setNote (this=0x178aed0, item=<value optimized out>) at /usr/src/debug/kdepim-4.2.88svn973768/kontact/plugins/knotes/knotetip.cpp:90
#8  0x00007fa0a048d4b6 in KNotesPart::requestToolTip (this=0x1498390, index=<value optimized out>) at /usr/src/debug/kdepim-4.2.88svn973768/kontact/plugins/knotes/knotes_part.cpp:142
#9  0x00007fa0a0490dfc in KNotesPart::qt_metacall (this=0x1498390, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fffbfee4810)
    at /usr/src/debug/kdepim-4.2.88svn973768/build/kontact/plugins/knotes/knotes_part.moc:110
#10 0x00007fa0b358c842 in QMetaObject::activate () from /usr/lib64/libQtCore.so.4
#11 0x00007fa0b275fe95 in QAbstractItemView::entered () from /usr/lib64/libQtGui.so.4
#12 0x00007fa0b276b52e in QAbstractItemView::mouseMoveEvent () from /usr/lib64/libQtGui.so.4
#13 0x00007fa0b27822ba in QListView::mouseMoveEvent () from /usr/lib64/libQtGui.so.4
#14 0x00007fa0b22b8908 in QWidget::event () from /usr/lib64/libQtGui.so.4
#15 0x00007fa0b263a4eb in QFrame::event () from /usr/lib64/libQtGui.so.4
#16 0x00007fa0b276feed in QAbstractItemView::viewportEvent () from /usr/lib64/libQtGui.so.4
#17 0x00007fa0b3576018 in QCoreApplicationPrivate::sendThroughObjectEventFilters () from /usr/lib64/libQtCore.so.4
#18 0x00007fa0b22676dc in QApplicationPrivate::notify_helper () from /usr/lib64/libQtGui.so.4
#19 0x00007fa0b22700fa in QApplication::notify () from /usr/lib64/libQtGui.so.4
#20 0x00007fa0b43b224b in KApplication::notify () from /usr/lib64/libkdeui.so.5
#21 0x00007fa0b3576d1c in QCoreApplication::notifyInternal () from /usr/lib64/libQtCore.so.4
#22 0x00007fa0b226f348 in QApplicationPrivate::sendMouseEvent () from /usr/lib64/libQtGui.so.4
#23 0x00007fa0b22d9409 in ?? () from /usr/lib64/libQtGui.so.4
#24 0x00007fa0b22d8475 in QApplication::x11ProcessEvent () from /usr/lib64/libQtGui.so.4
#25 0x00007fa0b22ff7ec in ?? () from /usr/lib64/libQtGui.so.4
#26 0x00007fa0ace1c95a in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0
#27 0x00007fa0ace20060 in ?? () from /usr/lib64/libglib-2.0.so.0
#28 0x00007fa0ace201fc in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#29 0x00007fa0b35a054f in QEventDispatcherGlib::processEvents () from /usr/lib64/libQtCore.so.4
#30 0x00007fa0b22fef3f in ?? () from /usr/lib64/libQtGui.so.4
#31 0x00007fa0b35755a2 in QEventLoop::processEvents () from /usr/lib64/libQtCore.so.4
#32 0x00007fa0b357596d in QEventLoop::exec () from /usr/lib64/libQtCore.so.4
#33 0x00007fa0b3577c74 in QCoreApplication::exec () from /usr/lib64/libQtCore.so.4
#34 0x00000000004049ab in main (argc=1, argv=0x7fffbfee7c08) at /usr/src/debug/kdepim-4.2.88svn973768/kontact/src/main.cpp:218

much better, thanks
(devs: is KCal calendar?)

Created attachment 34295 [details]
3 Star Backtrace on knotes crash running standalone

Guys,

    I think we hit "pay dirt" with this backtrace. I had simple opened knotes as a standalone application. It opened my notes on the desktop. I successfully deleted one note as a test. Then I went to delete a second note and "BAM" -- segfault. The Crash Assistant got the backtrace and gave it 3-stars (I guess that means it is useful).

    Let me know what else I can send and I'll be happy to do it. Thanks.

Created attachment 34296 [details]
3 backtraces from korganizer reminder daemon crash

Probably also related. The korganizer reminder daemon will open korganizer just fine, but every time I close korganizer, it crashes. The daemon is still running in the taskbar and can be reopened without any problem. I thought I would include these backtraces as well. Thanks.

@David: the crashes on comment 12 are bug 171797 (which seems to be unrelated to this issue). Thanks

New information and new weirdness,

Dario,

    I upgraded to kde4beta2 Version 4.2.90 (KDE 4.2.90 (KDE 4.3 Beta2)) "release 139". Now I cannot edit any of my notes. If I edit a note and then quit knotes and then restart, the changes are not saved. If I delete a note and close knotes, the note is back when I start it next time, the note is back. I just tried to start knotes for the third time, and it segfaulted with the following (probably not useful) error:

Application: KNotes (knotes), signal: Segmentation fault
[KCrash Handler]
#5  0x00007fd1baae95d4 in KCal::IncidenceBase::uid (this=0x882380) at /usr/include/QtCore/qstring.h:711
#6  0x000000000043450d in ?? ()
#7  0x000000000041cf42 in _start ()

Starting knotes for the fourth time, then trying to delete a note again, segfaulted with:

Application: KNotes (knotes), signal: Segmentation fault
[KCrash Handler]
#5  KCal::IncidenceBase::uid (this=0x882470) at /usr/include/QtCore/qatomic_x86_64.h:121
#6  0x000000000043bd9b in ?? ()
#7  0x000000000043c4df in ?? ()
#8  0x00007fa709231ef8 in QObject::event (this=0x8871e0, e=0xbc25a0) at kernel/qobject.cpp:1118
#9  0x00007fa709de929d in QWidget::event (this=0x8871e0, event=0xbc25a0) at kernel/qwidget.cpp:7918
#10 0x00007fa70a16b4eb in QFrame::event (this=0x8871e0, e=0xbc25a0) at widgets/qframe.cpp:559
#11 0x00007fa709d9870d in QApplicationPrivate::notify_helper (this=0x6840f0, receiver=0x8871e0, e=0xbc25a0) at kernel/qapplication.cpp:4057
#12 0x00007fa709da099a in QApplication::notify (this=0x7fff15c20600, receiver=0x8871e0, e=0xbc25a0) at kernel/qapplication.cpp:4022
#13 0x00007fa70ac3f24b in KApplication::notify (this=0x7fff15c20600, receiver=0x8871e0, event=0xbc25a0) at /usr/src/debug/kdelibs-4.2.90/kdeui/kernel/kapplication.cpp:302
#14 0x00007fa709221d1c in QCoreApplication::notifyInternal (this=0x7fff15c20600, receiver=0x8871e0, event=0xbc25a0) at kernel/qcoreapplication.cpp:610
#15 0x00007fa7092229aa in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x65bcb0) at kernel/qcoreapplication.h:213
#16 0x00007fa70924b8c3 in postEventSourceDispatch (s=<value optimized out>) at kernel/qcoreapplication.h:218
#17 0x00007fa703b8e95a in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0
#18 0x00007fa703b92060 in ?? () from /usr/lib64/libglib-2.0.so.0
#19 0x00007fa703b921fc in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#20 0x00007fa70924b54f in QEventDispatcherGlib::processEvents (this=0x65b8d0, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:324
#21 0x00007fa709e2ff3f in QGuiEventDispatcherGlib::processEvents (this=0x7fff15c1f970, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202
#22 0x00007fa7092205a2 in QEventLoop::processEvents (this=<value optimized out>, flags={i = 365036848}) at kernel/qeventloop.cpp:149
#23 0x00007fa70922096d in QEventLoop::exec (this=0x7fff15c20570, flags={i = 365036928}) at kernel/qeventloop.cpp:200
#24 0x00007fa709222c74 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#25 0x000000000041b1a9 in _start ()

    Hope this helps!

Here is a repeatable sequence from this morning causing kontact to segfault:

(1) Open kontact (fresh login)- notes shown:

http://www.3111skyline.com/download/openSUSE_bugs/kde4/screenshots/kontact-notes-shown.jpeg

(2) Access notes section of kontact:

http://www.3111skyline.com/download/openSUSE_bugs/kde4/screenshots/kontact-notes-accessed.jpeg

(3) View note:

http://www.3111skyline.com/download/openSUSE_bugs/kde4/screenshots/kontact-notes-viewed.jpeg

kontact crashes when the note is closed - no backtract - no drkonqi - no nothing.

Can you think of more tests that will help isolate this??

Backtrace from comment 14 seems to be another issue.
The report is a bit messy right now :-\ I guess it would need something with more knowledge about KDEPIM to check this.

Regarding the steps on comment 15:
I suggest you the following:

- Open Konsole
- Type "gdb kontact" and press Enter
- Type "run --nofork" and press Enter
Kontact will load
- Reproduce the steps to "crash" the app
Kontact should crash
- Go back to the Konsole/GDB window, type "bt full" and press Enter
You should get a backtrace of the crash (if it is really a crash)

I suggest you to open a NEW report and paste that backtrace there. Pasting a different backtrace in this report will mix it even more.

Thanks

Created attachment 34955 [details]
Knote appeared with middle-mouse on desktop with last saved filename??

While I run the suggested commands, Here is another bit of strangeness to think about. Tonight, I downloaded a file originally named DXZ585USB_ENG,3.pdf in Firefox which I renamed before save to DXZ585USB_ENG-3.pdf.

Now, every time I middle-click on the desktop, a new knote appears with the text "DXZ585USB_ENG,3" already entered in the note. (see attached jpeg file)

How in the heck does plasma/kontact/knotes .. whatever .. pull the original name for a download in Firefox that was "renamed" in the file-save dialog before being saved and stick that into a knote on my desktop in response to a middle-mouse click??

Done, see:

https://bugs.kde.org/show_bug.cgi?id=198493

Crap -- I forgot to change the priority to "Crash". You will have to do that for me Dario, I don't have access. Let me know if you need anything else. Looks like using knotes is out of the question for keeping track of the books my daughter has read for now. It would be a real short list. ;-)

Let's close this one. 198493 is less messy.

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