Re: Delay evolution-*-factory startup

[Jim Popovitch <jim@k4vqc.com>]

On Mon, 2020-02-03 at 14:49 +0000, Nektarios Katakis wrote:
> Στις 2020-02-03 14:24, Jim Popovitch έγραψε:
> > On Mon, 2020-02-03 at 14:07 +0000, Nektarios Katakis wrote:
> > > Στις 2020-02-03 12:59, Jim Popovitch έγραψε:
> > > > Hello!
> > > > 
> > > > Is there a way in Buster+Cinnamon to disable evolution-
> > > > (calendar|addressbook)-factory until after a VPN has connected?
> > > > 
> > > > Everytime I login and start Evolution I have a handful of blue
> > > > warnings,
> > > > that I must clear, because Evolution was unable to connect to services
> > > > only available over a VPN. By the time I clear the blue warnings the
> > > > VPN
> > > > is active, the warning just accrue after login and before network
> > > > manager activates the VPN.
> > > > 
> > > > -Jim P.
> > > 
> > > You can run the VPN as a systemd user service as the Evolution is now.
> > > And put VPN service to run before the evolution one.
> > 
> > The NetworkManager-OVPN depends on user configuration, therefore the 
> > VPN won't start until after user login.
> 
> The calendar service should be the same. Since it s a user service it 
> starts after you login.

It does, but I don't want it started until after it can reach the
calendar server (which is only available on the VPN).

> > > Alternatively you can disable evolution from starting automatically 
> > > and
> > > do it once you have connected manually in your VPN.
> 
> To disable it you can try: `systemctl --user disable 
> evolution-calendar-factory.service`
> Alternatively you can remove the WantedBy block from the unit file.

Thanks again, unfortunately that doesn't seem to survive a reboot. :-(

I tried disabling all evolution related services, but they still startup
after a normal reboot

-Jim P.