Bug 206292 - KNotes crash after deleting multiple notes
Summary: KNotes crash after deleting multiple notes
Status: RESOLVED DUPLICATE of bug 209259
Alias: None
Product: kontact
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-09-04 22:49 UTC by Eduard Sukharev
Modified: 2009-10-03 12:25 UTC (History)
1 user (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 Eduard Sukharev 2009-09-04 22:49:01 UTC
Application that crashed: kontact
Version of the application: 4.3.1
KDE Version: 4.3.1 (KDE 4.3.1)
Qt Version: 4.5.2
Operating System: Linux 2.6.30.5-yipeee i686

What I was doing when the application crashed:
I've opened KNotes inside the Kontact and found out that i have far too many duplicated notes. Actually, they weren't just duplicated, but ultiplicated. As it turned out there were only two different notes.
I selected one and pressed [delete]. The popup dialog asked if i wanted to delete the note. I decided that deleting might be too tedious with this dialog and so selected most of those notes. Pressed [delete] key and another dialog popped up. When i accepted that i wanted to delete notes the Kontact crashed with SegFault.

 -- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
[KCrash Handler]
#6  0xb1a0d5f7 in KNotesResourceManager::deleteNote () from /usr/lib/kde4/kontact_knotesplugin.so
#7  0xb1a1dae2 in KNotesPart::killSelectedNotes () from /usr/lib/kde4/kontact_knotesplugin.so
#8  0xb1a1e0bb in KNotesPart::qt_metacall () from /usr/lib/kde4/kontact_knotesplugin.so
#9  0xb76f79ac in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#10 0xb76f7df8 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#11 0xb6d2e3f1 in QAction::triggered () from /usr/lib/libQtGui.so.4
#12 0xb6d2f972 in QAction::activate () from /usr/lib/libQtGui.so.4
#13 0xb6d32458 in QAction::event () from /usr/lib/libQtGui.so.4
#14 0xb7b06ac3 in KAction::event () from /usr/lib/libkdeui.so.5
#15 0xb6d34994 in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4
#16 0xb6d3c07c in QApplication::notify () from /usr/lib/libQtGui.so.4
#17 0xb7bed43a in KApplication::notify () from /usr/lib/libkdeui.so.5
#18 0xb76e1fcb in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4
#19 0xb6d6d26d in ?? () from /usr/lib/libQtGui.so.4
#20 0xb6d6f0de in ?? () from /usr/lib/libQtGui.so.4
#21 0xb6d3d385 in QApplication::notify () from /usr/lib/libQtGui.so.4
#22 0xb7bed43a in KApplication::notify () from /usr/lib/libkdeui.so.5
#23 0xb76e1fcb in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4
#24 0xb6d3586e in ?? () from /usr/lib/libQtGui.so.4
#25 0xb6dcf02d in ?? () from /usr/lib/libQtGui.so.4
#26 0xb6dd14cc in ?? () from /usr/lib/libQtGui.so.4
#27 0xb6da7c57 in QApplication::x11ProcessEvent () from /usr/lib/libQtGui.so.4
#28 0xb6dd2f92 in ?? () from /usr/lib/libQtGui.so.4
#29 0xb5150d98 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#30 0xb51543e0 in g_main_context_iterate () from /usr/lib/libglib-2.0.so.0
#31 0xb5154513 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#32 0xb770c6cc in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4
#33 0xb6dd26c5 in ?? () from /usr/lib/libQtGui.so.4
#34 0xb76e0579 in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#35 0xb76e09ca in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#36 0xb76e2e3f in QCoreApplication::exec () from /usr/lib/libQtCore.so.4
#37 0xb6d34817 in QApplication::exec () from /usr/lib/libQtGui.so.4
#38 0x0804b496 in _start ()

This bug may be a duplicate of or related to bug 181406

Reported using DrKonqi
Comment 1 FiNeX 2009-10-03 12:25:27 UTC
bug #209259 has a better backtrace.

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