Version: unspecified (using KDE 4.6.0) OS: Linux There are several programs which without any custom settings in ~/.kde4 (ie. on a blank home directory) would startup automatically with KDE. These programs are defined by .desktop files in /usr/share/autostart. Examples include klipper, knetworkmanager and kmix. The problem is that once a user closes on of these programs manually an 'autostart=false' entry is created in that program's ~/.kde4/share/config/<program name>rc file. There is no way to get it to start with KDE again except by manually editing ~/.kde4/share/config/<program name>rc to say autostart=true. This changing of the autostart parameter should be exposed and handled by the Autostart control centre module, enabling the user to see these programs that are defined in /usr/share/autostart and have an enable/disable option for each one that sets autostart= in the corresponding ~/.kde4/share/config/<program name>rc Reproducible: Always Steps to Reproduce: 1. Click on klipper icon and choose 'quit' 2. When it asks tell it not to automatically start 3. Logout, log back in and verify klipper didn't start. 4. Start klipper from the menu or krunner or wherever - it runs normally Actual Results: Logout and log back in - no klipper, klipper is not started with KDE. Expected Results: An option exists in the Autostart control centre module to enable or disable the autostarting of klipper with KDE.
Has this been fixed? If not, can you add /etc/xdg/autostart/ as well? I would suggest adding a tab to the current Autostart settings module for System autostart and labeling the other one as Personal. The system tab would prompt the user for a password similar to other system adminitration functions. Meanwhile, someone needs to figure out what to do about the ~/.config/autostart directory. Until software developers can figure out a way of including QT support and quit locking programs to Gnome specific programs like Nautilus, it may easier to have a separate kde/Autostart directory. The OnlyShowIn and NotShowIn keys can be confusing and may not be set properly for various reasons, so though moving the personal KDE Autostart directory to .config could create havoc. As things stand, I manually edit .desktop files in system autostart directories, or create edited copies in .kde and/or .config directories to add OnlyShowIn or NotShowIn keys. However, it is still possible to mess things up even if one understands how to use those keys, so this is not a user friendly approach.
I don't think this has been fixed or even looked at. The current behaviour is definitely not user-friendly or in any way intuitive.
C'mon. This has been over two years now. How difficult is it?
*** Bug 328276 has been marked as a duplicate of this bug. ***
Follow up please
true. the several /usr/*/autostart/* or wherever they may hide need a KCM to deal with all of them. a button would be placed appropiately in the systemd-KCM .
*** Bug 430522 has been marked as a duplicate of this bug. ***
*** Bug 427855 has been marked as a duplicate of this bug. ***
*** Bug 428094 has been marked as a duplicate of this bug. ***
*** Bug 465271 has been marked as a duplicate of this bug. ***
*** Bug 485281 has been marked as a duplicate of this bug. ***
*** Bug 483508 has been marked as a duplicate of this bug. ***