Created attachment 143734 [details] backtrace SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Log into Plasma Session 2. Hit CTRL + L to lock the screen 3. Unlock the screen OBSERVED RESULT Plasmashell crashes and has to be started with kstart5 plasmashell EXPECTED RESULT Plasmashell works SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu (available in About System) KDE Plasma Version: 5.23.3 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION nothing else to report
Thank you for the bug report! Unfortunately the backtrace is incomplete and missing debug symbols that we need to figure out exactly what's going wrong: [KCrash Handler] #4 0x00007f528c5bb28f in QQuickItemPrivate::addToDirtyList() () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #5 0x00007f528c5bfd8e in QQuickItemPrivate::dirty(QQuickItemPrivate::DirtyType) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x00007f528c5d7158 in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #7 0x00007f528c5d7183 in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #8 0x00007f528c5d7183 in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #9 0x00007f528c5d7183 in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #10 0x00007f528c5dd964 in QQuickWindowPrivate::syncSceneGraph() () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #11 0x00007f528c579cb0 in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #12 0x00007f528c57b97c in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #13 0x00007f528c57c6b7 in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #14 0x00007f528a996a71 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #15 0x00007f528a51f927 in start_thread (arg=<optimized out>) at pthread_create.c:435 #16 0x00007f528a5af9e4 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:100 Furthermore none of the unsymbolicated frames indicate that the crash happened in KDE code. I can't reproduce the issue, so unfortunately there does not seem like a way to figure out what's going on here and fix the bug. :(