Bug 508476

Summary: Autostart misses option to disable entry
Product: [Applications] systemsettings Reporter: Mark <markg85>
Component: kcm_autostartAssignee: Plasma Bugs List <plasma-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: normal CC: linux_rulez, nate, nicolas.fella
Priority: NOR    
Version First Reported In: 6.4.4   
Target Milestone: ---   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Mark 2025-08-19 14:36:10 UTC
Hi,

Autostart used to have (don't know how long ago) an option to temporarily disable autostarting of entries. It was the checkbox that used to be in there.

The current autostart just doesn't have the option at all.
Granted, i only used this feature like a few times over the past decade or so.

My usecase? I had a few applications running at startup but had to disable them because of a network bug i tried to solve on my end. Disabling and re-enabling is easy and convenient.

I ended up removing them instead. And then re-adding them after i solved my network issue.

In hindsight i discovered that this apparently now is done with user systemd unit files. And if i had known that i would've just done "systemctl disable <app>" ... But i didn't know.

Now this might raise a few "think about it" questions. Why would you, essentially, maintain a minimal systemd gui? In the KDE camp there is also SystemdGenie https://invent.kde.org/system/systemdgenie/ it would make a million times more sense to have that project "provide" a KCM instead. In fact, i'd consider that to be part of the KDE apps. I just installed it and the installation package is only a mere ~280kb.
Comment 1 Nate Graham 2025-08-19 19:04:49 UTC

*** This bug has been marked as a duplicate of bug 274920 ***
Comment 2 kaminata 2025-08-19 23:11:25 UTC
A quick example from Cinnamon:
https://i.imgur.com/oo74xJu.png

Nice and clean. And convenient.