Bug 457977

Summary:	Kickoff not switching to already launched application
Product:	[Plasma] plasmashell	Reporter:	Mitja <mtjhrj>
Component:	Application Launcher (Kickoff) widget	Assignee:	Plasma Bugs List <plasma-bugs-null>
Status:	RESOLVED DOWNSTREAM
Severity:	normal	CC:	mikel5764, nate, noahadvs
Priority:	NOR
Version First Reported In:	master
Target Milestone:	1.0
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:
Attachments:	attachment-30542-0.html

Description Mitja 2022-08-17 01:16:53 UTC

SUMMARY
***
When user inadvertently launches an application that is already running (usually on another virtual desktop) nothing happens. I'm not sure if this is a bug, but I would expect plasmashell to switch to the already running application.
***


STEPS TO REPRODUCE
1. Create some virtual desktops. I usually use three virtual desktops.
2. Open an application, for example System Monitor and move it to another virtual desktop, to virtual desktop #2
3. While on virtual desktop #1 launch System Monitor.

OBSERVED RESULT
Nothing happens. Some application that are designed to run multiple instances like Kwrite open another instance.

EXPECTED RESULT
Expect KDE to switch to the already running application if designed to run only single instance.

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: KDE Neon (kernel 5.15.0-46-generic
(available in About System)
KDE Plasma Version: 5.25.4 Wayland session
KDE Frameworks Version: 5.96.0
Qt Version: 5.15.0

ADDITIONAL INFORMATION

Comment 1 Nate Graham 2022-08-17 19:57:32 UTC

This happens because the app in question does not implement the Wayland-specific activation protocol. It's still rather new and a lot of apps don't yet have support for it. They should. :) So you should report this to the developers of those apps.

Note: it's currently expected that it doesn't work for KDE apps because generic support in Qt for the activation protocol was only merged for Qt6, and KDE apps haven't been ported to use Qt 6 yet. But once they are, this should start working for them. But non-Qt 3rd-party apps will still need to manually implement the activation protocol.

Comment 2 Mitja 2022-08-17 22:31:41 UTC

Created attachment 151391 [details]
attachment-30542-0.html

Thanks for the clarification. I will wait till QT 6 is fully implemented
before reporting the issue to the authors.

Best regards.

Mitja

V sre., 17. avg. 2022 21:57 je oseba Nate Graham <bugzilla_noreply@kde.org>
napisala:

> https://bugs.kde.org/show_bug.cgi?id=457977
>
> Nate Graham <nate@kde.org> changed:
>
>            What    |Removed                     |Added
>
> ----------------------------------------------------------------------------
>              Status|REPORTED                    |RESOLVED
>          Resolution|---                         |DOWNSTREAM
>                  CC|                            |nate@kde.org
>
> --- Comment #1 from Nate Graham <nate@kde.org> ---
> This happens because the app in question does not implement the
> Wayland-specific activation protocol. It's still rather new and a lot of
> apps
> don't yet have support for it. They should. :) So you should report this
> to the
> developers of those apps.
>
> Note: it's currently expected that it doesn't work for KDE apps because
> generic
> support in Qt for the activation protocol was only merged for Qt6, and KDE
> apps
> haven't been ported to use Qt 6 yet. But once they are, this should start
> working for them. But non-Qt 3rd-party apps will still need to manually
> implement the activation protocol.
>
> --
> You are receiving this mail because:
> You reported the bug.