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 偶然出现的故障，无法重现 OBSERVED RESULT 整个桌面环境有明显卡顿，之后Plasma Shell崩溃。 等待Shell自动重启后触摸板的单击、滚动功能不起作用，Super键不能唤出主菜单 EXPECTED RESULT Plasma Shell重启后应该能正常运行 SOFTWARE/OS VERSIONS Linux/KDE Plasma: Debian testing bookworm (available in About System) KDE Plasma Version:5.24.4 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION
Can you provide crash backtrace?
(In reply to Fushan Wen from comment #1) > Can you provide crash backtrace? Maybe I cannot. This crash occurs quite rarely.
You can use `coredumpctl` to see if there is any crash report related to plasmashell. Without backtrace it's very hard to fix the bug.
Created attachment 149102 [details] The coredumpctl result. It has crashed again and I managed to find it.
(In reply to 2637827727 from comment #4) > Created attachment 149102 [details] > The coredumpctl result. > > It has crashed again and I managed to find it. You can run `coredumpctl gdb 9506`, and type `bt` to get all backtrace and then post here.
#0 0x00007f12118d88a1 in raise () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x00007f1213d98bf1 in KCrash::defaultCrashHandler(int) () from /lib/x86_64-linux-gnu/libKF5Crash.so.5 #2 <signal handler called> #3 0x00007f12118d88a1 in raise () from /lib/x86_64-linux-gnu/libc.so.6 #4 0x00007f12118c2546 in abort () from /lib/x86_64-linux-gnu/libc.so.6 #5 0x00007f1211919eb8 in ?? () from /lib/x86_64-linux-gnu/libc.so.6 #6 0x00007f121192191a in ?? () from /lib/x86_64-linux-gnu/libc.so.6 #7 0x00007f1211922cf4 in ?? () from /lib/x86_64-linux-gnu/libc.so.6 #8 0x00007f12119269b4 in free () from /lib/x86_64-linux-gnu/libc.so.6 #9 0x00007f121331c90b in QV4::IdentifierTable::asPropertyKeyImpl(QV4::Heap::String const*) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #10 0x00007f1213301682 in QV4::ExecutionEngine::newIdentifier(QString const&) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #11 0x00007f121330c1b0 in QV4::ExecutionEngine::fromVariant(QVariant const&) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #12 0x00007f121330c954 in QV4::ExecutionEngine::metaTypeToJS(int, void const*) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #13 0x00007f121330c1db in QV4::ExecutionEngine::fromVariant(QVariant const&) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #14 0x00007f121338aab2 in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #15 0x00007f121338b65f in QV4::QObjectWrapper::getQmlProperty(QQmlContextData*, QV4::String*, QV4::QObjectWrapper::RevisionMode, bool*, bool) const () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #16 0x00007f121338b7e3 in QV4::QObjectWrapper::virtualGet(QV4::Managed const*, QV4::PropertyKey, QV4::Value const*, bool*) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #17 0x00007f12133c36bb in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #18 0x00007f11b40732b0 in ?? () #19 0x0000000000000000 in ?? () Due to Bleachbit, some useful caches may have been deleted.Sorry for that.
It can be caused by some kinds of memory leaks. Do you have any 3rd applets enabled?
I use dbus-broker. Besides, my computer underwent several incorrect shutdowns, which I think may cause data loss.Maybe it has sth to do with the problem?
However, I haven't used any third party applet on my desktop. I just don't like doing so.
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!