I can confirm that this approach appears to have worked for me. At first I tried renaming the ~/.config/insync folder out of the way, and then created a symlink to the ~/config/Insync folder, but that crashed Insync. So I used your approach and that worked.
Thanks.
I also solved just deleting ~/.config/insync and renaming ~/.config/Insync to ~/.config/insync .
Can confirm this is the simplest and correct solution.
Please be very careful with symlinking different directories together etc, you may make life harder for yourself in future.
The developers really need some better automated testing to catch nonsense like this… We’re on these forums and can see what’s happening but the vast majority of users have just experienced data loss and are probably unlikely to continue to use InSync.
I didn’t notice - is there an official way to submit a bug or best to just post in the forums?
This forum is also the works as the public bug tracker. Bug reports are tagged appropriately. Normally they’re very responsive, but COVID has hurt the rhythm a bit.
Hello everyone. Mia here, speaking on behalf of the Insync team.
We truly and sincerely apologize for the serious bug that 3.7.4 introduced for Linux users. We understand that our words simply won’t take back what has happened to those who have lost their previous Insync configuration and needed to start over, as well as for those of you who needed to find a solution as quickly as possible.
Our engineers have been alerted on the urgency of this situation. They are working on rolling back 3.7.4 on Linux both in our webpage and the repositories so that it will not be further accessed by our Linux community while we address the issue.
The fix will be deployed in v3.7.5 – rest assured that we will take your workaround into account to ensure that the next version goes smoothly for everyone, including the affected users who have renamed their Insync config folder. We are also implementing stricter measures in the testing phase to avoid anything like this again moving forward.
Please don’t hesitate to comment here or reach out via email if you have any questions or concerns.
Thanks for the update! Indeed, after reconfiguring Insync I now have .config/Insync and .config/insync
Can I safely delete the old capital-I Insync folder? Or will 7.3.5 revert to the previous name?
Cheers: Chris
I ran the update this morning, about 9 hours ago, and that’s when I found this thread. Disappointed that there’s been no official acknowledgement of the issue as of yet (although perhaps I just missed it).
I didn’t run the Insync setup after the update so it appears that I still have my ~/.config/Insync folder intact, but I would like to hear from the company before proceeding with any work-around. If they’re going to issue a fix using Insync rather than insync, I’ll wait for that.
This very thread has the official response via miamoran, as of 5 hours ago. The post itself is here.
Thanks for pointing that out. I submitted my comment about 4 hours before the official response, but because I had never used the forum before, my post was put on moderation.
No worries, we’re all starting from the same point. Welcome to the community!
Hi Mia,
Can you confirm this bug is affecting only Linux users? I’m having another issue related to the upgrade but didn’t want to post it if it’s tied somehow to this thread’s issue.
Let me know if it’s unrelated and I’ll submit a proper bug with logs, etc. - but basically I’m getting a message to upgrade and restart, but nothing seems to happen when I click on the link (there is no upgrade or restart (have quit Insync and restarted/rebooted and old version number is still present and I’m prompted again to Update and restart. I’ve made sure no syncing is in progress before clicking on the Update and restart app link. I’ve tried this 4 or 5 times with the same result.
HI @brandtryan,
Yes, this particular issue on lost configuration/settings is only Linux-specific.
Could you please send the following to support@insynchq.com with the link to this post:
Those files can be located by following this guide. Thank you!
Hi @Christian_Frank,
This is the simplest workaround that has been effective for users: Lost settings & a couple of crashes after 3.7.4 upgrade
Hello all! For those wondering what would happen to your current settings (if you started over) once 3.7.5 is rolled out, I addressed it here. Thank you!
Confirm similar behaviour on Ubuntu 21.10. Upgraded, got the “upgrade is complete, you can start Insync” window, hit “start”, and got the new account login window. Tried to log in, Insync crashed.
Now Insync won’t start at all. I’ve tried all of the workarounds mentioned in these threads… Moving the insync folder to insync-bad and renaming Insync to insync, just symlinking insync to Insync, nothing works. Insync will not start.
Totally locked out of my syncing right now, and Insync is my only sync option from my Ubuntu box. I really need to get Nextcloud going on my NAS and just turf Insync and Google Drive. This is the third time in the history of using it that Insync has shat its pantaloons and left me stranded.
user@computer:~/.config$ insync start --no-daemon
Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use QT_QPA_PLATFORM=wayland to run on Wayland anyway.
``
(insync:8240): GLib-GIO-ERROR **: 09:23:57.319: Settings schema 'org.gnome.settings-daemon.plugins.xsettings' does not contain a key named 'antialiasing'
Trace/breakpoint trap (core dumped)
user@computer:~/.config$
Indeed, I just lost a bunch of offline work! This is crazy!
Hello, @ekalfwonS!
My deepest apologies for the mess that this update has caused on your end. Could you please let me know if rolling back to 3.7.3 helps? For reference, we have pulled out 3.7.4 from our downloads page and repositories to prevent more users from accessing this version.
Our downloads page for Linux shows 3.7.3 - you may check it out here: https://insynchq.com/downloads
Thank you!
Hello! Our Windows team has been alerted about this and I will be updating here once I know more.