Insync (1.5.7) does not start

Bugs and issues Linux
#1

Hi,

I have Insync 1.5.7. It used to work, but now—possibly after an update of some other package—it stopped and I cannot launch it anymore.
I tried to update to 3, which launches but it is filled with serious syncing problems, so I downgraded back to 1.5.7 and would like to keep that, at least until the newer version is improved.

insync start gives no output. This is the output of insync start --no-daemon:

which: no kreadconfig in (/usr/lib/insync:/home/name/.cargo/bin:/home/name/.local/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/lib/jvm/default/bin:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl)
INFO     2019-10-22 12:40:37,514 [__main__insync__:main:105] insync version: 1.5.7.37371
INFO     2019-10-22 12:40:37,516 [__main__insync__:main:106] client created <ideskmain.client.Client object at 0x7f1f1f1dec50>
INFO     2019-10-22 12:40:37,517 [unix_socket_server_portable:start:49] unix socket server thread start
INFO     2019-10-22 12:40:37,518 [__main__insync__:main:114] starting client
INFO     2019-10-22 12:40:37,524 [fswatch:_start:532] LinuxFSWatcher._start
INFO     2019-10-22 12:40:37,526 [fswatch:_pull_loop:267] Inotify loop enter
Received signal 11 SEGV_MAPERR 000000000108
#0 0x7f1f22d9e58f <unknown>
#1 0x7f1f217d085d <unknown>
#2 0x7f1f22d9ea9e <unknown>
#3 0x7f1f4a7d5930 <unknown>
#4 0x7f1f3d6e1654 <unknown>
#5 0x7f1f3d6e28e8 <unknown>
#6 0x7f1f4836ea45 glXCreatePbuffer
#7 0x7f1f218327b9 <unknown>
#8 0x7f1f2181d818 <unknown>
#9 0x7f1f238da47d <unknown>
#10 0x7f1f21b21151 <unknown>
#11 0x7f1f21b22945 <unknown>
#12 0x7f1f23d90707 <unknown>
#13 0x7f1f255c7375 <unknown>
#14 0x7f1f22e06f45 <unknown>
#15 0x7f1f22e022e0 <unknown>
#16 0x7f1f4a7ca4cf start_thread
#17 0x7f1f4a3922d3 __GI___clone
  r8: 0000000000000000  r9: 0000000000000001 r10: 0000000000000000 r11: 0000000000000206
 r12: 00005599bd5465b0 r13: 00005599bd56ff00 r14: 0000000000000001 r15: 0000000000000009
  di: 00005599bd5465b0  si: 0000000000000000  bp: 00005599bd5465b0  bx: 0000000000000000
  dx: 0000000000008041  ax: ffffffffffffff50  cx: 0000000000000000  sp: 00007f1eafffe480
  ip: 00007f1f3d6e1654 efl: 0000000000010202 cgf: 002b000000000033 erf: 0000000000000004
 trp: 000000000000000e msk: 0000000000000000 cr2: 0000000000000108
[end of stack trace]
Calling _exit(1). Core file will not be generated.

Thank you for the support.

OFFICIAL: Insync 3 Formal Statement
#2

Hi @gmar

Which distro/version are you using?

#3

Thank you. I use Manjaro, Xfce 4.14.1, Kernel 5.3.

#4

I have the same error in 1.5.7 after update from Lubuntu (LXDE) 19.04 to 19.10.

#5

I tried v3 (downloaded installer for Ubuntu 19.10), and it starts but it doesn’t see my previous setup. So it asks if I want to add a Drive. When I click on add Google Drive, it says /usr/lib/insync/https:/www.insynchq.com/connect/blahblah?key=blahblah&cloud=gd No such file or directory.

#6

Since no solution for 1.5.7 was proposed, I ended up trying again with version 3, assuming it would be the only one supported from now on. It took me a few attempts, some unnecessary re-uploading of files, and the creation of some duplicates, resulting in the loss of a few folders. The update was not smooth, but after all that, now it seems to work correctly.

#7

