@Vik_and_Pam: Have you tried the build for Ubuntu 16.04: https://d2t3ff60b2tol4.cloudfront.net/builds/insync_1.3.15.36150-xenial_amd64.deb?
I used the version from your repository, which I have added to my sources. So I ran an apt update, then upgrade. At this point it stopped working, after I received the prompts to restart Nautilus and restart insync.
I can try downloading directly and applying it again. Will let you know.
It seems to worked using that .deb file. I’m not on the current version and running well. Thx!
@Vik_and_Pam: Have you tried the build for Ubuntu 16.04: https://d2t3ff60b2tol4.cloudfront.net/builds/insync_1.3.15.36150-xenial_amd64.deb1?
This works fine for me at Ubuntu Mate 16.04.
Thanks.
Hi, Luis solved with test build for Ubuntu 17.04 available here: New Insync version: 1.3.15.
Today, as soon as version 1-3-16 was released and installed, the service is newly in error… :(((
Installing this version also solved my problem of Insync not starting however now Ubuntu Software updater tells me there is a newer version:
Changes for insync versions:
Installed version: 1.3.15.36150-xenial
Available version: 1.3.16.36155-trusty
Running Ubuntu Mate 16.04
@robbielink: Please confirm that the contents of the file /etc/apt/sources.list.d/insync.list is deb http://apt.insynchq.com/ubuntu xenial non-free contrib. It looks like you are using the one for trusty instead.
2 Likes
Ah, yes - wondered about that. Fixed. Thanks!
Thank you, @Ipugoy. This solution worked for me, too. I never thought to check my sources list.
I had a similar issue where after an upgrade my insync broke on Ubuntu MATE 16.04 LTS. In the course of troubleshooting I did check my apt sources and found what @lpugoy said about the source for insync being set to trusty instead of xenial. Manually changing the source file fixed it no problems after a sudo apt update && sudo apt upgrade
For what it’s worth to the insync folks, I installed mine via the built in Ubuntu MATE Software Boutique. I don’t know if that is similar with others who saw this issue or not, or if that helps with tracking down the source of the bug.
Thanks this fixed my issue in ubuntu mate 17.04