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. enter gridview, 2. drag a window from desktop 1 on screen A to desktop 2 on screen B. OBSERVED RESULT In the gridview effects it will show up at desktop 2 on screen A, while in reality it has been moved to desktop 2 on screen B. EXPECTED RESULT In the gridview effects it should show up at desktop 2 on screen B, SOFTWARE/OS VERSIONS Git master build of kwin. Operating System: Arch Linux KDE Plasma Version: 6.0.80 KDE Frameworks Version: 6.0.0 Qt Version: 6.7.0 Kernel Version: 6.7.6-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 20 × 13th Gen Intel® Core™ i9-13900H Memory: 15.2 GiB of RAM Graphics Processor: Mesa Intel® Graphics Manufacturer: ASUSTeK COMPUTER INC. Product Name: ROG Zephyrus G16 GU603VV_GU603VV System Version: 1.0 ADDITIONAL INFORMATION Yes, this happens despite many recent fixes. I use 9 virtual desktops arranged in a 3x3 grid. Now this only happens with one of my external monitors. The output of kscreen-doctor -o: Output: 1 eDP-2 enabled connected priority 1 Panel Modes: 0:2560x1600@240! 1:2560x1600@60* 2:1600x1200@60 3:1280x1024@60 4:1024x768@60 5:2560x1600@60 6:1920x1200@60 7:1280x800@60 8:2560x1440@60 9:1920x1080@60 10:1600x900@60 11:1368x768@60 12:1280x720@60 Geometry: 2259,42 1897x1186 Scale: 1.35 Rotation: 1 Overscan: 0 Vrr: Automatic RgbRange: Automatic HDR: incapable Wide Color Gamut: incapable ICC profile: none Output: 2 HDMI-A-1 enabled connected priority 2 HDMI Modes: 0:3840x2160@60*! 1:3840x2160@60 2:3840x2160@50 3:3840x2160@30 4:3840x2160@30 5:3840x2160@25 6:3840x2160@24 7:1920x2160@60 8:2560x1440@60 9:2048x1280@60 10:1920x1080@60 11:1920x1080@60 12:1920x1080@50 13:1920x1080@24 14:1600x1200@60 15:1280x1024@75 16:1280x1024@60 17:1280x800@60 18:1152x864@75 19:1280x720@60 20:1280x720@50 21:1024x768@75 22:1024x768@60 23:800x600@75 24:800x600@60 25:720x576@50 26:720x480@60 27:640x480@75 28:640x480@60 29:640x480@60 Geometry: 0,0 2259x1271 Scale: 1.7 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown HDR: incapable Wide Color Gamut: incapable ICC profile: none
Cannot reproduce the issue with current git master. I set my system up like yours: a 3x3 grid of desktops and two screens. My external screen is even connected via HDMI, like yours. Then I enter grid view by doing a four-finger downward swipe on my touchpad. In this view, I drag a window from desktop 1 on screen A to desktop 2 on screen B. It does what I expect.
(In reply to Nate Graham from comment #1) > Cannot reproduce the issue with current git master. I set my system up like > yours: a 3x3 grid of desktops and two screens. My external screen is even > connected via HDMI, like yours. Then I enter grid view by doing a > four-finger downward swipe on my touchpad. In this view, I drag a window > from desktop 1 on screen A to desktop 2 on screen B. It does what I expect. This only happens with my 4K external monitor, and not with my other 1920x1080 external monitor. It reproduces most consistently when I drag a window between desktop 4 and desktop 5 across screens (or between 5 and 8). It happens both when I use gesture and shortcut to trigger.
Update: this does not only occur with my 4k monitor. It happens on both monitors I have. Right now my suspicion is that it only happens with maximized wayland windows (e.g., maximized firefox with wayland backend, and maximized dolphin). It does not happen when these are not maximized, and it does not seem to happen with xwayland windows (like slack).
When you say gridview, do you mean the overview effect? If so, this is can be considered a duplicate of 481331 which is fixed next release
(In reply to David Edmundson from comment #4) > When you say gridview, do you mean the overview effect? > > If so, this is can be considered a duplicate of 481331 which is fixed next > release Desktop grid from overview. I am running a source build of kwin from yesterday (bc62e7e094), which includes the fixes for 481331, and I can still reproduce this.
Same.
*** Bug 482923 has been marked as a duplicate of this bug. ***
Seems fixed for me on git master.