SUMMARY Hi there, I searched for duplicates but couldn't find one, so I'm sorry if this has already been reported. On my Framework 13 I have configured the "meta" key to not open the kickoff menu, but to show the window overview effect. However, during the last few weeks, I sometimes (once a week) see a crash of kwin when I return from this overview effect (e.g. after searching for a program that I want to open and clicking enter, but I also saw it when I accidentally opened it using the meta key and closed it using the meta key again). Afterwards I'm thrown back to the login screen and have to login again with my session gone. I don't know what causes it to crash one time but not the other. STEPS TO REPRODUCE 1. ??? 2. Open window overview effect (default shortcut: Meta + w) 3. ??? 4. Close overview effect 5. ??? 6. See crash OBSERVED RESULT kwin completely crashes and I have to login again EXPECTED RESULT I just return from the overview effect SOFTWARE/OS VERSIONS Windows: macOS: (available in the Info Center app, or by running `kinfo` in a terminal window) Linux/KDE Plasma: KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION Should any additional information be required, please let me know :)
Sorry, forgot to enter the system info: Yuga Linux uses the openSUSE Tumbleweed packages Operating System: Yuga Linux 20260128 KDE Plasma Version: 6.5.5 KDE Frameworks Version: 6.22.0 Qt Version: 6.10.1 Kernel Version: 6.16.4-1-yuga (64-bit) <-- based on openSUSE Tumbleweed kernel Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 7840U w/ Radeon 780M Graphics Memory: 32 GiB of RAM (30.7 GiB usable) Graphics Processor: AMD Radeon 780M Graphics Manufacturer: Framework Product Name: Laptop 13 (AMD Ryzen 7040Series) System Version: A7
Unfortunately for crashes we cannot do much without either being to reproduce (we can't) or a backtrace. Please check `coredumpctl gdb kwin_wayland` and see if that has any output.
(In reply to David Edmundson from comment #2) > Unfortunately for crashes we cannot do much without either being to > reproduce (we can't) or a backtrace. > > Please check `coredumpctl gdb kwin_wayland` and see if that has any output. Understandable, unfortunately coredumpctl doesn't show anything. Is there any way for me to make sure that I capture logs the next time it happens or do I need to hope that it appears one day? :D
`journalctl --user -u plasma-kwin_wayland -r` after it happens should suffice. Failing that hopefully our automatic crash reporter should have caught something from someone else.