Unable to log into External Account

Bugs and issues Linux
1

I recently installed insync on a new Arch Linux installation. My google account that uses insync requires an external site to manage the login. When I try to connect insync, it begins to load this external page, but receives a segmentation fault in the process. The log file is included below. I have been able to log into this account through insync before. I am currently using insync 1.2.18. I do not know what version I was using when it was successful

which: no kreadconfig in (/usr/lib/insync:/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl)
Fatal Python error: Segmentation fault

Thread 0x00007fadd3fff700:
  File "isyncd/linux/fswatch.py", line 278 in _pull_loop
  File "threading.py", line 763 in run
  File "threading.py", line 810 in __bootstrap_inner
  File "threading.py", line 783 in __bootstrap

Thread 0x00007fadd8c0b700:
  File "SocketServer.py", line 155 in _eintr_retry
  File "SocketServer.py", line 236 in serve_forever
  File "isyncd/linux/portable/unix_socket_server_portable.py", line 76 in __serve
  File "threading.py", line 763 in run
  File "threading.py", line 810 in __bootstrap_inner
  File "threading.py", line 783 in __bootstrap

Thread 0x00007fade63c0700:
  File "gevent/hub.py", line 179 in run

Current thread 0x00007fadf6c43700:
  File "__main__insync__.py", line 104 in main
  File "__main__insync__.py", line 159 in <module>
  File "__main__.py", line 128 in <module>
  File "<string>", line 6 in <module>
2

@mschoney Please try this build: http://s.insynchq.com/test_builds/insync_1.2.18.35201-trusty_amd64.deb

3

Thank you for your reply. I installed the 35201 release, but it didn’t fix it.

The most recent entry in the log file with the new version is included below:

usr/bin/vendor_perl:/usr/bin/core_perl)
Fatal Python error: Segmentation fault

Thread 0x00007f2fe0ed6700:
  File "isyncd/linux/fswatch.py", line 278 in _pull_loop
  File "threading.py", line 763 in run
  File "threading.py", line 810 in __bootstrap_inner
  File "threading.py", line 783 in __bootstrap

Thread 0x00007f2fe1717700:
  File "SocketServer.py", line 155 in _eintr_retry
  File "SocketServer.py", line 236 in serve_forever
  File "isyncd/linux/portable/unix_socket_server_portable.py", line 76 in __serve
  File "threading.py", line 763 in run
  File "threading.py", line 810 in __bootstrap_inner
  File "threading.py", line 783 in __bootstrap

Thread 0x00007f2feeed7700:
  File "gevent/hub.py", line 179 in run

Current thread 0x00007f2fff758700:
  File "__main__insync__.py", line 104 in main
  File "__main__insync__.py", line 159 in <module>
  File "__main__.py", line 128 in <module>
  File "<string>", line 6 in <module>
which: no kreadconfig in (/usr/lib/insync:/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl)
4

@mschoney I see. Could you test with other accounts and other Linux distributions (using VMs, for example)? Please also try running Insync through gdb to capture the backtrace when it crashes.

  • open a terminal
  • cd /usr/lib/insync
  • gdb --args ./insync start --no-daemon
  • in the gdb prompt, run “r”
  • when Insync crashes, run “bt” in the gdb prompt
  • send the output to us