Bug 520624

Summary:	Wrong startup app id when "run in terminal" is checked
Product:	[Frameworks and Libraries] frameworks-kio	Reporter:	Kai Uwe Broulik <kde>
Component:	general	Assignee:	KIO Bugs <kio-bugs-null>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	akselmo, kdedev, kdelibs-bugs-null, nicolas.fella
Priority:	NOR
Version First Reported In:	6.24.0
Target Milestone:	---
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Kai Uwe Broulik 2026-05-25 06:33:27 UTC

DESCRIPTION
When a desktop file specifies the service be run in a terminal, DesktopExecParser rewrites the exec line to launch Konsole (or whatever TerminalApplication) instead of the actual program. However, the startup app ID is still the original service, so there is a mismatch and the bouncing cursor does not go away when Konsole launched.

STEPS TO REPRODUCE
1. Add a service using kmenuedit and set "Run in terminal" (or find one which does)
2. Launch it

OBSERVED RESULT
The bouncing cursor stays until it times out

EXPECTED RESULT
The bouncing cursor goes away as soon as the terminal app has launched

SOFTWARE/OS VERSIONS
Operating System (available in the Info Center app, or by running `kinfo` in a terminal window):
KDE Plasma Version: 6.7 Beta
KDE Frameworks Version: 6.24
Qt Version: 6.11.1

ADDITIONAL INFORMATION
The app still seems to get a proper xdg activation token (at least on low focus stealing prevention) so the window does come to the front properly at least

Comment 1 Akseli Lahtinen 2026-05-25 12:39:58 UTC

Can confirm. This might be related to the --desktopfile flag for konsole not working. --desktopfile comes from kcoreaddons and kaboutdata

Operating System: KDE Linux 2026-05-25
KDE Plasma Version: 6.7.80
KDE Frameworks Version: 6.27.0
Qt Version: 6.11.1
Kernel Version: 7.0.9-arch2-1 (64-bit)
Graphics Platform: Wayland
Processors: 12 × AMD Ryzen 5 3600 6-Core Processor
Memory: 16 GiB of RAM (15.5 GiB usable)
Graphics Processor: AMD Radeon RX 6600

Comment 2 Akseli Lahtinen 2026-05-28 14:36:24 UTC

I think on wayland we should just add the "asn" value always as the desktopFileName value, if its empty. This seems to get rid of the startup bouncing effect getting stuck.

Comment 3 Nicolas Fella 2026-05-29 10:24:28 UTC

What's the behaviour we actually want? Do we want Konsole to pretend it's the other app (via --desktopfile), or consistently use konsole's appid?

The first option could work for Konsole (if we fix --desktopfile), but I don't think it's feasible for arbitrary terminal apps

Comment 4 Nicolas Fella 2026-05-29 10:57:54 UTC


*** This bug has been marked as a duplicate of bug 459986 ***

Comment 5 Akseli Lahtinen 2026-05-29 11:08:56 UTC

(In reply to Nicolas Fella from comment #3)
> What's the behaviour we actually want? Do we want Konsole to pretend it's
> the other app (via --desktopfile), or consistently use konsole's appid?
> 
> The first option could work for Konsole (if we fix --desktopfile), but I
> don't think it's feasible for arbitrary terminal apps

I would expect --desktopfile be the one that works.