That part worked for me. Directing to the same folder resulted in the previous setup to be recognized. I suggest you open a new thread for that problem to have better support.

#8

I reverted my laptop to Ubuntu 18.04 and get the same crash (see below). But v.1.5.7 (same binary) still works on my Linux PC (19.04) – I bet if I re-installed Insync there I would see the same crash, so I will not do that.

Maybe some recent update to Ubuntu has made v1.5.7 unusable after install ? I have sent the logs.db file to Support.

INFO 2019-10-31 17:56:01,260 [main__insync:main:105] insync version: 1.5.7.37371
INFO 2019-10-31 17:56:01,269 [main__insync:main:106] client created <ideskmain.client.Client object at 0x7f8b481c0190>
INFO 2019-10-31 17:56:01,281 [unix_socket_server_portable:start:49] unix socket server thread start
INFO 2019-10-31 17:56:01,286 [main__insync:main:114] starting client
INFO 2019-10-31 17:56:01,314 [fswatch:_start:532] LinuxFSWatcher._start
INFO 2019-10-31 17:56:01,321 [fswatch:_pull_loop:267] Inotify loop enter
Received signal 11 SEGV_MAPERR 000000000108
#0 0x7f3e1ed9e58f
#1 0x7f3e1d7d085d
#2 0x7f3e1ed9ea9e
#3 0x7f3e488e8540
#4 0x7f3e3a6c7954
#5 0x7f3e3a6c8be8
#6 0x7f3e461e2dc4 glXCreatePbuffer
#7 0x7f3e1d8327b9
#8 0x7f3e1d81d818
#9 0x7f3e1f8da47d
#10 0x7f3e1db21151
#11 0x7f3e1db22945
#12 0x7f3e1fd90707
#13 0x7f3e215c7375
#14 0x7f3e1ee06f45
#15 0x7f3e1ee022e0
#16 0x7f3e488dc669 start_thread
#17 0x7f3e4848d323 clone
r8: 0000000000000000 r9: 0000000000000001 r10: 0000000000000000 r11: 0000000000000206
r12: 0000562fed7bfe60 r13: 0000562fed92ce50 r14: 0000000000000005 r15: 0000562fed7eba20
di: 0000562fed7bfe60 si: 0000000000000000 bp: 0000562fed7bfe60 bx: 0000000000000000
dx: 0000000000008041 ax: ffffffffffffff50 cx: 0000000000000000 sp: 00007f3ddfffe480
ip: 00007f3e3a6c7954 efl: 0000000000010202 cgf: 002b000000000033 erf: 0000000000000004
trp: 000000000000000e msk: 0000000000000000 cr2: 0000000000000108
[end of stack trace]
Calling _exit(1). Core file will not be generated.

#9

I tried what gmar suggested, and installed v3 into 18.04 on the laptop and got that working. For some reason it then sync’d older files from the laptop to the PC, overwriting newer files. I had made a backup so I restored the newer files, after that it worked normally So for me that is settled for now. But maybe there is still an issue with v1.5.7 and v3 in Ubuntu 19.10.

#10

On my PC (Ubuntu 19.04) I tried upgrading from 1.5.7 to v3. I got the same error dialog box that I reported earlier:

/usr/lib/insync/https:/www.insynchq.com/connect/lGzXFlo3jz-long-string-Ob1Ku&cloud=gd: No such file or directory

So I copied the URL part of that, starting at https and not including the : after the gd:

https:/www.insynchq.com/connect/lGzXFlo3jz-long-string-vU9VOb1Ku&cloud=gd

and pasted into a browser. It prompted for Google permission, then the Insync app logged itself in correctly. After that was normal!

1 Like
#11

I have also had this problem and also want to encourage Insync to get back to work on fixing 1.5.7. As everyone has pointed out, Insync 3 is basically a whole different program with barely any overlap in functionality. It’s false to think that we can transition to Insync3 ---- a great many of us are still needing to use 1.5.7 because of lost functionalities in 3. Horrible rollout of terrible software with zero consultation of existing users. GET ON THIS INSYNC AND MAINTAIN 1.5.7!