Application: korgac (4.10.5) KDE Platform Version: 4.10.5 "release 1" Qt Version: 4.8.4 Operating System: Linux 3.7.10-1.16-desktop x86_64 Distribution: "openSUSE 12.3 (x86_64)" -- Information about the crash: - What I was doing when the application crashed: kmail was configured earlier. Configured organiser.ics calendar in system settings -> personal information -> add ical file, pointing it to the file created by KDE 4.7.2 using an older KDE 4.4.11 PIM setup. kmail is running, and its outgoing mail part is waiting for a password from the wallet, the walletmanager password request window is open. Start the organiser by clicking on the desktop symbol - the program run by this is kontac (as per application launcher menu entry for this application). The crash handler starts, giving korgc as application name that crashed. The kontact window opens, seems to be running fine, and the personal calendar configured just before is showing up fine with its entries showing in the calendar (selecting the calendar from the list of icons down the left). - Custom settings of the application: None further that I can think of. -- Backtrace: Application: KOrganizer Reminder Dæmon (korgac), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [KCrash Handler] #6 deref (this=0x2f00300031baa0) at /usr/include/QtCore/qatomic_x86_64.h:133 #7 operator= (l=..., this=0x1709a28) at /usr/include/QtCore/qlist.h:442 #8 QList<Akonadi::Collection>::clear (this=0x1709a28) at /usr/include/QtCore/qlist.h:766 #9 0x00002ab5f086129f in QMetaObject::activate (sender=0x170b840, m=<optimized out>, local_signal_index=<optimized out>, argv=0x0) at kernel/qobject.cpp:3548 #10 0x00002ab5f08605ac in QObject::event (this=0x170b840, e=<optimized out>) at kernel/qobject.cpp:1165 #11 0x00002ab5ef97786c in QApplicationPrivate::notify_helper (this=this@entry=0x148c000, receiver=receiver@entry=0x170b840, e=e@entry=0x7ffffdcc97f0) at kernel/qapplication.cpp:4562 #12 0x00002ab5ef97bceb in QApplication::notify (this=0x7ffffdcc9c00, receiver=0x170b840, e=0x7ffffdcc97f0) at kernel/qapplication.cpp:4423 #13 0x00002ab5eea227f6 in KApplication::notify (this=0x7ffffdcc9c00, receiver=0x170b840, event=0x7ffffdcc97f0) at /usr/src/debug/kdelibs-4.10.5/kdeui/kernel/kapplication.cpp:311 #14 0x00002ab5f084bd8e in QCoreApplication::notifyInternal (this=0x7ffffdcc9c00, receiver=0x170b840, event=0x7ffffdcc97f0) at kernel/qcoreapplication.cpp:946 #15 0x00002ab5f087cb61 in sendEvent (event=0x7ffffdcc97f0, receiver=<optimized out>) at kernel/qcoreapplication.h:231 #16 QTimerInfoList::activateTimers (this=0x148bf70) at kernel/qeventdispatcher_unix.cpp:637 #17 0x00002ab5f0879c54 in timerSourceDispatch (source=<optimized out>) at kernel/qeventdispatcher_glib.cpp:186 #18 timerSourceDispatch (source=<optimized out>) at kernel/qeventdispatcher_glib.cpp:180 #19 0x00002ab5f0879c71 in idleTimerSourceDispatch (source=<optimized out>) at kernel/qeventdispatcher_glib.cpp:233 #20 0x00002ab5f6e017d5 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #21 0x00002ab5f6e01b08 in ?? () from /usr/lib64/libglib-2.0.so.0 #22 0x00002ab5f6e01bc4 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #23 0x00002ab5f087a2c6 in QEventDispatcherGlib::processEvents (this=0x1487d80, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #24 0x00002ab5efa17c1e in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=...) at kernel/qguieventdispatcher_glib.cpp:204 #25 0x00002ab5f084aadf in QEventLoop::processEvents (this=this@entry=0x7ffffdcc9a70, flags=...) at kernel/qeventloop.cpp:149 #26 0x00002ab5f084ad68 in QEventLoop::exec (this=0x7ffffdcc9a70, flags=...) at kernel/qeventloop.cpp:204 #27 0x00002ab5f084fa08 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1218 #28 0x000000000040e582 in main (argc=3, argv=0x7ffffdcc9d48) at /usr/src/debug/kdepim-4.10.5/korganizer/korgac/korgacmain.cpp:96 Possible duplicates by query: bug 322333, bug 322106, bug 317830, bug 316638, bug 311628. Reported using DrKonqi
Using the "restart application" function at the end of the crash reporter restarted the korganiser reminder daemon (which went crazy - looks like the "done" information for todos isn't carried over during a system re-installation with a clean ~/.kde4/).
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present? If noone confirms this bug for a Framework-based version of korgac (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months.
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.