From: usenet.16@scottsonline.org.uk.invalid   
      
   On 09/09/2025 11:05, Mike Scott wrote:   
   > Hmmm. I was interested in disabling lightdm at system boot time, to re-   
   > enable if/when needed.   
   >   
   > So I did 'systemctl | grep lightdm' which showed lightdm apparently   
   > under systemd control. Then 'systemctl disable lightdm' and reboot -   
   > fine, it's disabled; what I wanted.   
   >   
   > 'systemctl start lightdm' does indeed start it up, and the login greeter   
   > screen appears. Exactly the behaviour I want in the longer term.   
   >   
   > However, 'systemctl enable lightdm' just gives an error message:   
   (etc)   
      
   Sorry for following up my own query. It seems you're not supposed to do   
   this, but rather   
   systemctl set-default multi-user.target   
   (or graphical.target, as needed).   
      
   (I restored from a backup, and haven't tried the above yet)   
      
   But the question is still there: why does systemctl disable something it   
   can't then re-enable? A strange design choice.   
      
      
   --   
   Mike Scott   
   Harlow, England   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)