Summary: | kwin_wayland crashes in KConfigWatcher::onConfigChangeNotification() on user login | ||
---|---|---|---|
Product: | [Plasma] kwin | Reporter: | Jerzy Kołosowski <kde> |
Component: | generic-crash | Assignee: | KWin default assignee <kwin-bugs-null> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | chn, kdedev, nate, snowsnooks, xaver.hugl |
Priority: | HI | Keywords: | drkonqi |
Version First Reported In: | 6.3.5 | ||
Target Milestone: | --- | ||
Platform: | Arch Linux | ||
OS: | Linux | ||
See Also: | https://bugs.kde.org/show_bug.cgi?id=443302 | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | https://crash-reports.kde.org/organizations/kde/issues/179027 |
Description
Jerzy Kołosowski
2025-05-22 09:04:31 UTC
Same issue, on NixOS 25.05, kernel 6.12, Wayland. Device is one-netbook 4 (Intel graphics). (In reply to Haonan Chen from comment #1) > Same issue, on NixOS 25.05, kernel 6.12, Wayland. Device is one-netbook 4 > (Intel graphics). Fixed by remove ~/.config/ksmserverrc Do you use Krohnkite? Did you save your ksmserverrc, can you share it please? (In reply to Vlad Zahorodnii from comment #3) > Do you use Krohnkite? Did you save your ksmserverrc, can you share it please? I do not use Kronhnkite. Here is the `ksmserverrc` that cause the problem: ``` [LegacySession: saved at previous logout] count=0 [Session: saved at previous logout] count=0 ``` The `ksmserverrc` itself seems to contain nothing special. Actually, after I delete it and relogin, plasma generate the same `ksmserverrc`. Before deleting `ksmserverrc`, I also tried to reset some other plasma settings, including delete config files (kwinrc etc.), delete all installed theme, apply default theme (breeze) in settings. Finally deleting `ksmserverrc` works. Maybe you could try to start plasma using a new user (with a clean home folder). If plasma starts correctly, you could try to reset plasma settings. Nope, I see no crash with the same ksmserverrc config file. *** Bug 505622 has been marked as a duplicate of this bug. *** There are 15 reports and 83 events since May 8, raising priority A possibly relevant merge request was started @ https://invent.kde.org/frameworks/kconfig/-/merge_requests/375 Git commit da889c31e088902723f089673f3be0a70b4560a5 by Vlad Zahorodnii. Committed on 17/06/2025 at 14:10. Pushed by vladz into branch 'master'. Guard against KConfigWatcher getting deleted while emitting configChanged() If a user of the KConfigWatcher releases its reference after receiving the configChanged() signal so the watcher gets deleted and there are more configChanged() signals to emit, then KConfigWatcher may crash. This change adds the corresponding guard. In hindsight, it'd be better if the KConfigWatcher emitted only one signal (for example by wrapping the changes variable in a helper to provide a convenient way to determine dirty groups and keys). This is a blind fix for a somewhat mildly recurring crash in kwin. SENTRY: KWIN-C3Q M +5 -0 src/core/kconfigwatcher.cpp https://invent.kde.org/frameworks/kconfig/-/commit/da889c31e088902723f089673f3be0a70b4560a5 There are no Sentry crash reports with KF 6.16, so Vlad's fix seems to work |