Summary: | X11 applications can't move focus between themselves on Wayland | ||
---|---|---|---|
Product: | [Plasma] kwin | Reporter: | Nate Graham <nate> |
Component: | wayland-generic | Assignee: | KWin default assignee <kwin-bugs-null> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | CC: | gobonja, kde, xaver.hugl, zorael |
Priority: | NOR | Keywords: | wayland |
Version: | git master | ||
Target Milestone: | --- | ||
Platform: | Other | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Nate Graham
2021-09-10 16:03:54 UTC
None of those examples have activation support The fact that the X11 app isn't brought forward is surprising, that potentially should work. Can we focus on that. The app always gets brought forward on X11; on Wayland it does not. There is no problem to solve on X11. Can reproduce with Discord, Telegram, Slack, 1Password; all opened in native Wayland.
> /usr/bin/discord --enable-features=UseOzonePlatform --ozone-platform=wayland
> /usr/bin/telegram-desktop -platform wayland -- %u
> /usr/bin/slack --enable-features=UseOzonePlatform,WebRTCPipeWireCapturer --ozone-platform=wayland -s %U
> /opt/1Password/1password --enable-features=UseOzonePlatform --ozone-platform=wayland %U
Not applicable to 1Password, but a very easy way to reproduce this is to try to give focus to the program in question by its tray icon, when its window already exists.
This happens even with Focus Stealing Prevention set to None. X11 works fine.
This title seems to be kind of misleading. Wayland native apps have this problem, if app is forced to run with XWayland - clicking on notification activates and focuses app. Tested on plasma 5.25. (In reply to gobonja from comment #5) > This title seems to be kind of misleading. > Wayland native apps have this problem, if app is forced to run with XWayland > - clicking on notification activates and focuses app. > Tested on plasma 5.25. Typo: tested on plasma 5.24. Works fine for me on 5.27 with Discord |