SUMMARY I am experiencing a very peculiar, but annoying crash when some particular steps are executed. Because I use the clock widget at bottom-right corner of the screen, I end up triggering the crash inadvertently every now and then. Also, when the crash happens, after I kill kwin-wayland and login again, some processes eat up 100% of my CPU. It is generally some akonadi processes and/or Yakuake. Effectively, I have to reboot after the crash happens. STEPS TO REPRODUCE 1. Point to clock widget in a panel 2. Wait for the hovering box to appear 3. Move mouse out of the panel OBSERVED RESULT kwin crashes EXPECTED RESULT No crash SOFTWARE/OS VERSIONS Operating System: Kubuntu 21.04 KDE Plasma Version: 5.21.4 KDE Frameworks Version: 5.80.0 Qt Version: 5.15.2 Kernel Version: 5.11.0-17-generic OS Type: 64-bit Graphics Platform: Wayland Processors: 8 × Intel® Core™ i5-1035G1 CPU @ 1.00GHz Memory: 15.4 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics ADDITIONAL INFORMATION Only happens using plasma Wayland. Also, I only observed this bug after activating PIM events plugin in the clock widget settings.
If we have a crash we need a backtrace. See https://community.kde.org/KWin/Debugging
*** Bug 437784 has been marked as a duplicate of this bug. ***
The duplicate bug was reported just 3 minutes after this one exhibiting similar issues. It has a short video demo of the bug and soon hopefully journalctl logs.
Created attachment 138858 [details] journalctl-1-bug-437784 journalctl log from first time issue from bug 437784
Created attachment 138859 [details] journalctl-2-bug-437784 journalctl log from second time issue from bug 437784
journalctl logs are not backtraces. Please read these: https://community.kde.org/KWin/Debugging https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl
Created attachment 138862 [details] dump Okay, so i attached the debugger by the listed command and then found the first process named kwin_wayland and send SIGSEGV to it. I'm attaching the result and i'm hoping it's what i should've done.
Created attachment 138863 [details] kwin_wayland.gdb There's some other file lurking in my /home directory...
backtrace was provided. I can confirm this problem on neon unstable.
(In reply to Patrick Silva from comment #9) > backtrace was provided. > > I can confirm this problem on neon unstable. I cannot reproduce it. Did you enable PIM events plugin?
(In reply to Vlad Zahorodnii from comment #10) > (In reply to Patrick Silva from comment #9) > > backtrace was provided. > > > > I can confirm this problem on neon unstable. > > I cannot reproduce it. Did you enable PIM events plugin? Not sure what PIM is, but i have checked "Astronomical Events", "Holidays", "Lunar phases" and "Astronomical seasons". Did i produce the backtrace incorrectly, please see the steps i took above.
Sorry, I confused this bug with bug 422072(In reply to Vlad Zahorodnii from comment #10) > (In reply to Patrick Silva from comment #9) > > backtrace was provided. > > > > I can confirm this problem on neon unstable. > > I cannot reproduce it. Did you enable PIM events plugin? Sorry, I think I have confused this bug with bug 422072
Crashing thread: Thread 1 (LWP 1671 "kwin_wayland"): #0 0x00007efeda7b432e in __ppoll (fds=fds@entry=0x55eefae90c98, nfds=nfds@entry=9, timeout=<optimised out>, timeout@entry=0x7ffccec62bb0, sigmask=sigmask@entry=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:48 #1 0x00007efedaf9e3e0 in ppoll (__ss=<optimised out>, __timeout=<optimised out>, __nfds=<optimised out>, __fds=<optimised out>) at /usr/include/x86_64-linux-gnu/bits/poll2.h:79 #2 qt_ppoll (timeout_ts=0x7ffccec62bb0, nfds=9, fds=0x55eefae90c98) at kernel/qcore_unix.cpp:132 #3 qt_ppoll (timeout_ts=0x7ffccec62bb0, nfds=9, fds=0x55eefae90c98) at kernel/qcore_unix.cpp:129 #4 qt_safe_poll (fds=0x55eefae90c98, nfds=9, timeout_ts=timeout_ts@entry=0x7ffccec62c20) at kernel/qcore_unix.cpp:164 #5 0x00007efedaf9fbd3 in QEventDispatcherUNIX::processEvents (this=<optimised out>, flags=...) at kernel/qeventdispatcher_unix.cpp:502 #6 0x000055eef9795681 in ?? () #7 0x00007efedaf47b8b in QEventLoop::exec (this=this@entry=0x7ffccec62d50, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69 #8 0x00007efedaf50024 in QCoreApplication::exec () at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #9 0x000055eef9741235 in ?? () #10 0x00007efeda6d0565 in __libc_start_main (main=0x55eef973f1a0, argc=5, argv=0x7ffccec63268, init=<optimised out>, fini=<optimised out>, rtld_fini=<optimised out>, stack_end=0x7ffccec63258) at ../csu/libc-start.c:332 #11 0x000055eef9741afe in ?? () Unfortunately the backtrace is incomplete. :( It needs more debug symbols! See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Ubuntu-based_distros_.28Ubuntu.2C_Kubuntu.2C_KDE_Neon.2C_Linux_Mint.29
How can i find out the symbols for 0x000055eef9741235 in ?? () There are no files. Usually Dr Konqi tells me the missing files and i find what packages these are and install the dbgsyms. Now there are no files listed for the ??() functions. Also my gut makes me feel obliged to reiterate that this is a crash artificially made by me via manual SIGSEGV to kwin_wayland. I just found out in a different unrelated bug here that you could capture the state of the process that way.
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!