SUMMARY When running any electron app with native wayland backend (requires `--enable-features=UseOzonePlatform --ozone-platform=wayland` command line flags) they will stop showing new frames when entering fullscreen until you focus another window with a shortcut STEPS TO REPRODUCE 1. Launch electron running natively on wayland, if you have a system wide electron can just launch it on any URL, like `electron32 --enable-features=UseOzonePlatform --ozone-platform=wayland https://kde.org` on arch linux while having `electron32` package 2. Enter fullscreen with a shortcut like F11 3. Try to interact with the window OBSERVED RESULT The window stays in the same frame until you focus another window, after that it works normally on fullscreen (like alt tabbing, opening the application launcher or the overview, anything that unfocus and focus the window again) EXPECTED RESULT The window should not stay in the same frame SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.2.91 KDE Frameworks Version: 6.10.0 Qt Version: 6.9.0 Kernel Version: 6.12.10-zen1-1-zen (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 4600G with Radeon Graphics Memory: 16.0 GB of RAM Graphics Processor: AMD Radeon Graphics ADDITIONAL INFORMATION I could also reproduce it on 6.2.5 before i updated to the 6.3 beta
Oh also i just realized it could be related to direct scanout after i sent the bug report and it is! setting `KWIN_DRM_NO_DIRECT_SCANOUT=1` fixes the issue
Please attach the output of > journalctl --user-unit plasma-kwin_wayland --boot 0 after triggering the issue.
i don't think there's anything useful but sure short log because i did a fresh boot to remove the environment variable that disables direct scanout i triggered it multiple times before copying the logs and nothing showed up Feb 05 03:23:25 archlinux systemd[893]: Starting KDE Window Manager... Feb 05 03:23:25 archlinux systemd[893]: Started KDE Window Manager. Feb 05 03:23:25 archlinux kwin_wayland[980]: No backend specified, automatically choosing drm Feb 05 03:23:27 archlinux kwin_wayland_wrapper[1076]: The XKEYBOARD keymap compiler (xkbcomp) reports: Feb 05 03:23:27 archlinux kwin_wayland_wrapper[1076]: > Warning: Unsupported maximum keycode 708, clipping. Feb 05 03:23:27 archlinux kwin_wayland_wrapper[1076]: > X11 cannot support keycodes above 255. Feb 05 03:23:27 archlinux kwin_wayland_wrapper[1076]: > Warning: Could not resolve keysym XF86KbdInputAssistPrevgrou Feb 05 03:23:27 archlinux kwin_wayland_wrapper[1076]: > Warning: Could not resolve keysym XF86KbdInputAssistNextgrou Feb 05 03:23:27 archlinux kwin_wayland_wrapper[1076]: Errors from xkbcomp are not fatal to the X server Feb 05 03:23:27 archlinux kcminit[1078]: Initializing "/usr/lib/qt6/plugins/plasma/kcms/systemsettings/kcm_fonts.so" Feb 05 03:23:27 archlinux kcminit[1078]: Initializing "/usr/lib/qt6/plugins/plasma/kcms/systemsettings/kcm_style.so" Feb 05 03:23:42 archlinux kwin_wayland[980]: kwin_core: Cannot grant a token to KWin::ClientConnection(0x5fc378f021c0) Feb 05 03:23:42 archlinux kwin_wayland[980]: kwin_core: Cannot grant a token to KWin::ClientConnection(0x5fc378f021c0)
Created attachment 177982 [details] The bug happening with multi monitor so here's it happening with 2 monitors, the konsole window on the right screen is running > journalctl --user-unit plasma-kwin_wayland -e --follow and no new logs show up when it happens, the GL_INVALID_OPERATION warns seem to happen completely unrelated and also happen when direct scanout is off with the env var it apparently fixes itself after direct scanout gets disabled in any way by a single frame like moving a window to that monitor like how i opened the electron dev tools while the window was frozen and it only showed up after direct scanout got disabled by moving another window on top
🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME. For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging. Thank you for helping us make KDE software even better for everyone!
Please get a drm debug output for when this freeze happens; see https://invent.kde.org/plasma/kwin/-/wikis/Debugging/Debugging-DRM-issues for how to do that.
🐛🧹 This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME.