New Insync version: 3.0.28

Releases
#10

Can I upgrade safely from latest v3 to this v3 on Ubuntu 19.10?

#11

i would not recommend the migration for 1.5.7 to 3.0.28 just yet.

we are in the process of looking at the migration issues but it’s slated for 3.0.30 or beyond so if 1.5.7 still works for you, just stay with that.

thanks!

1 Like
#12

Thank you!

Finally a useful, to the point reply and advice.

I shall wait for 3.0.30 or later then.

Sad to see all these issues, really

#13

i really appreciate the feedback and yeah it sucks but the good news: we are focused on issues + headless.

we are listening :pray:t4:

#14

unable to download from http://yum.insync.io repo VERY SLOW …

#15
  1. I have my current insync install(s) 3.0.27 (Ubuntu Bionic / Deb Buster) set up the way I want and they are working.
    a. If its not broke don’t “fix” it?
    b. When / if upgrade will I have to reset everything … on 3 different machines all running different distros
  2. 1/29/2020 8:45a EST 3.0.28 does not show up* the Bionic repo at this time.
    a. Wait?
    *after running sudo apt update
  3. What happens if I run the new 3.0.28 .deb(s)? … over current installation(s)?

Thx

#16

Getting this error and can’t seem to “clear” it. How do I clear this issue?

image

#17

Hi @Andre_Verwijs,

This version is not yet available in the Linux repo, but we’ll put it up as soon as we release the update in our downloads page. :slight_smile: In the meantime, you may download the builds we linked above. Let me know if you’re having trouble with that.

#18

Hi @rrhobbs,

This is not yet available in our Linux repositories but we’ll update it as soon as the build can be released in our downloads page. :slight_smile: When you update, you won’t have to reset everything. You just need to quit your current version and install the latest.

#19

Hi @Andor_Kiss,

This is currently being worked on by our engineers. We’ll update all affected users as soon as the fix is available.

#20

miamoran: is this the long file name issue, or a different issue?

#22

Using the Ubuntu 18.04 version worked well and resolved the 416 error on Ubuntu 19.10.

1 Like
#23

Wierd, I have not problem running it after upgrade on my Fedora 31, although I’m on KDE Spin, but shouldn’t make a difference.

#24

Hi! It’s a different issue from what @Andor_Kiss has posted here.

#25

Does this include any fix to the memory leak on OSX? If not, is there an estimate which version (i.e. 29 or 30?) that will have that fix?

#26

Hi @inforr,

This build doesn’t have the fix yet, but the initial workaround will be available in 3.0.29 :slight_smile:

#27

Thank you to all Insync engineers! Yay, I can start using it again on Debian now :slight_smile:

1 Like
#28

@Pierre_Cornier Awesome. Thank you for waiting patiently!!

#29

I’ve been experiencing issues on Debian buster since the v3 upgrade.

The GUI seems to freeze when there is a sync in progress.
The taskbar icon is stuck on blue syncing status even though there is nothing that got modified.
Sometimes files get stuck in upload.
Scrolling on certain screens is locked up.
Closing the application windows is unresponsive on first click when sync is in progress.

So I’ve rolled back to the 1.5.7. I’m afraid version v3 brought few new features and plenty breakage. I prefer to have stable, boring applications.

Please clean up your game.

1 Like
#30

Hi @Zelmor,

Thank you for writing about your experience and my apologies for the experience.

Do you mind sending your logs to support@insynchq.com with the link to this post? Can you recall if it was a large sync at the time the issues started?