Bug 162321

Summary:	Launch feedback times out even if application was successfully started
Product:	[Frameworks and Libraries] kdelibs	Reporter:	Armin Berres <armin>
Component:	klauncher	Assignee:	kdelibs bugs <kdelibs-bugs>
Status:	RESOLVED FIXED
Severity:	normal	CC:	cullmann, dominik.tritscher, greg_g, roland.leissa, th-fr, wilderkde, zahl
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Compiled Sources
OS:	Linux
Latest Commit:		Version Fixed In:

Description Armin Berres 2008-05-19 20:06:06 UTC

Version:            (using Devel)
Installed from:    Compiled sources

When starting apps like iceweasel (the Debian name of firefox) or kmix, the launch feedback doesn't vanish when the app is started. It stays there until the 30 seconds timeout is over.
For other applications like akregator or OOo I don't see this problem. One interesting thing: When i starticeweasel as "mozilla" it also works fine.

Comment 1 Roland Leißa 2008-12-01 23:51:27 UTC

same problem here with kmix and some other apps. (KDE 4.1.3, gentoo packages)

Comment 2 Dominik Tritscher 2009-05-24 15:38:51 UTC

I can confirm this issue for kmix. But the same behaviour is shown, if I launch kmix from kickoff. So this seems to be no krunner issue.

Comment 3 Jacopo De Simoi 2009-05-24 15:58:45 UTC

It happens with a bunch of apps: firefox, kopete, kmix, skype. It's a problem in kdelibs (kio?) as far as I can understand

Comment 4 Dominik Tritscher 2009-05-24 16:53:30 UTC

Moved to kdelibs, as this also happens with other application launchers.

Comment 5 Armin Berres 2009-07-21 15:00:30 UTC

Still happens with KDE 4.3 rc2.
rsibreak also triggers the problem.

Comment 6 Thomas 2013-01-07 11:40:19 UTC

It still happens when the application is started minizied (to system tray) in KDE SC 4.9.5 (arch linux). For example, if you close Kopete minimized, it will start minimized and will not disable the launch feedback.

Comment 7 Christoph Cullmann 2024-05-01 20:46:46 UTC

Hi,

the KDE libaries and applications version 4.x are obsolete and got replaced
with Frameworks 5 and now 6 based variants that are still maintained.

The issue in this bug doesn't seem to happen for me with these versions.

If it still happens with some application, please report it there, the startup notification handling might be broken there.