screencloud
screencloud copied to clipboard
Upstart issues with new version
Hey, I'm really glad to see a new version of SC out! :D
But I'm having this strange issue with starting the program now.
When I first tried, right after updating (I removed the 15.10 repo and added the 16.04 repo, but did not uninstall/reinstall) starting it from the system menu it did not start, I only got this error message:
But starting it from terminal worked fine.
Well when I turned my pc on this morning SC did not start up automatically as it has always done before. But now I can start it from the menu with no error message! I checked that the settings still says that it should start on boot, and I checked the list of startup applications on my system. Then I rebooted, just to check, but it still did not start automatically (but again I could start it from the system menu without any apparent issues)
PS: this is what it says in my startup applications system (I have not added this manually, it's what was added when I turned on Run on startup in the SC preferences, IIRC):
Try turning off "Run on startup", quitting the app, and turning it back on again. That way the .desktop file will be removed and replaced with a new one. The /opt/screencloud
part is from the older versions and shouldn't be there anymore.
Thanks! I tried that. It changed the command in the Startup Apps settings to /usr/bin/screencloud-1.3.0.sh, but it still does not start on boot.
Here too, ubuntu 16.04, screencloud at some point last month stopped starting up. No errors, just does not start. The checkbox is active both in Screencloud preferences and in the Ubuntu Startup Applications Preferences. I am sure it was working when I first installed it a few months ago, and did stop working in the last month.
any log I can send to help?
I did the same as @ildella , but instead of /usr/bin/screencloud-1.3.0.sh, i changed it to /usr/bin/screencloud, and now it starts on boot.
thanks @coffeverton that worked.
This issue has had no activity in the last 60 days. Please add a reply if you want to keep this issue active, otherwise it will be automatically closed after 30 days.
This issue was closed because of inactivity. If this issue is still relevant, please re-open a new issue.