Bug 500256

Summary: Kwin crashes when trying to create a New Folder
Product: [Plasma] kwin Reporter: ogamal523
Component: wayland-genericAssignee: KWin default assignee <kwin-bugs-null>
Status: RESOLVED NOT A BUG    
Severity: crash CC: kde, ogamal523
Priority: NOR    
Version First Reported In: 6.3.0   
Target Milestone: ---   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: Systemd crash log
Video demeonstrating the bug and how to reproduce it

Description ogamal523 2025-02-17 13:04:31 UTC
Created attachment 178481 [details]
Systemd crash log

SUMMARY
Kwin crashes when trying to create a New Folder or open specific apps on empty desktop (no windows open) if I have a window open even if it's not fullscreen it doesn't crash.
This crash happens only on Wayland, X11 works fine.

STEPS TO REPRODUCE
1. Try to create a new folder or text file on an empty desktop with no windows, try opening flatsweep or gimp on an empty desktop with no windows

OBSERVED RESULT
Kwin crashes

EXPECTED RESULT
No crash

SOFTWARE/OS VERSIONS
KDE Plasma Version: 6.3.0
KDE Frameworks Version: 6.11.0
Qt Version: 6.8.2
Kernel Version: 6.13.2-zen1-1-zen (64-bit)
Graphics Platform: Wayland

ADDITIONAL INFORMATION
My laptop has an integrated Intel GPU and a dedicated Nvidia GPU if that information helps
Comment 1 ogamal523 2025-02-17 16:28:08 UTC
Created attachment 178486 [details]
Video demeonstrating the bug and how to reproduce it

Sorry for the horrible video quality had to compress it for the file size limit
Comment 2 David Redondo 2025-02-18 10:10:39 UTC
Thank you for the bug report! Unfortunately I can't reproduce the crash myself on current git master, and the backtrace is incomplete and missing debug symbols for the following lines that we need to figure out exactly what's going wrong:
Could you please install debug symbols and attach a new symbolicated backtrace generated by using coredumpctl gdb in a terminal window? See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl for details about how to do this.
Thanks again!
Then mark it as NEEDSINFO BACKTRACE
Comment 3 ogamal523 2025-02-18 18:20:52 UTC
(In reply to David Redondo from comment #2)
> debug symbols for the following lines that we need to figure out exactly
> what's going wrong:
> Could you please install debug symbols and attach a new symbolicated
> backtrace generated by using coredumpctl gdb in a terminal window? See

Thank you for telling me about this debugging method, I figured out the issue and fixed it it was because of a Window Rule I made related to window sizing