That won't happen. Use systemsettings/Advanced/Autostart instead.

You realize that is tiresome from user POV -- because when user uses Akr. and likes and wants it to start every time she/he would like to set it right away, from Akr. This is also more intuitive, i.e. "start every time _this_ app".

PS. Two avoid confusion, both ways should be provided -- for every app like Akr. -- because one person knows in advance what apps she/he wants to run, then SS->Adv.->Autostart is more handy, and another person, tries, works, and then adds it to his/her "toolbox".
In short -- in this case, there is no one way that fits all cases best.

It's still a environment issue. If system settings is not the right place because it's unintuitive, then it should be implemented differently (See e.g. OS X, where one can check an option in the app dock item's context menu).
An option in Akregator doesn't make sense as Autostart implementation depends on the environment Akregator runs in (KDE, Gnome, XFCE, $YourFavoriteWindowManager, OS X, Windows, all do it differently).

You run the same binary in Windows that I run in Linux/KDE?

But more importantly -- if you are trying to find here common denominator then you have to throw off a lot of functionality. In other words -- you are not letting KDE users to have potential because somebody _maybe_ run it in Gnome. Hmm, it would make sense, but -- is Akregator a KDE app, or not? It is OK to have only multiplatform features for multiplatform app, but "KDE app" means (?) -- "you can run it in Gnome too, but if you want to all the whistles install KDE".

It is not KDE fault that other DE don't have autostart and it is strange that KDE users have to pay the price of having crippled akregator because of existence of other DE. This simple rule don't change in computers -- if you want to please everyone you end up pleasing nobody.

Please reconsider reopening this issue. Changing autostart within app works perfectly for other applications, it is intuitive, natural, user-friendly and fast. App-problem task is "attached" to app (*).

(*) when you have to print document it is natural to focus on document, not on printer -- you don't "open printer" and choose which document you have to print.

I see that there is indeed API for this in kdelibs - KAutostart. So it doesn't require platform-specific hacks on the app side. Let's reopen the wishlist item then.

Which KDE apps already do provide autostart toggling from within the application?

I still think that an option in the taskbar/app icon context menu/etc. providing it for all KDE (and non-KDE) applications would be better than each app implementing a hard-to-find and differently labeled checkbox in their config dialog, with some apps having such an option and some not.

Frank, thank you!

Kpowersave, KGpg for example. From technical point of view you are right -- it is good to have main, control center and manage autostarting there. This is very useful. But one feature does not make the same feature in different shape an obsolete feature.

So you should have two places:
a) managing autostart, broad scope -> KControl, you set on some apps, you set of some
b) managing specific app -> its config, you set close behaviour, you set notifications, you set autostart, all in app's config dialog

I don't think anybody would say it is useful that if in order to config. some app you have to go to several control centers looking for your app pieces scattered all over the places, instead of configuring it in one place.

So depending what you want to do, KDE should give you a chance to do it in fast way.

And in time more and more apps will be unified (UI). Currently you don't drop "keep icon in systray on close" just because it is "hard-to-find and differently labeled checkbox", right? One step a time.

Thank you for the bug report.

As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists.

If this bug is no longer persisting or relevant please change the status to resolved.