https://bugs.kde.org/show_bug.cgi?id=522547
[email protected] changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #7 from [email protected] --- I have the same issue on my system. Fedora 44, Wayland session, NVIDIA 610.43.03: plasma-workspace 6.7.3-1.fc44 kwin 6.7.3-1.fc44 kf6-kwindowsystem 6.28.0-1.fc44 qt6-qtbase 6.11.1-1.fc44 Every occurrence of the protocol error equals exactly one plasmashell restart. Previous boot: 10 errors / 10 restarts. Current boot: 1 / 1. plasmashell[5267]: ext_background_effect_surface_v1#191: error 0: tried to set blur region on destroyed surface plasmashell[5267]: The Wayland connection experienced a fatal error: Protokollfehler [locale de_DE, = "Protocol error"] systemd[1684]: plasma-plasmashell.service: Main process exited, code=exited, status=255/EXCEPTION systemd[1684]: plasma-plasmashell.service: Scheduled restart job, restart counter is at 2. Note: plasmashell leaves no coredump, because it exits with a status code rather than on a signal. coredumpctl therefore only shows its kioworker children, which segfault during teardown in ~QFontconfigDatabase -> FcInitLoadOwnConfig. That second crash is not the cause. It only happens because the parent process was disconnected. But it is the only part of the sequence that leaves a coredump. The event that actually starts everything is visible only in the journal: journalctl --user -b | grep ext_background_effect Client path confirmed: plasmashell has /usr/lib64/qt6/plugins/kf6/kwindowsystem/KF6WindowSystemKWaylandPlugin.so (kf6-kwindowsystem-6.28.0-1.fc44) mapped, and that file contains the ext_background_effect bindings. Possible frequency factor: this system uses a Kvantum theme with reduce_window_opacity=18 and reduce_menu_opacity=75, i.e. a large number of translucent, short-lived surfaces. That may explain 10 restarts in a single session compared to the lower rates reported so far, and could help with reproduction. -- You are receiving this mail because: You are watching all bug changes.
