Bug 460303 - wayland: activating an app on another virtual desktop doesn't open a new instance in the current virtual desktop as it does on X11
Summary: wayland: activating an app on another virtual desktop doesn't open a new inst...
Status: CONFIRMED
Alias: None
Product: kwin
Classification: Plasma
Component: wayland-generic (other bugs)
Version First Reported In: 5.25.5
Platform: Other Linux
: NOR wishlist
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-10-12 12:31 UTC by Marián Konček
Modified: 2023-07-24 12:43 UTC (History)
4 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Marián Konček 2022-10-12 12:31:15 UTC
I noticed this issue on wayland:
When i open a text file from Dolphin in a virtual desktop, it adds a new tab to a different already running instance of Kate in a different virtual desktop instead of launching a new window in the current one. This is different from X11 which would launch a new window in the current virtual desktop unless there is already a running instance in the current virtual desktop.

Note that launching Kate manually does indeed launch a new instance.
Comment 1 Vlad Zahorodnii 2022-10-12 12:38:13 UTC
kate should already activate itself when opening a new tab. As is, the problem is that virtual desktops are not exposed to clients.
Comment 2 Nate Graham 2022-10-12 19:42:03 UTC
FWIW in Plasma 5.26, you can configure what happens when you perform an action that would activate a window that's in a virtual desktop other than the current one:
- Switch to the virtual desktop with that window
- Bring that window to the current desktop
Comment 3 Marián Konček 2022-10-24 12:01:37 UTC
Yeah, but from X11, I also expect the option to have multiple instances of Kate one per virtual desktop.
Comment 4 kde.xg0ws 2023-02-17 22:48:21 UTC
I have the same problem also with Firefox and Okular. On X11 I fixed it with a script based on wmctl, which is not possible on Wayland unfortunately.