Insync application not working after update to Ubuntu 18.04


#1

So recently I upgraded to Ubuntu 18.04 and I have been having problems with the Insync application ever since. The first thing to notice is that the system tray icon doesn’t work. At first it was not appearing at all, and after a bit of googling I found that this is due to Gnome not supporting system tray icons. I tried a couple of suggestions like installing TopIcons, with the result that an icon now appears at the top right corner, but it does not respond to clicking at all. Interestingly, a Chrome icon recently appeared which opens up a task manager when clicked, indicating that tray icons can be functional. To be honest, I don’t remember exactly what I did that got the icon to appear in the first place.

The biggest problem, however, is that Insync is simply not syncing my files. I still have access to my Google Drive folder in files, and it appears with the same special icon that it always does, with all my files in it, but it is not syncing any longer. After I boot, I get a message that Insync had to close, and I check the box to reload the application and send a report, but nothing happens. When I try to open Insync directly from Applications, nothing happens either.

I would really appreciate any advice on how to fix this.


#2

I’m not using Ubuntu 18.04 (I’m using Debian 9.6), but I recently experienced a similar issue to the one you are describing.

My particular issue wasn’t related to upgrading to a newer distribution version (i.e., Ubuntu 16.04 to Ubuntu 18.04), but rather to upgrading to a newer package version of Insync (1.5.4 to 1.5.5), which imagine happened when you upgraded your distribution version. For whatever reason, the Insync GUI crashed whenever I attempted to launch it on my machine. I could see this happening in the systray and in the terminal. And, like you, my drive folder was present on my machine but it wasn’t being synced.

