After upgrade from 1.4.9 to 1.5.1, Insync fails to start

Konstantin_Boyandin · September 13, 2018, 1:06pm

Today I updated insync to the latest version (Ubuntu 16.04.5 64-bit), namely 1.5.1.37343

It stopped starting immediately. “insync show” prints

Traceback (most recent call last):
  File "isyncd/linux/headless/cli.py", line 108, in ipc_insync
  File "socket.py", line 228, in meth
error: [Errno 111] Connection refused

On my other computer insync (1.4.9.37127) works without problems.

Questions:

How to fix the 1.5.1 startup problem?
Where can I download the older version (1.4.9), since it’s seems working fine ?

Thanks

Konstantin_Boyandin · September 13, 2018, 1:48pm

Update: I downgraded insync to 1.4.9, having downloaded the .deb from links here.

Looks like I will keep it at hand while 1.5.1 startup issue is being studied.

Also: version 1.5.1., when run as “insync start --no-daemon” prints:

NFO     2018-09-13 20:33:01,777 [__main__insync__:main:98] insync version: 1.5.1.37343
INFO     2018-09-13 20:33:01,778 [__main__insync__:main:99] client created <ideskmain.client.Client object at 0x7f9165083b90>
INFO     2018-09-13 20:33:01,778 [unix_socket_server_portable:start:49] unix socket server thread start
INFO     2018-09-13 20:33:01,779 [__main__insync__:main:107] starting client
INFO     2018-09-13 20:33:01,782 [fswatch:_start:532] LinuxFSWatcher._start
INFO     2018-09-13 20:33:01,783 [fswatch:_pull_loop:267] Inotify loop enter
libpng warning: iCCP: known incorrect sRGB profile
[0913/203301.811310:WARNING:stack_trace_posix.cc(699)] Failed to open file: /tmp/.glj5KiHk (deleted)
  Error: No such file or directory
INFO     2018-09-13 20:33:01,979 [gdsyncer:sync_account:153] Syncing GDUser(id=u'111494326092827652999', email=u'[email removed]', name=u'[name removed]').
libGL error: No matching fbConfigs or visuals found
libGL error: failed to load driver: swrast
Received signal 11 SEGV_MAPERR 0000000001c5
#0 0x7f916ad8c95f <unknown>
#1 0x7f91697be85d <unknown>
#2 0x7f916ad8ce6e <unknown>
#3 0x7f91a85f0390 <unknown>
#4 0x7f91345a5321 <unknown>
#5 0x7f9169820949 <unknown>
#6 0x7f916980b9a8 <unknown>
#7 0x7f916b8c8add <unknown>
#8 0x7f9169b0f411 <unknown>
#9 0x7f9169b10c05 <unknown>
#10 0x7f916bd7eea7 <unknown>
#11 0x7f916d5b5c65 <unknown>
#12 0x7f916adf5315 <unknown>
#13 0x7f916adf06b0 <unknown>
#14 0x7f91a85e66ba start_thread
#15 0x7f91a79f241d clone
  r8: 0000000000000000  r9: 0000000000000000 r10: 00000000000000e9 r11: 0000000000000000
 r12: 000000000000010d r13: 000000000000000a r14: 000000000000009a r15: 000000000000000a
  di: 00000000030499c4  si: 0000000000000001  bp: 00007f91357f9590  bx: 0000000003041bb0
  dx: 0000000000000019  ax: 00000000030499b0  cx: 0000000000000001  sp: 00007f91357f9530
  ip: 00007f91345a5321 efl: 0000000000010206 cgf: 002b000000000033 erf: 0000000000000004
 trp: 000000000000000e msk: 0000000000000000 cr2: 00000000000001c5
[end of stack trace]
Calling _exit(1). Core file will not be generated.

void75 · September 13, 2018, 2:56pm

