SUMMARY If I try to restart Wayland session immediately after logout from it, login fails and coredumpctl command lists kded5 coredump. STEPS TO REPRODUCE 1. start Wayland session 2. logout 3. immediately try to login to Wayland session again OBSERVED RESULT Wayland session is not started and kded5 coredump is generated. This problem does not occur if I wait ~30 seconds before trying to log in again. EXPECTED RESULT login to Wayland session without any coredump SOFTWARE/OS VERSIONS Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.20.80 KDE Frameworks Version: 5.78.0 Qt Version: 5.15.2 Thread 1 (Thread 0x7f27a4860840 (LWP 11034)): #0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 #1 0x00007f27a75b0859 in __GI_abort () at abort.c:79 #2 0x00007f27a79f0be7 in qt_message_fatal (context=..., message=<synthetic pointer>...) at global/qlogging.cpp:1914 #3 QMessageLogger::fatal (this=this@entry=0x7fffd67f5320, msg=msg@entry=0x7f27a8665825 "%s") at global/qlogging.cpp:893 #4 0x00007f27a81aea63 in init_platform (argv=<optimized out>, argc=@0x7fffd67f555c: 1, platformThemeName=..., platformPluginPath=..., pluginNamesWithArguments=...) at ../../include/QtCore/../../src/corelib/tools/qarraydata.h:208 #5 QGuiApplicationPrivate::createPlatformIntegration (this=0x55d6d8923350) at kernel/qguiapplication.cpp:1481 #6 0x00007f27a81aeef8 in QGuiApplicationPrivate::createEventDispatcher (this=<optimized out>) at kernel/qguiapplication.cpp:1498 #7 0x00007f27a7c18176 in QCoreApplicationPrivate::init (this=this@entry=0x55d6d8923350) at kernel/qcoreapplication.cpp:852 #8 0x00007f27a81b2013 in QGuiApplicationPrivate::init (this=this@entry=0x55d6d8923350) at kernel/qguiapplication.cpp:1527 #9 0x00007f27a898e11d in QApplicationPrivate::init (this=0x55d6d8923350) at kernel/qapplication.cpp:513 #10 0x000055d6d7e1efa2 in main (argc=<optimized out>, argv=0x7fffd67f5758) at ./src/kded.cpp:732
See also Bug 430740.
*** This bug has been marked as a duplicate of bug 419496 ***
*** This bug has been marked as a duplicate of bug 419492 ***