| Summary: | After unlocking screen, Plasmashell Crashes and must be restarted with kstart5 plasmashell | ||
|---|---|---|---|
| Product: | [Plasma] plasmashell | Reporter: | sparkie <lg_ninjalo> |
| Component: | generic-crash | Assignee: | Plasma Bugs List <plasma-bugs-null> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | nate |
| Priority: | NOR | ||
| Version First Reported In: | 5.23.3 | ||
| Target Milestone: | 1.0 | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: | backtrace | ||
|
Description
sparkie
2021-11-19 14:44:55 UTC
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. :( |