Bug 374041 - Cannot start service if it is disabled
Summary: Cannot start service if it is disabled
Status: REOPENED
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_systemdgenie (other bugs)
Version First Reported In: unspecified
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: Ragnar Thomsen
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-12-22 14:02 UTC by Alexander Potashev
Modified: 2025-07-17 14:40 UTC (History)
3 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alexander Potashev 2016-12-22 14:02:36 UTC
I want to start a service, but I don't want it to start on system boot.
Comment 1 Ragnar Thomsen 2016-12-31 11:08:40 UTC
Git commit c578cbba22c0bd83357761d2b4ae2751d03d6c5d by Ragnar Thomsen.
Committed on 31/12/2016 at 11:05.
Pushed by rthomsen into branch 'master'.

Enable starting units with no Unit dbus object

For units with no Unit dbus object we cannot query the CanStart property
so just enable the start unit action unconditionally.

M  +3    -1    src/mainwindow.cpp

https://commits.kde.org/systemdgenie/c578cbba22c0bd83357761d2b4ae2751d03d6c5d
Comment 2 Ragnar Thomsen 2016-12-31 11:09:26 UTC
Thanks for reporting. Should be fixed with the above commit.
Comment 3 biohazard777.bgo 2021-09-06 16:22:12 UTC
(In reply to Ragnar Thomsen from comment #2)
> Thanks for reporting. Should be fixed with the above commit.

Hi, it appears that the bug is back.
I'm running:
Manjaro Linux x86_64
Kernel: 5.10.61-1-MANJARO (64 bit)
KDE Plasma 5.22.5
KDE Frameworks: 5.85.0
Qt: 5.15.2
SystemdGeanie: 0.99.0

I've got postgresql 13.3 installed which I don't want to start on system boot.
From SystemdGeanie I have to "Enable Unit" first, then "Start unit" and then "Disable Unit".
Wile from the terminal I can just run: systemctl start postgresql.

PS I'm new here, I have read the bug reporting instructions and if I understood it correctly: adding a comment with "reopened" status is the right thing to do since the bug was already reported once. Please let me know if I should have done it differently. 
Best regards.
Comment 4 Guillaume BINET 2025-07-17 14:40:48 UTC
I confirm on Arch Linux too.

This was specifically for this use case I installed this tool: I am on a laptop and I don't want cups or ollama running when I don't need them.