SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. upgrade to plasma 5.27 beta 2. open a window 3. maximize it OBSERVED RESULT only crossfade for the first time EXPECTED RESULT full maximize effect for the first time SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 5.26.9 (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION
Created attachment 155872 [details] maximize
By the way, fullscreen effect has this bug too.
Is it X11 or Wayland? Does it happen for every new window? Does it happen with "stock" plasma, i.e. without customizations?
(In reply to Vlad Zahorodnii from comment #3) > Is it X11 or Wayland? > > Does it happen for every new window? > > Does it happen with "stock" plasma, i.e. without customizations? It only happens on X11, every time. I created a new user, and it still happens.
A possibly relevant merge request was started @ https://invent.kde.org/plasma/kwin/-/merge_requests/3533
Git commit 2babccda048b61305ade9046658491cfd5311636 by Vlad Zahorodnii. Committed on 03/02/2023 at 08:33. Pushed by vladz into branch 'master'. x11: Fix maximize animation Window::maximize() used to be split in two halves: - generic Window::setMaximized() and Window::maximize() - protocol-specific Window::changeMaximize() Window::changeMaximize() used to block all geometry updates and Window::maximize() emit "maximize mode changed" signals. With that, frameGeometryChanged came always before clientMaximizedStateChanged. After merging Window::changeMaximize() and Window::maximize(), the order of the signals has been reversed because of RAII. Unblock geometry updates explicitly to preserve the old behavior. M +2 -1 src/x11window.cpp https://invent.kde.org/plasma/kwin/commit/2babccda048b61305ade9046658491cfd5311636
Git commit a6a22271683308a193c1e886b35958038a91cada by Vlad Zahorodnii. Committed on 03/02/2023 at 14:08. Pushed by vladz into branch 'cherry-pick-2babccda'. x11: Fix maximize animation Window::maximize() used to be split in two halves: - generic Window::setMaximized() and Window::maximize() - protocol-specific Window::changeMaximize() Window::changeMaximize() used to block all geometry updates and Window::maximize() emit "maximize mode changed" signals. With that, frameGeometryChanged came always before clientMaximizedStateChanged. After merging Window::changeMaximize() and Window::maximize(), the order of the signals has been reversed because of RAII. Unblock geometry updates explicitly to preserve the old behavior. (cherry picked from commit 2babccda048b61305ade9046658491cfd5311636) M +2 -1 src/x11window.cpp https://invent.kde.org/plasma/kwin/commit/a6a22271683308a193c1e886b35958038a91cada
also, the same issue for fullscreen effect.