| Summary: | Crash on KWin windowed mode toggle to fullscreen | ||
|---|---|---|---|
| Product: | [Plasma] kwin | Reporter: | RJVB <rjvbertin> |
| Component: | wayland-generic | Assignee: | KWin default assignee <kwin-bugs-null> |
| Status: | RESOLVED UPSTREAM | ||
| Severity: | crash | Keywords: | drkonqi |
| Priority: | NOR | ||
| Version: | 5.13.3 | ||
| Target Milestone: | --- | ||
| Platform: | Compiled Sources | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
RJVB
2020-07-04 09:00:46 UTC
Crash is in Qt. Please don't try QtWayland on this hopelessly outdated Qt version. The backtrace is with Qt 5.12 which is still in LTS support AFAIK, and there are plenty of ways to crash Qt by doing stupid things that lead to dereferencing a null "this" pointer as happens here. So I wouldn't shrug off responsibility to upstream so easily. FWIW, the crash does NOT happen when I use one of Qt's own Wayland compositor examples. Testing this (with more current KWin and Qt versions) takes less than a minute when you have an X11 session running. If that doesn't reproduce the issue than this report can be closed more properly. Is there a kwin appimage I could test with myself? How is this related to KWin? It is Konsole that is crashing. Also, what versions of Wayland libraries does Ubuntu 14.04 ship? I get the same crash in any KDE application (possibly in any Qt application) that I expose to a size change of Kwin's windowed-mode window. You're right though that KWin cannot crash other apps directly, it must just send the signal do change the cursor but some other layer must act on that from within the application space. I can only presume that this is KDE functionality - in the KDE platform theme plugin maybe, in a component that we don't see in the backtrace because of the asynchronous nature of the event and signal mechanisms. It is relevant to ask however why KWin would send a cursor-change signal to its clients. I can see why itself might react to a window size change with a (temporary?) cursor change, but not why the client windows would be concerned. And FWIW, I also don't see the change in text size that I see in the Wayland/Kwin clients when I make the window fullscreen when I use "qwindow-compositor" instead. I'm not using the system wayland libraries; I've basically turned my Kubuntu 14.04 into a rolling release by updating more and more libraries myself; Wayland is at 1.18.0 . AKA Frankenstein OS... Anyway, I suggest to test with a proper distribution which ships recent versions of anything, at least Kubuntu 20.04 LTS, preferably something newer. That would have to be in a VM or off a LiveCD or similar, which might be too different to trigger the issue even with my current versions. An appimage KWin version would not be in that (potential) situation and also be a lot easier to test for me. But I take it then that doesn't exist? BTW, does anyone have an idea why an application running under a "Kwin-dowed" Wayland session would end up where the crash occurs when the session window is resized? |