Summary: | System Settings crashed in QtWayland::wl_registry::handle_global() for org_kde_kwin_blur_manager on Wayland when changing global theme | ||
---|---|---|---|
Product: | [Plasma] kwin | Reporter: | Patrick Silva <bugseforuns> |
Component: | wayland-generic | Assignee: | KWin default assignee <kwin-bugs-null> |
Status: | RESOLVED WORKSFORME | ||
Severity: | crash | CC: | alex765, magiblot, nate |
Priority: | NOR | Keywords: | drkonqi |
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Neon | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | systemsettings with WAYLAND_DEBUG=1 |
Description
Patrick Silva
2021-03-27 10:24:19 UTC
Almost the same backtrace as in Bug 422424, but it's System Settings crashing, now KWin. In that case, shouldn't this bug be moved to the systemsettings5 product? Also I'm unable to reproduce this on a fresh Neon Unstable VM... The bug isn't in System Settings itself, but rather something deep in the compositor. This should be fixed by https://invent.kde.org/plasma/kwayland-server/-/merge_requests/156. Not sure that Neon was shipping kwin with that MR included. Can you also please run systemsettings with WAYLAND_DEBUG=1? Created attachment 137264 [details]
systemsettings with WAYLAND_DEBUG=1
(In reply to Patrick Silva from comment #6) > Created attachment 137264 [details] > systemsettings with WAYLAND_DEBUG=1 I don't see anything suspicious in the log. You ran systemsettings with WAYLAND_DEBUG=1 and made it crash by changing the global theme, right? No. This crash is not reproducible, it happened just once. *** Bug 433036 has been marked as a duplicate of this bug. *** (In reply to Patrick Silva from comment #8) > No. This crash is not reproducible, it happened just once. It's quite possible that neon didn't ship the right kwaylandserver at that time. Let's mark it RESOLVED WORKSFORME. If this issue happens again in git master, please reopen this bug report. |