Version: (using KDE 4.2.2) OS: Linux Installed from: Ubuntu Packages Hi, I'm not sure whether it belongs two report 180288. My symptom is another. It started with bug report 191193. Now I think the plasma applet is okay. It might be an issue of Kontact. As suggested in 191193 I open another one for it and paste the relevant stuff inside this one: Best Regards Rico After each start up I get a message that kontact is already started. The question in the popup is then open or close. When I press open I have two instances when I press close, no one. Could it be that kontact has issues when it uses Kawallet? Maybe it causes side effects on the widget. When i press open after the popup (kontact is already started) and close then one window Kontact crashes: Anwendung: Kontact (kontact), Signal SIGABRT Thread 1 (Thread 0xb48a4700 (LWP 3642)): [KCrash Handler] #6 0xb8036430 in __kernel_vsyscall () #7 0xb58e06d0 in raise () from /lib/tls/i686/cmov/libc.so.6 #8 0xb58e2098 in abort () from /lib/tls/i686/cmov/libc.so.6 #9 0xb58d95ce in __assert_fail () from /lib/tls/i686/cmov/libc.so.6 #10 0xb101d13c in KMKernel::self () at /build/buildd/kdepim-4.2.2/kmail/kmkernel.cpp:2118 #11 0xb10f538c in kmcrashHandler (sigId=6) at /build/buildd/kdepim-4.2.2/kmail/kmstartup.cpp:69 #12 0xb6dee17a in KCrash::defaultCrashHandler (sig=6) at /build/buildd/kde4libs-4.2.2/kdeui/util/kcrash.cpp:224 #13 <signal handler called> #14 0xb8036430 in __kernel_vsyscall () #15 0xb58e06d0 in raise () from /lib/tls/i686/cmov/libc.so.6 #16 0xb58e2098 in abort () from /lib/tls/i686/cmov/libc.so.6 #17 0xb58d95ce in __assert_fail () from /lib/tls/i686/cmov/libc.so.6 #18 0xb101d13c in KMKernel::self () at /build/buildd/kdepim-4.2.2/kmail/kmkernel.cpp:2118 #19 0xb1107df7 in KMMainWidget::initializeFilterActions (this=0x9733968) at /build/buildd/kdepim-4.2.2/kmail/kmmainwidget.cpp:4761 #20 0xb157a9d6 in KMailPart::guiActivateEvent (this=0x969e4b8, e=0xbfc53908) at /build/buildd/kdepim-4.2.2/kmail/kmail_part.cpp:181 #21 0xb71b2dc4 in KParts::Part::customEvent (this=0x969e4b8, ev=0xbfc53908) at /build/buildd/kde4libs-4.2.2/kparts/part.cpp:321 #22 0xb5c983ff in QObject::event (this=0x969e4b8, e=0xbfc53908) at kernel/qobject.cpp:1149 #23 0xb6158f2c in QApplicationPrivate::notify_helper (this=0x9368ee0, receiver=0x969e4b8, e=0xbfc53908) at kernel/qapplication.cpp:4084 #24 0xb616122e in QApplication::notify (this=0xbfc539d8, receiver=0x969e4b8, e=0xbfc53908) at kernel/qapplication.cpp:3631 #25 0xb6d7d94d in KApplication::notify (this=0xbfc539d8, receiver=0x969e4b8, event=0xbfc53908) at /build/buildd/kde4libs-4.2.2/kdeui/kernel/kapplication.cpp:307 #26 0xb5c87a3b in QCoreApplication::notifyInternal (this=0xbfc539d8, receiver=0x969e4b8, event=0xbfc53908) at kernel/qcoreapplication.cpp:602 #27 0xb71beaba in KParts::MainWindow::createGUI (this=0x94576a0, part=0x0) at /usr/include/qt4/QtCore/qcoreapplication.h:213 #28 0xb78f37d5 in ~MainWindow (this=0x94576a0) at /build/buildd/kdepim-4.2.2/kontact/src/mainwindow.cpp:256 #29 0x0804c0ae in main (argc=3, argv=0xbfc53cd4) at /usr/include/qt4/QtCore/qalgorithms.h:350
This could be related to bug 186898.
*** This bug has been marked as a duplicate of bug 197140 ***