Maestral no longer launching at startup

[pintapass]

I've got a dual instance of Maestral — one for work, one for personal files. It's been working fine for a year, even after migrating to an M1 Mac and subsequently upgrading to Ventura (11.3).

However, since 1.7.x, Maestral is no longer launching both instances on startup. Sometimes it doesn't even launch one. The "Start at login" item is checked for both instances.

When they both fail to launch, clicking on the Maestral app icon typically launches the personal (primary) instance, as expected.

If I go to the command line and enter, maestral gui -c work, it will launch the second instance, but the terminal output will be as follows:

app_packages/rubicon/__init__.py:5: DeprecationWarning: Deprecated call to pkg_resources.declare_namespace('rubicon'). Implementing implicit namespace packages (as specified in PEP 420) is preferred to pkg_resources.declare_namespace. See https://setuptools.pypa.io/en/latest/references/keywords.html#keyword-namespace-packages [Cocoa] Not implemented: ScrollContainer.set_on_scroll()

As soon as I close the Terminal, it terminates the second Maestral (work) instance.

[samschott]

The second part of the description, manually launching the GUI, looks correct to me. Both warnings can be safely ignored.

However, since 1.7.x, Maestral is no longer launching both instances on startup. Sometimes it doesn't even launch one. The "Start at login" item is checked for both instances.

This is definitely not working as intended. Could you try the following, in order?

1. Uncheck and then check again the "Start at login" option. This will recreate the launch entries.
2. Log out and log in again.
3. If you don't see both instances starting, try to manually launch them using launchctl in the Terminal. The commands for the default and the work instance are:

   launchctl start com.samschott.maestral.maestral
   launchctl start com.samschott.maestral.work

4. If that does not work either, I'd be curious to see the content of the respective launch plists at ~/Library/LaunchAgents. Maybe something went wrong when creating them.

[pintapass]

I had cleared the LaunchAgents, checked and unchecked the "Start at login" option in both Maestral instances, made sure the "Open at Login" items were present in System Preferences (now System Settings), run Onyx, etc.

But running those two commands:

launchctl start com.samschott.maestral.maestral
launchctl start com.samschott.maestral.work

... launched both instances immediately and appears to have survived a reboot. So whatever that did, fixed it. Thanks!

[samschott]

Interesting. This indicates that maybe some registration logic is now required to add startup items which is not being run automatically.

[walterheisenberg]

I have the same problem, but with virtualenviroment on Kubuntu 23.04: maestral doesn't autostart. I have to source maestral-venv/bin/activate to be able to start maestral.

ralf@ralf-Aspire-1810TZ:~$ maestral
Traceback (most recent call last):
  File "/home/ralf/.local/bin/maestral", line 5, in <module>
    from maestral.cli import main
ModuleNotFoundError: No module named 'maestral'
ralf@ralf-Aspire-1810TZ:~$ source maestral-venv/bin/activate
(maestral-venv) ralf@ralf-Aspire-1810TZ:~$ maestral gui

then maestral works until I close the console-window. How can I have maestral gui autostart again?

btw: I needed to enable system-site-packages to activate dbus in venv. Without it, maestral didn't work. python3 -m venv --system-site-packages maestral-venv

Thanks in advance

PS: If you think, that this is worth a separate Issue, please split it.

[samschott]

@walterheisenberg, I've moved this to a new issue since autostart in your case works very differently compared to a bundled macOS App.