alexball

I have found that on faster computers the indicator gets loaded twice, once as a child of init and once as a child of btsync-starter. It took me a while to work out what was wrong (I had wondered if it was an issue with KDE's session management, for example) but what seems to have solved it for me is to introduce an extra delay in the btsync-starter script. In the definition of agent_runner(), I inserted a 'sleep 1' line just before 'start_frontend', and that seems to have done the trick.