Don't auto-run applications until System Tray applet is loaded

[Fjodor42]

Case in point is that I have the ownCloud application set to run upon login, but its icon never shows in the System Tray applet. Once in a while, it crashes, and when run again, the icon shows up.

This leads me to believe that applications that are set to run upon login may be executed before the System Tray applet is fully functional, which is sub-optimal.

On my work laptop, the same behaviour can be seen with the Dropbox client, leading me to believe that this is indeed a Cinnamon problem, as opposed to a problem with the respective applications.

I am far from sure, but there may be a correlation in time with the time that the startup animation was introduced.

[mtwebster]

Depending on how your app is set to autorun, you probably could just set a slight delay in Startup Applications.

Long term, we could look at having our session handler wait until the desktop is fully-formed to load these apps.

[Fjodor42]

While I can confirm that setting a delay works around the problem, it would seem that at least Dropbox resets the delay to 0 when the client is updated.

For this reason, and since the default behaviour is suboptimal, I tend to think that a proper fix should be made - if at all possible.

[tp0]

@Fjodor42: Yes (except that it seems to reset after every boot, updating isn't needed for that to happen). Additionally, if you remove the auto-added Dropbox entry from the startup applications (and uncheck "start Dropbox on system startup" from Dropbox settings GUI) and add the same command there by yourself, it still doesn't seem to work reliably with the delay or not.

So, I removed both entries and added these into a script loaded on boot and now it seems to start properly everytime:

sleep 10
dropbox start -i

[Vahan86]

@Fjodor42, is this still an issue for you with Cinnamon 3.2?

[MegaV0lt]

After two years still not fixed. Why?

[Fjodor42]

@Vahan86 I believe it is, yes - sorry

[github-actions]

This issue has been automatically marked as stale because it has not had
any activity in over 2 years.

If this issue is still relevant:

• Please test on a current version of this package.
• Add a comment with your findings

If no activity occurs in the next 30 days, this issue will be
automatically closed. Issues can be reopened if needed.

[Fjodor42]

Have any attempts actually been made to fix this?

[JosephMcc]

No, nor are there any real plans to since there is a built in way to get around this sort of thing.