Bug 274920

Summary:	Control of system/distro-provided startup elements
Product:	[Applications] systemsettings	Reporter:	Tim Edwards <tkedwards>
Component:	kcm_autostart	Assignee:	Plasma Bugs List <plasma-bugs>
Status:	CONFIRMED ---
Severity:	wishlist	CC:	justin, Makuru_DD, mo78, myndstream, nate, null, rb03884, SaburoutaMishima, thomas.sisson.1
Priority:	HI
Version:	unspecified
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:
Bug Depends on:	430522
Bug Blocks:

Description Tim Edwards 2011-06-04 15:51:36 UTC

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.

Comment 1 Thomas Sisson 2013-09-28 21:53:03 UTC

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.

Comment 2 Tim Edwards 2013-09-29 14:27:10 UTC

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.

Comment 3 Roman Bysh 2013-11-01 23:47:57 UTC

C'mon. This has been over two years now. How difficult is it?

Comment 4 David Edmundson 2015-09-26 14:17:20 UTC

*** Bug 328276 has been marked as a duplicate of this bug. ***

Comment 5 Roman Bysh 2015-10-01 20:08:21 UTC

Follow up please

Comment 6 fire f. 2018-11-19 10:40:55 UTC

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 .

Comment 7 Nate Graham 2023-07-25 15:59:27 UTC

*** Bug 430522 has been marked as a duplicate of this bug. ***

Comment 8 Nate Graham 2023-07-25 15:59:32 UTC

*** Bug 427855 has been marked as a duplicate of this bug. ***

Comment 9 Nate Graham 2023-09-18 18:18:06 UTC

*** Bug 428094 has been marked as a duplicate of this bug. ***

Comment 10 Nate Graham 2023-09-18 18:18:10 UTC

*** Bug 465271 has been marked as a duplicate of this bug. ***

Comment 11 Nate Graham 2024-04-09 20:17:07 UTC

*** Bug 485281 has been marked as a duplicate of this bug. ***

Comment 12 Nate Graham 2024-04-09 20:17:12 UTC

*** Bug 483508 has been marked as a duplicate of this bug. ***