| Summary: | kwin crashes every now and then when launching particular applications | ||
|---|---|---|---|
| Product: | [Plasma] kwin | Reporter: | coolio128 |
| Component: | platform-drm | Assignee: | KWin default assignee <kwin-bugs-null> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | crash | CC: | kdedev, xaver.hugl |
| Priority: | NOR | ||
| Version First Reported In: | 6.4.3 | ||
| Target Milestone: | --- | ||
| Platform: | Bazzite | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
coolio128
2025-08-08 12:17:45 UTC
Can you check kwin's logs when the hard freeze occurs? You might need to switch to a TTY. journalctl --boot --user-unit plasma-kwin_wayland > ~/log.txt Also, is there any chance that you could retrieve kwin's backtrace when the hard freeze occurs? You would need to ssh from another computer and attach a debugger to kwin process, e.g. sudo gdb -p $(pidof kwin_wayland) then type bt and paste the output here. Thanks. Thank you for the reply. I tried switching to TTY during the hard freeze, but I was not able to - it was a complete hang. The keyboard was not responsive, toggling "Num Lock" on and off did not do anything. I'll try your second suggestion later and let you know how it went. ๐๐งน โ ๏ธ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME. For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging. 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. Closing as RESOLVED WORKSFORME. |