482188 2024-03-01 19:11:56 +0000 Shell crashes in KWindowShadow::destroy() when unlocking the screen after idling for a while 2024-07-22 21:06:47 +0000 1 1 4 Plasma plasmashell generic-crash master Other Linux RESOLVED DUPLICATE 445893 qt6, wayland-only NOR crash 1.0 0 oded plasma-bugs-null kde nate 0 oldest_to_newest 2293592 0 oded 2024-03-01 19:11:56 +0000 SUMMARY I often have Plasma shell crash when I unlock the screen, after idling for a long time or after waking up from sleep. The Dr Konqi crash wizard can't seem to get a stack trace showing a dialog with a lot of "can't access memory" errors, but looking at the Dr Konqi core dump GUI I can get some sort of stack trace: #0 0x00007f1b5ad564c0 in KCrash::defaultCrashHandler(int) () at /lib/x86_64-linux-gnu/libKF6Crash.so.6 #1 0x00007f1b57c42520 in <signal handler called> () at /lib/x86_64-linux-gnu/libc.so.6 #2 0x00007f1b5adf1f1b in wl_proxy_marshal_flags () at /lib/x86_64-linux-gnu/libwayland-client.so.0 #3 0x00007f1b500c5e8e in xdg_activation_token_v1_set_app_id (app_id=0x55a13d366200 " \272\027[\033\177", xdg_activation_token_v1=0x55a13b5b7c50) at ./obj-x86_64-linux-gnu/src/platforms/wayland/wayland-xdg-activation-v1-client-protocol.h:363 #4 QtWayland::org_kde_kwin_shadow_manager::unset(wl_surface*) (this=<optimized out>, this=<optimized out>, surface=0x55a13d366200) at ./obj-x86_64-linux-gnu/src/platforms/wayland/qwayland-shadow.cpp:78 #5 WindowShadow::internalDestroy() (this=0x55a13d367d90) at ./src/platforms/wayland/windowshadow.cpp:195 #6 0x00007f1b5ab8851a in KWindowShadow::destroy() (this=this@entry=0x55a13d387550) at ./src/kwindowshadow.cpp:266 #7 0x00007f1b5ab8853b in KWindowShadow::~KWindowShadow() (this=0x55a13d387550, this=<optimized out>) at ./src/kwindowshadow.cpp:65 #8 0x00007f1b5ab8856d in KWindowShadow::~KWindowShadow() (this=0x55a13d387550, this=<optimized out>) at ./src/kwindowshadow.cpp:66 #9 0x00007f1b587ca0aa in QObjectPrivate::deleteChildren() (this=this@entry=0x55a13d351b80) at ./src/corelib/kernel/qobject.cpp:2207 #10 0x00007f1b587cdfb8 in QObject::~QObject() (this=<optimized out>, this=<optimized out>) at ./src/corelib/kernel/qobject.cpp:1159 #11 0x00007f1b5b126c9d in DialogShadows::~DialogShadows() (this=0x55a13d37e8e0, this=<optimized out>) at ./src/plasmaquick/dialogshadows.cpp:63 #12 0x00007f1b587ca0aa in QObjectPrivate::deleteChildren() (this=this@entry=0x55a13b56c2f0) at ./src/corelib/kernel/qobject.cpp:2207 #13 0x00007f1b587cdfb8 in QObject::~QObject() (this=<optimized out>, this=<optimized out>) at ./src/corelib/kernel/qobject.cpp:1159 #14 0x000055a13b3f5ab3 in main(int, char**) (argc=<optimized out>, argv=<optimized out>) at ./shell/main.cpp:215 SOFTWARE/OS VERSIONS Operating System: KDE neon Testing Edition KDE Plasma Version: 6.0.0 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.5.0-21-generic (64-bit) Graphics Platform: Wayland Processors: 20 × 12th Gen Intel® Core™ i7-12700H Memory: 31.0 GiB of RAM Graphics Processor: Mesa Intel® Graphics 2293686 1 nate 2024-03-01 21:37:22 +0000 Can you update Neon and try again? There were some packaging glitches with the initial 6.0 release that might account for this. 2293722 2 oded 2024-03-01 22:53:25 +0000 (In reply to Nate Graham from comment #1) > Can you update Neon and try again? There were some packaging glitches with > the initial 6.0 release that might account for this. I try to keep up to date. I'm currently running Neon testing, should I move to stable? This used to happen once daily (last time was today). I'll update if it happens again (or not). 2293905 3 oded 2024-03-02 14:30:10 +0000 I just had another similar crash, though the Dr Konqi crash dialog didn't show anything except lots of errors like this: Backtrace stopped: Cannot access memory at address 0x7ffee5a1b0f0 2294849 4 nate 2024-03-04 20:00:11 +0000 My mistake, I missed that you weren't on Neon User, which is where the glitches appeared. 2302400 5 oded 2024-03-18 07:29:44 +0000 I'm closing this bug as a dup of bug #472616, which is an earlier one I reported - even though the stack trace here is very much not like the others. I think there may be a few different crashes that are possibly not related - except in their eerie predictability: it always crashes when unlocking after idle - but as I haven't seen this specific trace again, and I get a lot more "no useful backtrace" crashes than good ones, I will just collect every traceable crash I do have in #472616. *** This bug has been marked as a duplicate of bug 472616 *** 2339331 6 nate 2024-07-22 21:06:47 +0000 *** This bug has been marked as a duplicate of bug 445893 ***