| Summary: | KWin crashed in KWin::Item::sortedChildItems while interacting with QtCreator | ||
|---|---|---|---|
| Product: | [Plasma] kwin | Reporter: | Daniel Schulte <trilader+kdebugs> |
| Component: | general | Assignee: | KWin default assignee <kwin-bugs-null> |
| Status: | REOPENED --- | ||
| Severity: | crash | CC: | kde, kdedev |
| Priority: | NOR | Keywords: | drkonqi |
| Version First Reported In: | 6.5.5 | ||
| Target Milestone: | --- | ||
| Platform: | Arch Linux | ||
| OS: | Linux | ||
| See Also: | https://bugs.kde.org/show_bug.cgi?id=515123 | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: | New crash information added by DrKonqi | ||
|
Description
Daniel Schulte
2026-01-27 15:17:32 UTC
Created attachment 188949 [details]
New crash information added by DrKonqi
DrKonqi auto-attaching complete backtrace.
I've had a log at the system journal. It shows that qtcreator crashed just before kwin_wayland did: ``` Jan 27 16:10:25 eldingar kernel: qtcreator[30091]: segfault at 100000014 ip 00007f1756b2905f sp 00007fffe3b5f468 error 4 in libQt6Gui.so.6.10.1[12905f,7f1756ae4000+6c8000] likely on CPU 8 (core 8> Jan 27 16:10:25 eldingar kernel: Code: 18 f3 0f 7e 50 04 66 0f 14 c0 f3 0f e6 ca 66 0f 5e c8 66 0f 28 c1 66 0f 15 c9 c3 f3 0f 1e fa 48 8b 57 10 31 c0 48 85 d2 74 04 <48> 8b 42 10 c3 90 66 66 2e 0> Jan 27 16:10:25 eldingar systemd-coredump[311081]: Process 30091 (qtcreator) of user 1000 terminated abnormally with signal 11/SEGV, processing... Jan 27 16:10:25 eldingar systemd[1]: Started Process Core Dump (PID 311081/UID 0). Jan 27 16:10:25 eldingar systemd[1]: Started Pass systemd-coredump journal entries to relevant user for potential DrKonqi handling. Jan 27 16:10:28 eldingar kwin_wayland_wrapper[135076]: KCrash: Application 'kwin_wayland' crashing... crashRecursionCounter = 2 Jan 27 16:10:28 eldingar systemd-coredump[311126]: Process 135076 (kwin_wayland) of user 1000 terminated abnormally with signal 11/SEGV, processing... Jan 27 16:10:28 eldingar systemd[1]: Started Process Core Dump (PID 311126/UID 0). Jan 27 16:10:28 eldingar systemd[1]: Started Pass systemd-coredump journal entries to relevant user for potential DrKonqi handling. ``` *** This bug has been marked as a duplicate of bug 510781 *** I'm unsure if this really is a duplicate of 510781 (which itself is marked as a duplicate of 509690) as both of them are marked as resolved since 2025-10-14 and this has happened for me again. If this really is a duplicate maybe one of them should also be re-opened? I had a look at those other two bugs, and their backtraces look subtly different. Also, they were supposed to be fixed with 6.5.0 and you're running 6.5.5. Let's keep those other bugs closed for now, and use this one for this backtrace. I also took a look at bug 515123 and while the backtrace also shares some similarities with this one, they are sufficiently different for me not to mark them as duplicates. |