Bug 497792 - Inactive window on top after moving to another virtual desktop
Summary: Inactive window on top after moving to another virtual desktop
Status: CONFIRMED
Alias: None
Product: kwin
Classification: Plasma
Component: general (other bugs)
Version First Reported In: 6.2.4
Platform: Neon Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-12-22 19:19 UTC by antroids
Modified: 2025-01-03 20:31 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments
Screenshots (2.98 MB, image/gif)
2024-12-22 19:19 UTC, antroids
Details

Note You need to log in before you can comment on or make changes to this bug.
Description antroids 2024-12-22 19:19:41 UTC
Created attachment 176825 [details]
Screenshots

SUMMARY
In overview move it's possible to move not active window from one virtual desktop to another.
The window will have active state after moving and activating the desktop, but it will not be shown on top.

STEPS TO REPRODUCE
1. Create second virtual desktop.
2. Open two applications on the first virtual desktop.
3. Open one application on the second virtual desktop.
4. Enter to the overview mode on the first virtual desktop. 
5. Drag first opened application, which is not active on the first virtual desktop, to the second virtual desktop.
6. Exit overview mode and switch to the second virtual desktop.

OBSERVED RESULT
The first opened application will be active, but the third will be on top. 
It will be active in task manager and it will handle input.

EXPECTED RESULT
Top application should be active.

SOFTWARE/OS VERSIONS
Operating System: KDE neon 6.2
KDE Plasma Version: 6.2.4
KDE Frameworks Version: 6.8.0
Qt Version: 6.8.1
Kernel Version: 6.8.0-50-generic (64-bit)
Graphics Platform: Wayland
Processors: 12 × AMD Ryzen 5 PRO 4650U with Radeon Graphics
Memory: 14.9 GiB of RAM
Graphics Processor: AMD Radeon Graphics


ADDITIONAL INFORMATION
Comment 1 Nate Graham 2025-01-03 20:31:11 UTC
Can confirm, but I'm not sure if it's intentional or not. I'll leave this to the KWin devs.