You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After doing an auto-upgrade (triggered in a GUI dialog after seeing an error in Notification Centre) only one of my configs is reloaded automatically*.
It would be great if autostart was triggered afterwards to load all (both) configs.
Currently I need to run (obviously I didn't need to run the first command):
% maestral start -c Work
Daemon is already running.
% maestral start -c maestral
Starting Maestral... [OK]
% maestral autostart
Autostart is enabled. Use -N to disable.
% maestral --version
1.9.4
*In fact, looking at the PID numbers (low number from autostart after boot), I see that the Work deamon was never stopped by the upgrade process. I guess it was still using the older version. So no configs are autoloaded after an upgrade.
The text was updated successfully, but these errors were encountered:
After doing an auto-upgrade (triggered in a GUI dialog after seeing an error in Notification Centre) only one of my configs is reloaded automatically*.
It would be great if autostart was triggered afterwards to load all (both) configs.
Currently I need to run (obviously I didn't need to run the first command):
*In fact, looking at the PID numbers (low number from autostart after boot), I see that the Work deamon was never stopped by the upgrade process. I guess it was still using the older version. So no configs are autoloaded after an upgrade.
The text was updated successfully, but these errors were encountered: