Bug 269649 - KDE fails to know when application starts/crashes
Summary: KDE fails to know when application starts/crashes
Status: RESOLVED FIXED
Alias: None
Product: kde
Classification: I don't know
Component: general (show other bugs)
Version: 4.6
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-03-28 23:25 UTC by Lukas
Modified: 2020-09-28 23:31 UTC (History)
1 user (show)

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


Attachments
desktop file, created using Dolphin GUI (389 bytes, application/x-desktop)
2011-03-28 23:25 UTC, Lukas
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Lukas 2011-03-28 23:25:36 UTC
Created attachment 58411 [details]
desktop file, created using Dolphin GUI

Version:           4.6 (using KDE 4.6.1) 
OS:                Linux

This bug is about the "Starting response" - the bouncing icon next to the cursor then application is started.

In some cases KDE fails to know the sate of started application and tends to show bouncing icon until it timeouts. It creates an impression that KDE is super slow, while its obviously no true.

When such behavior was noticed:

Starting an application with desktop file like Net Beans. Starting from bin file works OK (see attachment).

Clicking the links outside the browser, while Firefox is default browser. If FF was open at the time link was pressed, it will be opened in existing window.

Opening applications with problems like with missing dependencies. Starting such application from CLI immediately gives error about missing dep and exits. However doing it in a GUI way, it looks like it dies silently after timeout. Try setting up Skype on fresh instal. 

 

Reproducible: Always



Expected Results:  
KDE should do a extra check each e.g 3-5 seconds, if application/thread s still running. If not, kill the animation and give error message, if possible.
Comment 1 Christoph Feck 2011-03-30 20:50:20 UTC
Netbeans and Firefox are no KDE applications, so I doubt they support the freedesktop startup nofification protocol.
Comment 2 Lukas 2011-03-31 15:01:27 UTC
Probably not, but there are too many apps that don't follow free desktop, that it would be not wise to ignore them. 

At least it should be possible to check if app don't support startup notifications and then reduce timeout to 5-10 seconds max
Comment 3 Lukas 2011-04-02 14:07:11 UTC
Its also broken with Amarok. 

Try to add files from Dolphin, while Amarok is running. So its more likely a bug with KDE, not only within implementation of startup notification protocol.
Comment 4 Andrew Crouthamel 2018-11-05 03:07:15 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 5 Andrew Crouthamel 2018-11-16 05:32:12 UTC
Dear Bug Submitter,

This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version?

Thank you for helping us make KDE software even better for everyone!
Comment 6 Nate Graham 2020-09-28 23:31:56 UTC
No response; assuming it was fixed since then.