On Mon, 2020-02-03 at 10:24 -0500, Jim Popovitch wrote: > On Mon, 2020-02-03 at 15:19 +0000, Nektarios Katakis wrote: > > Στις 2020-02-03 14:59, Jim Popovitch έγραψε: > > > 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 > > > > If no one else is using evolution on that PC you can do `rm > > /usr/lib/systemd/user/evolution-*` > > > > When you reinstall the package you ll have the service files back > > anyway. > > Thanks, I'd rather not do it that way. > > I guess I'll open a bug with Gnome to see if they can suppress the blue > connectivity warnings at startup as there is no need to report an error > that resolves itself once the user has started the application.
While messing around with some Evolution settings I resolved this problem by setting: Evolution -> Preferences -> Network Preferences -> Method to detect online state = Network Manager. Bam! Problem solved. -Jim P.