Version 1.3.6 crashes on startup


I performed the update from version 1.3.5 to 1.3.6. The prior version performed properly. The new version ( fails to start. There is a momentary flash of the icon on the panel bar and no error is returned.

Starting in no-daemon mode reveals the following

$ insync start --no-daemon
Fontconfig error: “/etc/fonts/conf.d/10-scale-bitmap-fonts.conf”, line 70: non-double matrix element
Fontconfig error: “/etc/fonts/conf.d/10-scale-bitmap-fonts.conf”, line 70: non-double matrix element
Fontconfig warning: “/etc/fonts/conf.d/10-scale-bitmap-fonts.conf”, line 78: saw unknown, expected number
INFO 2016-02-23 16:02:27,788 [init:info:1610] insync version:
INFO 2016-02-23 16:02:27,789 [init:info:1610] client created <ideskmain.client.Client object at 0x5388250>
INFO 2016-02-23 16:02:27,790 [init:info:1610] unix socket server thread start
INFO 2016-02-23 16:02:27,790 [init:info:1610] starting client
INFO 2016-02-23 16:02:27,795 [init:info:1610] LinuxFSWatcher._start
INFO 2016-02-23 16:02:27,796 [init:info:1610] Inotify loop enter
Cannot mix incompatible Qt library (version 0x40806) with this library (version 0x40802)
Fatal Python error: Aborted

Thread 0x00007f2815af5700:
File “”, line 244 in wait
File “”, line 404 in wait
File “isyncd/linux/”, line 47 in invoke_in_qt_thread
File “isyncd/linux/”, line 58 in wrapper
File “isyncd/linux/”, line 10 in _init
File “ideskui/”, line 25 in init
File “ideskui/”, line 29 in init
File “isyncd/linux/”, line 162 in create_app_dialog
File “ideskutils/”, line 92 in wrapper
File “”, line 505 in run
File “”, line 552 in __bootstrap_inner
File “”, line 525 in __bootstrap

Thread 0x00007f2816bf8700:
File “isyncd/linux/”, line 278 in _pull_loop
File “”, line 505 in run
File “”, line 552 in __bootstrap_inner
File “”, line 525 in __bootstrap

Thread 0x00007f28173f9700:
File “”, line 155 in _eintr_retry
File “”, line 236 in serve_forever
File “isyncd/linux/portable/”, line 76 in __serve
File “”, line 505 in run
File “”, line 552 in __bootstrap_inner
File “”, line 525 in __bootstrap

Thread 0x00007f28224e1700:
File “gevent/”, line 179 in run

Current thread 0x00007f2836e7e700:
File “isyncd/linux/”, line 175 in init
File “isyncd/linux/”, line 208 in init
File “isyncd/linux/”, line 230 in init
File “isyncd/linux/”, line 136 in create_window
File “isyncd/linux/”, line 40 in wrapper
File “isyncd/linux/”, line 25 in event
File “”, line 103 in main
File “”, line 166 in
File “”, line 128 in
File “”, line 6 in

There appears to be a new QT library incompatibility in the new version

The new version of Insync is

apt-cache showpkg insync

Package: insync
Versions: (/var/lib/apt/lists/apt.insynchq.com_debian_dists_jessie_non-free_binary-amd64_Packages) (/var/lib/dpkg/status)
Description Language:
File: /var/lib/apt/lists/apt.insynchq.com_debian_dists_jessie_non-free_binary-amd64_Packages
MD5: 1ad68f871ddf79784846aac96436e9ce

Reverse Depends:
Dependencies: - xdg-utils (0 (null)) libc6 (2 2.13) python (0 (null)) insync-beta (0 (null)) insync-beta:i386 (0 (null)) insync-headless (0 (null)) insync-headless:i386 (0 (null)) insync (0 (null)) insync:i386 (0 (null)) insync:i386 (0 (null))
Provides: -
Reverse Provides:

System is Linux Mint Debian Edition V1, which is Debian Jessie with some Mint extensions but is fully Debian compliant:

uname -a

Linux xxx 3.11-2-amd64 #1 SMP Debian 3.11.8-1 (2013-11-13) x86_64 GNU/Linux

Where can I obtain the prior version (1.3.5) until the new version is fixed?



Just Google “insync 1.3.5”.

You’ll find it pretty easily :slight_smile:

In case you’re lazy here’s a link :




Just incase this doesn’t work, I’ll be tagging our engineer @lpugoy and he will get back to you.

For reference, all previous versions of Insync are also here in the forums :smile:


@Philip_Crichton: Apologies for the trouble. There was an issue with the Debian builds for 1.3.6. Version 1.3.7 for Debian has been uploaded. The download links in New Insync version: 1.3.6 has been updated. The update has also been pushed to the Debian repos.


Thank you. I loaded the 1.3.7 version and it seems to be running properly. As you are aware, it was the graphic “head” that had the problem but the engine ran fine in headless mode.

Thank you for your quick response.