https://bugs.kde.org/show_bug.cgi?id=512403

            Bug ID: 512403
           Summary: kwin_wayland SIGSEGV in QObjectPrivate::deleteChildren
                    (Qt6) randomly when closing windows
    Classification: Plasma
           Product: kwin
      Version First unspecified
       Reported In:
          Platform: Arch Linux
                OS: Linux
            Status: REPORTED
          Severity: crash
          Priority: NOR
         Component: wayland-generic
          Assignee: [email protected]
          Reporter: [email protected]
  Target Milestone: ---

Created attachment 187005
  --> https://bugs.kde.org/attachment.cgi?id=187005&action=edit
logs captured with coredumpctl

SUMMARY

I am experiencing random kwin_wayland crashes (Signal 11) specifically when
closing windows. It does not happen every time; it appears to be random (I can
go days or even weeks without issues), but the trigger is always the action of
closing an application window.

I captured a coredump, and the stack trace points towards an issue with Qt6
object destruction (QObjectPrivate::deleteChildren and QQuickItem).

STEPS TO REPRODUCE

1. Login to a Plasma (Wayland) session.
2. Open application windows normally.
3. Close a window.

OBSERVED RESULT
The compositor (kwin_wayland) crashes with a Segmentation Fault (Signal 11),
terminating the session immediately

EXPECTED RESULT
The window should close normally without crashing the compositor.

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 6.5.3
KDE Frameworks Version: 6.20.0
Qt Version: 6.10.0
Kernel Version: 6.17.8-zen1-1-zen (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i5-1035G1 CPU @ 1.00GHz
Memory: 16 GiB of RAM (15.2 GiB usable)
Graphics Processor: Intel® UHD Graphics
Manufacturer: HP
Product Name: HP 240 G7 Notebook PC

ADDITIONAL INFORMATION

I initially suspected a custom window decoration (Aurorae) or a hardware issue
(RAM), but I reverted my system to the stock Breeze theme and removed
third-party widgets. The crash persists with the exact same stack trace on a
standard configuration.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to