Bug 209259 - Kontact crashes after deleting multiple popup notes (always reproducible) [KNotesResourceManager::deleteNote, KNotesPart::killSelectedNotes]
Summary: Kontact crashes after deleting multiple popup notes (always reproducible) [KN...
Status: RESOLVED WORKSFORME
Alias: None
Product: kontact
Classification: Applications
Component: notes (show other bugs)
Version: unspecified
Platform: Unlisted Binaries Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
: 206292 217648 (view as bug list)
Depends on:
Blocks:
 
Reported: 2009-10-03 01:16 UTC by mm
Modified: 2013-02-14 11:12 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
New crash information added by DrKonqi (5.62 KB, text/plain)
2010-05-14 00:04 UTC, gustgans90
Details
New crash information added by DrKonqi (5.81 KB, text/plain)
2010-12-16 15:16 UTC, Nicolas
Details

Note You need to log in before you can comment on or make changes to this bug.
Description mm 2009-10-03 01:16:59 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-43.fc11.i586 i686

What I was doing when the application crashed:
Always reproducible.
Steps:
Open kontact,
Switch to notes,
Select multiple notes,
Delete them,
Crash.

I am using the IMAP resource functionality, with kolab 2, but I don't known if it matters, I can't find anything related to it in the stack trace at a first sight.

Additionaly, this is the same behaviour as bug #206292,  but the stack trace is different.
I am also getting bug Always reproducible.
Steps:
Open kontact,
Switch to notes,
Select multiple notes,
Delete them,
Crash.

I am using the IMAP resource functionality, with kolab 2, but I don't known if it matters, I can't find anything related to it in the stack trace at a first sight.

This is the same behaviour as bug #206292,  but the stack trace is different, perhaps it is useful.

Additionaly, I am getting the exact stack trace of bug 205489 ( duplicate of #199325), and stack trace of Thread 2 is exactly the same as in this bug. Could this be related ? 

 -- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
[Current thread is 1 (Thread 0xb7ecc780 (LWP 1901))]

Thread 2 (Thread 0xaccffb70 (LWP 27279)):
#0  0x004c4422 in __kernel_vsyscall ()
#1  0x00769fa5 in pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/i386/i486/pthread_cond_wait.S:122
#2  0x059b7337 in QWaitConditionPrivate::wait (time=<value optimized out>, this=<value optimized out>) at thread/qwaitcondition_unix.cpp:87
#3  QWaitCondition::wait (time=<value optimized out>, this=<value optimized out>) at thread/qwaitcondition_unix.cpp:159
#4  0x003be4d2 in QHostInfoAgent::run (this=0x9db4058) at kernel/qhostinfo.cpp:260
#5  0x059b62f2 in QThreadPrivate::start (arg=0x9db4058) at thread/qthread_unix.cpp:188
#6  0x00765935 in start_thread (arg=0xaccffb70) at pthread_create.c:297
#7  0x00d4e94e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130

Thread 1 (Thread 0xb7ecc780 (LWP 1901)):
[KCrash Handler]
#6  KNotesResourceManager::deleteNote (this=0xe31fdf8, journal=0xd25e9e0) at /usr/src/debug/kdepim-4.3.1/knotes/resourcemanager.cpp:109
#7  0x028ca832 in KNotesPart::killSelectedNotes (this=0xe469ef8) at /usr/src/debug/kdepim-4.3.1/kontact/plugins/knotes/knotes_part.cpp:325
#8  0x028cae0b in KNotesPart::qt_metacall (this=0xe469ef8, _c=QMetaObject::InvokeMetaMethod, _id=11, _a=0xbfedb068)
    at /usr/src/debug/kdepim-4.3.1/i586-redhat-linux-gnu/kontact/plugins/knotes/knotes_part.moc:108
#9  0x05abc853 in QMetaObject::activate (sender=0xeba1ba0, from_signal_index=5, to_signal_index=6, argv=0xbfedb068) at kernel/qobject.cpp:3113
#10 0x05abccc8 in QMetaObject::activate (sender=0xeba1ba0, m=0x679a9b0, from_local_signal_index=1, to_local_signal_index=2, argv=0xbfedb068) at kernel/qobject.cpp:3207
#11 0x05f35331 in QAction::triggered (this=0xeba1ba0, _t1=false) at .moc/release-shared/moc_qaction.cpp:236
#12 0x05f368c6 in QAction::activate (this=0xeba1ba0, event=QAction::Trigger) at kernel/qaction.cpp:1160
#13 0x05f393d8 in QAction::event (this=0xa6084c8, e=0x0) at kernel/qaction.cpp:1079
#14 0x068a2073 in KAction::event (this=0xeba1ba0, event=0xbfedb4b8) at /usr/src/debug/kdelibs-4.3.1/kdeui/actions/kaction.cpp:88
#15 0x05f3b974 in QApplicationPrivate::notify_helper (this=0x8638338, receiver=0xeba1ba0, e=0xbfedb4b8) at kernel/qapplication.cpp:4056
#16 0x05f430e9 in QApplication::notify (this=0xbfedd3f4, receiver=0xeba1ba0, e=0xbfedb4b8) at kernel/qapplication.cpp:3603
#17 0x0698960a in KApplication::notify (this=0xbfedd3f4, receiver=0xeba1ba0, event=0xbfedb4b8) at /usr/src/debug/kdelibs-4.3.1/kdeui/kernel/kapplication.cpp:302
#18 0x05aa6b0b in QCoreApplication::notifyInternal (this=0xbfedd3f4, receiver=0xeba1ba0, event=0xbfedb4b8) at kernel/qcoreapplication.cpp:610
#19 0x05f7475d in QCoreApplication::sendEvent (event=<value optimized out>, receiver=<value optimized out>) at ../../src/corelib/kernel/qcoreapplication.h:213
#20 QShortcutMap::dispatchEvent (event=<value optimized out>, receiver=<value optimized out>) at kernel/qshortcutmap.cpp:884
#21 0x05f76616 in QShortcutMap::tryShortcutEvent (this=0x86383d8, o=0xaf66f10, e=0xbfedb864) at kernel/qshortcutmap.cpp:369
#22 0x05f44476 in QApplication::notify (this=0xbfedd3f4, receiver=0xaf66f10, e=0xbfedb864) at kernel/qapplication.cpp:3645
#23 0x0698960a in KApplication::notify (this=0xbfedd3f4, receiver=0xaf66f10, event=0xbfedb864) at /usr/src/debug/kdelibs-4.3.1/kdeui/kernel/kapplication.cpp:302
#24 0x05aa6b0b in QCoreApplication::notifyInternal (this=0xbfedd3f4, receiver=0xaf66f10, event=0xbfedb864) at kernel/qcoreapplication.cpp:610
#25 0x05f3c87e in QCoreApplication::sendSpontaneousEvent (event=<value optimized out>, receiver=<value optimized out>) at ../../src/corelib/kernel/qcoreapplication.h:216
#26 qt_sendSpontaneousEvent (event=<value optimized out>, receiver=<value optimized out>) at kernel/qapplication.cpp:4958
#27 0x05fd74f0 in QKeyMapper::sendKeyEvent (keyWidget=0xaf66f10, grab=false, type=QEvent::KeyPress, code=16777223, modifiers={i = 0}, text=@0xbfedb9e8, autorepeat=<value optimized out>, 
    count=<value optimized out>, nativeScanCode=119, nativeVirtualKey=65535, nativeModifiers=0) at kernel/qkeymapper_x11.cpp:1861
#28 0x05fd9a05 in QKeyMapperPrivate::translateKeyEvent (this=0x8658e90, keyWidget=0xaf66f10, event=0xbfedd05c, grab=false) at kernel/qkeymapper_x11.cpp:1831
#29 0x05faf7af in QApplication::x11ProcessEvent (this=0xbfedd3f4, event=0xbfedd05c) at kernel/qapplication_x11.cpp:3438
#30 0x05fdb5d2 in x11EventSourceDispatch (s=0x862b9a8, callback=0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146
#31 0x058be308 in g_main_dispatch (context=<value optimized out>) at gmain.c:1824
#32 IA__g_main_context_dispatch (context=<value optimized out>) at gmain.c:2377
#33 0x058c19e0 in g_main_context_iterate (context=0x862ac90, block=<value optimized out>, dispatch=1, self=0x8638c88) at gmain.c:2455
#34 0x058c1b13 in IA__g_main_context_iteration (context=0x862ac90, may_block=1) at gmain.c:2518
#35 0x05ad15ec in QEventDispatcherGlib::processEvents (this=0x860aa28, flags={i = 36}) at kernel/qeventdispatcher_glib.cpp:327
#36 0x05fdacb5 in QGuiEventDispatcherGlib::processEvents (this=0x860aa28, flags={i = 36}) at kernel/qguieventdispatcher_glib.cpp:202
#37 0x05aa50d9 in QEventLoop::processEvents (this=0xbfedd354, flags={i = 36}) at kernel/qeventloop.cpp:149
#38 0x05aa552a in QEventLoop::exec (this=0xbfedd354, flags={i = 0}) at kernel/qeventloop.cpp:201
#39 0x05aa79af in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#40 0x05f3b7f7 in QApplication::exec () at kernel/qapplication.cpp:3525
#41 0x0804b2e6 in main (argc=3, argv=0xbfedd614) at /usr/src/debug/kdepim-4.3.1/kontact/src/main.cpp:218

Reported using DrKonqi
Comment 1 FiNeX 2009-10-03 12:25:27 UTC
*** Bug 206292 has been marked as a duplicate of this bug. ***
Comment 2 FiNeX 2009-12-06 22:58:23 UTC
*** Bug 217648 has been marked as a duplicate of this bug. ***
Comment 3 gustgans90 2010-05-14 00:04:42 UTC
Created attachment 43556 [details]
New crash information added by DrKonqi

It happens exactly the same as discribed before.
Comment 4 Nicolas 2010-12-16 15:16:42 UTC
Created attachment 54823 [details]
New crash information added by DrKonqi

kontact (4.4.6) on KDE Platform 4.5.1 (KDE 4.5.1) using Qt 4.7.0

- What I was doing when the application crashed:

Kontact crashes as soon as I want to delete a note. This Stacktrace has been produced when I deleted a single note.

-- Backtrace (Reduced):
#6  KNotesResourceManager::deleteNote (this=0x4951af0, journal=0x48d6d90) at ../../../../knotes/resourcemanager.cpp:109
#7  0x00007fe1bdbcf549 in KNotesPart::killSelectedNotes (this=0x5addb00) at ../../../../kontact/plugins/knotes/knotes_part.cpp:354
#8  0x00007fe1bdbd0340 in KNotesPart::qt_metacall (this=0x5addb00, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff235e6b40) at ./knotes_part.moc:114
[...]
#10 0x00007fe1d9464852 in QAction::triggered (this=0x0, _t1=false) at .moc/release-shared/moc_qaction.cpp:263
#11 0x00007fe1d9465f5b in QAction::activate (this=0x22bb0d0, event=<value optimized out>) at kernel/qaction.cpp:1256
Comment 5 Myriam Schweingruber 2013-02-14 11:12:39 UTC
Not reproducible with KDE 4.10, this is most likely solved since quite some time. Please feel free to reopen if you can reproduce this with KDE 4.10 or later.