I too have managed to get an insync-headless session up and running, but I’m getting strange updates as it tries to sync, and a target directory name change doesn’t seem to have been taken well
It seems to build the file structure on the target drive, but no actual files are syncing. This is the part that seems … less promising?
:~$ insync-headless start --no-daemon & :~$ Qt WebEngine seems to be initialized from a plugin. Please set Qt::AA_ShareOpenGLContext using QCoreApplication::setAttribute before constructing QGuiApplication. INFO 2018-12-10 18:31:56,523 [__main__insync__:main:105] insync version: 22.214.171.124368 INFO 2018-12-10 18:31:56,524 [__main__insync__:main:106] client created <ideskmain.client.Client object at 0x7f8ff0813bd0> INFO 2018-12-10 18:31:56,525 [unix_socket_server_portable:start:49] unix socket server thread start INFO 2018-12-10 18:31:56,525 [__main__insync__:main:114] starting client INFO 2018-12-10 18:31:56,531 [fswatch:_start:532] LinuxFSWatcher._start INFO 2018-12-10 18:31:56,532 [fswatch:_pull_loop:267] Inotify loop enter INFO 2018-12-10 18:31:56,543 [gdsyncer:sync_account:153] Syncing GDUser(id=u'*************', email@example.com', name=u'*********'). INFO 2018-12-10 18:31:56,705 [fsstate:setup:167] There are no existing trees. INFO 2018-12-10 18:31:56,842 [client:__on_gd_account_added:891] GDUser(id=u'100746353429552130553', firstname.lastname@example.org', name=u'*****') (existing) is now being synced. INFO 2018-12-10 18:31:57,035 [fsworks:__process_main_tree:221] Main syncing location for u'**********' becomes missing. INFO 2018-12-10 18:32:56,865 [_updater:_run:129] No updater available.