Same error on me.
And I can’t find old package for trusty distro. ;-(

Traceback (most recent call last):
File “isyncd/linux/headless/cli.py”, line 108, in ipc_insync
File “socket.py”, line 224, in meth
error: [Errno 111] Connection refused

Konstantin_Boyandin · September 13, 2018, 3:10pm

Cached packages might still be present in /var/cache/apt/archives

Otherwise, ask the developers…

izk8 · September 13, 2018, 8:08pm

Exact same issue here.

“insync show”

Traceback (most recent call last):
  File "isyncd/linux/headless/cli.py", line 108, in ipc_insync
  File "socket.py", line 228, in meth
error: [Errno 111] Connection refused

and “insync start --no-daemon”

INFO     2018-09-13 16:03:23,676 [__main__insync__:main:98] insync version: 1.5.1.37343
INFO     2018-09-13 16:03:23,677 [__main__insync__:main:99] client created <ideskmain.client.Client object at 0x7f3545570b10>
INFO     2018-09-13 16:03:23,677 [unix_socket_server_portable:start:49] unix socket server thread start
INFO     2018-09-13 16:03:23,678 [__main__insync__:main:107] starting client
INFO     2018-09-13 16:03:23,681 [fswatch:_start:532] LinuxFSWatcher._start
INFO     2018-09-13 16:03:23,682 [fswatch:_pull_loop:267] Inotify loop enter
libpng warning: iCCP: known incorrect sRGB profile
[0913/160323.700308:WARNING:stack_trace_posix.cc(699)] Failed to open file: /tmp/.glDyyOZG (deleted)
  Error: No such file or directory
libGL error: No matching fbConfigs or visuals found
libGL error: failed to load driver: swrast
Received signal 11 SEGV_MAPERR 000000000165
#0 0x7f354b47095f <unknown>
#1 0x7f3549ea285d <unknown>
#2 0x7f354b470e6e <unknown>
#3 0x7f35876be390 <unknown>
#4 0x7f34f35ab321 <unknown>
#5 0x7f3549f04949 <unknown>
#6 0x7f3549eef9a8 <unknown>
#7 0x7f354bfacadd <unknown>
#8 0x7f354a1f3411 <unknown>
#9 0x7f354a1f4c05 <unknown>
#10 0x7f354c462ea7 <unknown>
#11 0x7f354dc99c65 <unknown>
#12 0x7f354b4d9315 <unknown>
#13 0x7f354b4d46b0 <unknown>
#14 0x7f35876b46ba start_thread
#15 0x7f3586ac041d clone
  r8: 0000000000000000  r9: 0000000000000000 r10: 00000000000000e9 r11: 0000000000000000
 r12: 00000000000000ad r13: 000000000000000a r14: 000000000000009a r15: 000000000000000a
  di: 0000000002a69734  si: 0000000000000001  bp: 00007f35117f9590  bx: 0000000002a62220
  dx: 0000000000000019  ax: 0000000002a69720  cx: 0000000000000001  sp: 00007f35117f9530
  ip: 00007f34f35ab321 efl: 0000000000010216 cgf: 002b000000000033 erf: 0000000000000004
 trp: 000000000000000e msk: 0000000000000000 cr2: 0000000000000165
[end of stack trace]
Calling _exit(1). Core file will not be generated.
[3:3:0100/000000.782978:FATAL:zygote_linux.cc(495)] Check failed: len > 0 (0 vs. 0)
#0 0x7ff48e2b495f <unknown>
#1 0x7ff48e2cfe7c <unknown>
#2 0x7ff48d37fb5a <unknown>
#3 0x7ff48d380988 <unknown>
#4 0x7ff48d380e2b <unknown>
#5 0x7ff48d3813b3 <unknown>
#6 0x7ff48d3817ed <unknown>
#7 0x7ff48d38300c <unknown>
#8 0x7ff48e279b8c <unknown>
#9 0x7ff48e27a1df <unknown>
#10 0x7ff48f4a6d24 <unknown>
#11 0x7ff48e278e75 <unknown>
#12 0x7ff48cd4b453 QtWebEngine::processMain()
#13 0x000000400bad main
#14 0x7ff488e8e830 __libc_start_main
#15 0x000000400c19 <unknown>

Received signal 6
#0 0x7ff48e2b495f <unknown>
#1 0x7ff48cce685d <unknown>
#2 0x7ff48e2b4e6e <unknown>
#3 0x7ff489aea390 <unknown>
#4 0x7ff488ea3428 gsignal
#5 0x7ff488ea502a abort
#6 0x7ff48e2b33d9 <unknown>
#7 0x7ff48e2cffcf <unknown>
#8 0x7ff48d37fb5a <unknown>
#9 0x7ff48d380988 <unknown>
#10 0x7ff48d380e2b <unknown>
#11 0x7ff48d3813b3 <unknown>
#12 0x7ff48d3817ed <unknown>
#13 0x7ff48d38300c <unknown>
#14 0x7ff48e279b8c <unknown>
#15 0x7ff48e27a1df <unknown>
#16 0x7ff48f4a6d24 <unknown>
#17 0x7ff48e278e75 <unknown>
#18 0x7ff48cd4b453 QtWebEngine::processMain()
#19 0x000000400bad main
#20 0x7ff488e8e830 __libc_start_main
#21 0x000000400c19 <unknown>
  r8: 00007ff489234770  r9: 00007ff49367b900 r10: 0000000000000008 r11: 0000000000000206
 r12: 00007ff489ad8140 r13: 00007ffcc13a5ee0 r14: 0000000000000053 r15: 00007ff489ad71c0
  di: 0000000000000003  si: 0000000000000003  bp: 00007ffcc13a5c80  bx: 00007ffcc13a6410
  dx: 0000000000000006  ax: 0000000000000000  cx: 00007ff488ea3428  sp: 00007ffcc13a5b48
  ip: 00007ff488ea3428 efl: 0000000000000206 cgf: 002b000000000033 erf: 0000000000000000
 trp: 0000000000000000 msk: 0000000000010000 cr2: 0000000000000000
[end of stack trace]
Calling _exit(1). Core file will not be generated.

Using ubuntu 16.04, haven’t had any problems until I updated today.

izk8 · September 13, 2018, 8:11pm

To fix, go to the link and get old 1.4.9 .deb image. cd to where it is downloaded and:

sudo dpkg -i insync_1.4.9.37127-xenial_amd64.deb

The devs should really check before pushing this into production for us if it just breaks like that. Little disappointed.

jonw · September 14, 2018, 2:30pm

Same issue on Linux Mint 19.0 running insync 1.5.1.37343. Downgraded to 1.4.9.37127-artful and all is fine.
Holding off on the upgrade until this issue is resolved.

cstoudt · September 14, 2018, 4:32am

Same issue on Linux Mint 17.3

Kurt_Ko · September 14, 2018, 4:36am

Hi!
Sorry for the inconvenience everyone!

Can you run sudo ldconfig -p | grep -i gl.so and send me the output?
Also are you using Nvidia drivers?

Thanks!

void75 · September 14, 2018, 4:38am

@Kurt_Ko

ldconfig -p | grep -i gl.so
libwayland-egl.so.1 (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libwayland-egl.so.1
libwayland-egl.so (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libwayland-egl.so
libQt5OpenGL.so.5 (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libQt5OpenGL.so.5
libQtOpenGL.so.4 (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libQtOpenGL.so.4
libQtOpenGL.so.4 (libc6) => /usr/lib/i386-linux-gnu/libQtOpenGL.so.4
libOpenGL.so.0 (libc6,x86-64) => /usr/lib/nvidia-396/libOpenGL.so.0
libOpenGL.so (libc6,x86-64) => /usr/lib/nvidia-396/libOpenGL.so
libGL.so.1 (libc6,x86-64) => /usr/lib/nvidia-396/libGL.so.1
libGL.so.1 (libc6) => /usr/lib32/nvidia-396/libGL.so.1
libGL.so (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libGL.so
libGL.so (libc6,x86-64) => /usr/lib/nvidia-396/libGL.so
libGL.so (libc6) => /usr/lib32/nvidia-396/libGL.so
libEGL.so.1 (libc6,x86-64) => /usr/lib/nvidia-396/libEGL.so.1
libEGL.so.1 (libc6) => /usr/lib32/nvidia-396/libEGL.so.1
libEGL.so (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libEGL.so
libEGL.so (libc6,x86-64) => /usr/lib/nvidia-396/libEGL.so
libEGL.so (libc6) => /usr/lib32/nvidia-396/libEGL.so

Yes, I am using nvidia drivers.

Kurt_Ko · September 14, 2018, 4:44am

Hi @void75!

If you can take a look at this

I think it’s an issue with your graphics libraries when you installed Nvidia drivers.

In your case, deleting /usr/lib/x86_64-linux-gnu/libGL.so and /usr/lib/x86_64-linux-gnu/libEGL.so should fix your issue.

Let me know if it works. Thanks!

void75 · September 14, 2018, 4:54am

@Kurt_Ko
Perfect. It was an old mesa relict Great work!

Kurt_Ko · September 14, 2018, 5:00am

@void75

Great to hear! Hope you enjoy using our new 1.5.1 version!

Kurt_Ko · September 14, 2018, 5:14am

Hi @Konstantin_Boyandin @izk8 @jonw @cstoudt

Can you run sudo ldconfig -p | grep -i gl.so and send me the output?

If you can take a look at this

It’s possibly an issue with old graphics libraries still on your system when you installed Nvidia drivers. I can help you find which ones to delete when you send me the output of the above command.

cstoudt · September 14, 2018, 11:32am

libwayland-egl.so.1 (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libwayland-egl.so.1
libvgagl.so.1 (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libvgagl.so.1
libcogl.so.15 (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libcogl.so.15
libQt5OpenGL.so.5 (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libQt5OpenGL.so.5
libQtOpenGL.so.4 (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libQtOpenGL.so.4
libQtOpenGL.so.4 (libc6) => /usr/lib/i386-linux-gnu/libQtOpenGL.so.4
libOpenGL.so.0 (libc6,x86-64) => /usr/lib/nvidia-384/libOpenGL.so.0
libOpenGL.so (libc6,x86-64) => /usr/lib/nvidia-384/libOpenGL.so
libGL.so.1 (libc6,x86-64) => /usr/lib/nvidia-384/libGL.so.1
libGL.so.1 (libc6) => /usr/lib32/nvidia-384/libGL.so.1
libGL.so (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libGL.so
libGL.so (libc6,x86-64) => /usr/lib/nvidia-384/libGL.so
libGL.so (libc6) => /usr/lib32/nvidia-384/libGL.so
libEGL.so.1 (libc6,x86-64) => /usr/lib/nvidia-384/libEGL.so.1
libEGL.so.1 (libc6) => /usr/lib32/nvidia-384/libEGL.so.1
libEGL.so (libc6,x86-64) => /usr/lib/nvidia-384/libEGL.so
libEGL.so (libc6) => /usr/lib32/nvidia-384/libEGL.so

Konstantin_Boyandin · September 14, 2018, 11:54am

Sure:

$ sudo ldconfig -p | grep -i gl.so
	libwayland-egl.so.1 (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libwayland-egl.so.1
	libwayland-egl.so.1 (libc6) => /usr/lib/i386-linux-gnu/libwayland-egl.so.1
	libwayland-egl.so (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libwayland-egl.so
	libcogl.so.20 (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libcogl.so.20
	libQt5OpenGL.so.5 (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libQt5OpenGL.so.5
	libQtOpenGL.so.4 (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libQtOpenGL.so.4
	libOpenGL.so.0 (libc6,x86-64) => /usr/lib/nvidia-384/libOpenGL.so.0
	libOpenGL.so (libc6,x86-64) => /usr/lib/nvidia-384/libOpenGL.so
	libGL.so.1 (libc6,x86-64) => /usr/lib/nvidia-384/libGL.so.1
	libGL.so.1 (libc6) => /usr/lib32/nvidia-384/libGL.so.1
	libGL.so (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libGL.so
	libGL.so (libc6,x86-64) => /usr/lib/nvidia-384/libGL.so
	libGL.so (libc6) => /usr/lib32/nvidia-384/libGL.so
	libEGL.so.1 (libc6,x86-64) => /usr/lib/nvidia-384/libEGL.so.1
	libEGL.so.1 (libc6) => /usr/lib32/nvidia-384/libEGL.so.1
	libEGL.so (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libEGL.so
	libEGL.so (libc6,x86-64) => /usr/lib/nvidia-384/libEGL.so
	libEGL.so (libc6) => /usr/lib32/nvidia-384/libEGL.so

cstoudt · September 14, 2018, 1:05pm

Is deleting old libraries such a good idea? How do we know there aren’t other applications that are still using them?

Just give me a link to insync_1.4.9.37343-trusty_amd64.deb

Arto_Jarvinen · September 14, 2018, 2:15pm

So I downgraded which worked fine (@cstoudt: the link is above in this thread). What is the general rule for which .so files to delete to fix the problem? Is the problem going to be fixed in insync? Thanks!

cstoudt · September 14, 2018, 2:19pm

Those are xenial .deb files. I need trusty.

jonw · September 14, 2018, 2:32pm

Here’s mine from a Mint 19 install.

libwayland-egl.so.1 (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libwayland-egl.so.1
libcogl.so.20 (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libcogl.so.20
libGL.so.1 (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libGL.so.1
libEGL.so.1 (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libEGL.so.1