My original intention to prevent autostarting was to prevent early startup of syncdaemon that would have caused even more login slowdowns. Now that is fixed I can create autostart entry.
The question is whether to add it globally or for the user upon initial application startup?
At the moment I see occasional (though rare) crashes of ubuntuone-indicator due to BadMatch X error. That's actually the reason why indicator does not hide itself when idle. If it is not shown then it must have crashed.
I think I should set ubuntuone-indicator to auto-restart after failures but that would clash with existing entries for ubuntuone-indicator (most likely) so I will need to handle the existing .desktop file in autostart directory too.
My original intention to prevent autostarting was to prevent early startup of syncdaemon that would have caused even more login slowdowns. Now that is fixed I can create autostart entry.
The question is whether to add it globally or for the user upon initial application startup?
At the moment I see occasional (though rare) crashes of ubuntuone-indicator due to BadMatch X error. That's actually the reason why indicator does not hide itself when idle. If it is not shown then it must have crashed.
I think I should set ubuntuone-indicator to auto-restart after failures but that would clash with existing entries for ubuntuone-indicator (most likely) so I will need to handle the existing .desktop file in autostart directory too.