https://bugs.kde.org/show_bug.cgi?id=512707
John Schroeder <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #187643|0 |1 is obsolete| | --- Comment #12 from John Schroeder <[email protected]> --- Created attachment 187694 --> https://bugs.kde.org/attachment.cgi?id=187694&action=edit kwin backtrace Thanks for the help! I was able to run "drkonqi-coredump-gui" and generate a (hopefully) "useful" backtrace. Let me know if there is still more I can do. I can reproduce this consistently so I don't have a problem creating a new log or backtrace. Some details on the crash: 1. Only happens when I use GPU passthrough (noted in the description). 2. Only happens when opening some apps (non-flatpak?). Konsole, Kate, Dolphin, System Settings, etc. crash. Firefox does not. 3. Does not happen immediately after login (as noted in the ticket). kwin will only crash immediately if I had an app (e.g. Dolphin) open from a previous session and the app re-opens due to it being in the saved session. Note: Here are some details that came up for me. (Probably not useful to anyone else.) 1. I lost my "golden" 202511180408 image because I had automatic updates checked. However, that image wasn't useful for getting crash info. 2. I was able to boot into newer images (202512140922 and 202512150254) without GPU passthrough and run drkonqi-coredump-gui that way. 3. I had to increase my VM RAM size from 4GB to 8GB in order to not have the error message "KDE This backtrace is very limited because there was not enough memory available to generate a full backtrace. You can close some applications and try again." -- You are receiving this mail because: You are watching all bug changes.