I solved this temporarily by removing/purging Insync 1.5.5 and reinstalling Insync 1.5.4 via a .deb file available in the forums (https://forums.insynchq.com/t/new-insync-version-1-5-4/12724). I’ve instructed Synaptic and APT to hold version 1.5.4 until I hear some news about how others have solved this problem.


#3

Hi @silvascientist,

May I confirm if the installer is the artful build instead of xenial? Please also try to install the AppIndicator extension instead of TopIcons.

If the app still doesn’t run as expected, run insync quit && insync start --no-daemon and send the output here. Thank you!


#4

Hi @stwilkes,

This is a known issue and we have escalated this to our engineer for further investigation. Thank you for letting us know about the workaround, by the way. :slight_smile: Could you also run insync start --no-daemon and send the output here?


#5

Sure thing. And I apologize for the delay. Thanksgiving break means time away from my PhD program, and, consequently, time away from my PC.

Below is the output of “insync start --no-daemon” for Insync version 1.5.5. Please note that I modified the INFO line to obfuscate my personal information. If this information would be helpful to send in the clear, I would be more than happy to forward it privately:

/usr/lib/insync/isyncd.deskcore-0.0.0-py2.7.egg/ideskutils/gevent_init.py:47: UserWarning: libevent version mismatch: system version is ‘2.0.21-stable’ but this gevent is compiled against ‘2.0.22-stable’
INFO 2018-11-20 14:19:32,850 [main__insync:main:105] insync version: 1.5.5.37367
INFO 2018-11-20 14:19:32,852 [main__insync:main:106] client created <ideskmain.client.Client object at 0x7f249cd438d0>
INFO 2018-11-20 14:19:32,853 [unix_socket_server_portable:start:49] unix socket server thread start
INFO 2018-11-20 14:19:32,854 [main__insync:main:114] starting client
INFO 2018-11-20 14:19:32,859 [fswatch:_start:532] LinuxFSWatcher._start
INFO 2018-11-20 14:19:32,861 [fswatch:_pull_loop:267] Inotify loop enter
libpng warning: iCCP: known incorrect sRGB profile
[12189:12240:1120/141932.962448:ERROR:nss_util.cc(653)] Error initializing NSS with a persistent database (sql:/home/thomastavis/.pki/nssdb): libsoftokn3.so: cannot open shared object file: No such file or directory
[12189:12240:1120/141932.962531:ERROR:nss_util.cc(154)] Error initializing NSS without a persistent database: NSS error code: -5925
[12189:12240:1120/141932.962545:FATAL:nss_util.cc(156)] nss_error=-5925, os_error=0
#0 0x7f24a2da3c1f
#1 0x7f24a2dbf13c
#2 0x7f24a3629023
#3 0x7f24a36295d0
#4 0x7f24a362963c
#5 0x7f24a3552ade
#6 0x7f24a3552be9
#7 0x7f24a33e8f3f
#8 0x7f24a33ab2a1
#9 0x7f24a18285cd
#10 0x7f24a182a267
#11 0x7f24a182c621
#12 0x7f24a1ec6bf1
#13 0x7f24a230f8d1
#14 0x7f24a2da4329
#15 0x7f24a2dc5dd0
#16 0x7f24a2dc682d
#17 0x7f24a2dc6b17
#18 0x7f24a2dc8f71
#19 0x7f24a2de88bf
#20 0x7f24a1f1c33b
#21 0x7f24a1f1c7eb
#22 0x7f24a2e0c5c8
#23 0x7f24a2e07970
#24 0x7f24dc08d494 start_thread
#25 0x7f24db4aaacf clone

Received signal 6
#0 0x7f24a2da3c1f
#INFO 2018-11-20 14:19:32,987 [gdsyncer:sync_account:153] Syncing GDUser(id=u’’, email=u’S@g..edu’, name=u’S W*****’).
1 0x7f24a17cca9d
#2 0x7f24a2da412e
#3 0x7f24dc0970c0
#4 0x7f24db3f4fff gsignal
#5 0x7f24db3f642a abort
#6 0x7f24a2da2699
#7 0x7f24a2dbf28f
#8 0x7f24a3629023
#9 0x7f24a36295d0
#10 0x7f24a362963c
#11 0x7f24a3552ade
#12 0x7f24a3552be9
#13 0x7f24a33e8f3f
#14 0x7f24a33ab2a1
#15 0x7f24a18285cd
#16 0x7f24a182a267
#17 0x7f24a182c621
#18 0x7f24a1ec6bf1
#19 0x7f24a230f8d1
#20 0x7f24a2da4329
#21 0x7f24a2dc5dd0
#22 0x7f24a2dc682d
#23 0x7f24a2dc6b17
#24 0x7f24a2dc8f71
#25 0x7f24a2de88bf
#26 0x7f24a1f1c33b
#27 0x7f24a1f1c7eb
#28 0x7f24a2e0c5c8
#29 0x7f24a2e07970
#30 0x7f24dc08d494 start_thread
#31 0x7f24db4aaacf clone
r8: 0000000000000000 r9: 00007f24597f8950 r10: 0000000000000008 r11: 0000000000000246
r12: 00007f24d537efa0 r13: 00007f24597f8df0 r14: 0000000000000053 r15: 00007f24d537e060
di: 0000000000000002 si: 00007f24597f8950 bp: 00007f24597f8b90 bx: 0000000000000006
dx: 0000000000000000 ax: 0000000000000000 cx: 00007f24db3f4fff sp: 00007f24597f89c8
ip: 00007f24db3f4fff efl: 0000000000000246 cgf: 002b000000000033 erf: 0000000000000000
trp: 0000000000000000 msk: 0000000000000000 cr2: 0000000000000000
[end of stack trace]
Calling _exit(1). Core file will not be generated.
[12248:12248:0100/000000.008253:ERROR:broker_posix.cc(43)] Invalid node channel message


#6

Thank you for this. :slight_smile:

Could you please run sudo apt-get update && sudo apt-get install insync or re-download the installer from our downloads?

Let me know if this works. Thank you so much for your patience and happy Thanksgiving!


#7

@miamoran The problem that I’ve been experiencing seems to have been fixed. Thank you, and a happy Thanksgiving to you as well.