Created attachment 161208 [details]
New crash information added by DrKonqi

DrKonqi auto-attaching complete backtrace.

Which configuration were you changing, in which app?


Pasting full backtrace for searchability:

Thread 1 (Thread 0x7fcd97909240 (LWP 610025)):
[KCrash Handler]
#6  0x00007fcd9d3d7f1c in KCoreConfigSkeleton::load() () at /lib/x86_64-linux-gnu/libKF5ConfigCore.so.5
#7  0x00007fcd9c0f4924 in QtPrivate::QSlotObjectBase::call(QObject*, void**) (a=0x7ffc9e115ed0, r=0x559b9ec56470, this=0x559ba60ae2a0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#8  doActivate<false>(QObject*, int, void**) (sender=0x559b9ec56470, signal_index=3, argv=0x7ffc9e115ed0) at kernel/qobject.cpp:3925
#9  0x00007fcd9d3e96fb in KConfigWatcher::configChanged(KConfigGroup const&, QList<QByteArray> const&) () at /lib/x86_64-linux-gnu/libKF5ConfigCore.so.5
#10 0x00007fcd9d3ea6f9 in  () at /lib/x86_64-linux-gnu/libKF5ConfigCore.so.5
#11 0x00007fcd9d3ea8b2 in KConfigWatcher::qt_metacall(QMetaObject::Call, int, void**) () at /lib/x86_64-linux-gnu/libKF5ConfigCore.so.5
#12 0x00007fcd9cb93feb in QDBusConnectionPrivate::deliverCall(QObject*, int, QDBusMessage const&, QVector<int> const&, int) (this=<optimized out>, object=<optimized out>, msg=<optimized out>, metaTypes=<optimized out>, slotIdx=<optimized out>) at ../../include/QtCore/../../src/corelib/tools/qvarlengtharray.h:189
#13 0x00007fcd9c0ea3ce in QObject::event(QEvent*) (this=0x559b9ec56470, e=0x7fcd90432ba0) at kernel/qobject.cpp:1347
#14 0x00007fcd9cd6c763 in QApplicationPrivate::notify_helper(QObject*, QEvent*) (this=<optimized out>, receiver=0x559b9ec56470, e=0x7fcd90432ba0) at kernel/qapplication.cpp:3640
#15 0x00007fcd9c0bce7a in QCoreApplication::notifyInternal2(QObject*, QEvent*) (receiver=0x559b9ec56470, event=0x7fcd90432ba0) at kernel/qcoreapplication.cpp:1064
#16 0x00007fcd9c0bd052 in QCoreApplication::sendEvent(QObject*, QEvent*) (receiver=<optimized out>, event=<optimized out>) at kernel/qcoreapplication.cpp:1462
#17 0x00007fcd9c0bff77 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) (receiver=0x0, event_type=0, data=0x559b9c251f50) at kernel/qcoreapplication.cpp:1821
#18 0x00007fcd9c0c0410 in QCoreApplication::sendPostedEvents(QObject*, int) (receiver=<optimized out>, event_type=<optimized out>) at kernel/qcoreapplication.cpp:1680
#19 0x00007fcd9c116d17 in postEventSourceDispatch(GSource*, GSourceFunc, gpointer) (s=0x559b9c293b30) at kernel/qeventdispatcher_glib.cpp:277
#20 0x00007fcd9ab6b49d in g_main_dispatch (context=0x7fcd90000ee0) at ../../../glib/gmain.c:3460
#21 g_main_context_dispatch (context=0x7fcd90000ee0) at ../../../glib/gmain.c:4200
#22 0x00007fcd9abc6178 in g_main_context_iterate.constprop.0 (context=0x7fcd90000ee0, block=<optimized out>, dispatch=1, self=<optimized out>) at ../../../glib/gmain.c:4276
#23 0x00007fcd9ab6a1b0 in g_main_context_iteration (context=0x7fcd90000ee0, may_block=1) at ../../../glib/gmain.c:4343
#24 0x00007fcd9c116368 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) (this=0x559b9c298bf0, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#25 0x00007fcd9c0bb79b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) (this=this@entry=0x7ffc9e1164e0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69
#26 0x00007fcd9c0c3d44 in QCoreApplication::exec() () at ../../include/QtCore/../../src/corelib/global/qflags.h:121
#27 0x00007fcd9c536d50 in QGuiApplication::exec() () at kernel/qguiapplication.cpp:1863
#28 0x00007fcd9cd6c6d9 in QApplication::exec() () at kernel/qapplication.cpp:2832
#29 0x0000559b9a52ca6b in main(int, char**) (argc=<optimized out>, argv=<optimized out>) at ./shell/main.cpp:235

I think Plasma's configuration was reloading due to a change in the system settings - I was playing with stuff to try to figure out a problem report, but I don't remember what I changed that caused the crash.

Ok, thanks. Unfortunately that makes it a lot less likely that we'll be able to figure out what caused this. If you can manage to reproduce the issue with the same backtrace again, and you remember what you did, feel free to re-open the bug report. Thanks for understanding!

Found a generic duplicate for it, actually.

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