I’m not sure on which release you started linking against gvfs and glib-networking libs but now that you do you really need to include those in the release tarball the same way you’re doing with other libs, that’s because users have been using your releases on other distros than intended (e.g. Arch Linux) and you’re linking against specific lib versions that are may or may not available in the user’s distro.
/usr/lib/x86_64-linux-gnu/gio/modules/libgiognomeproxy.so: undefined symbol: g_task_set_name
Failed to load module: /usr/lib/x86_64-linux-gnu/gio/modules/libgiognomeproxy.so
/usr/lib/x86_64-linux-gnu/gio/modules/libgiognutls.so: undefined symbol: g_task_set_name
Failed to load module: /usr/lib/x86_64-linux-gnu/gio/modules/libgiognutls.so
/usr/lib/x86_64-linux-gnu/gio/modules/libgiolibproxy.so: undefined symbol: g_task_set_name
Failed to load module: /usr/lib/x86_64-linux-gnu/gio/modules/libgiolibproxy.so
/usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so: undefined symbol: g_date_time_format_iso8601
Failed to load module: /usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so
Another issue that I noticed is that you’re not including the qt5-wayland shell integration plugins. For example, there’s no libxdg-shell-v6.so in PySide2/plugins. This means Insync can’t run as a native Wayland client and I need to force it to run through XWayland with QT_QPA_PLATFORM=xcb.
Also, can you give further details about this?
Linux: Improve checks for whether Insync is running
Are you still only using the Unix socket in /tmp for that? what about registering DBus name?
On Fedora 32 I have to force a rescan to get anything to sync, as it doesn’t detect changes by itself. This has been happening since at least 3.2.3 if not earlier and I reported it at the time.
Hey all-- can you send your logs.db and out.txt files to support@insynchq.com with the link to this post? We need to look into what’s causing Insync to re-scan/re-sync after you updated your version.
I just had an instance of an unnecessary apparent fulls re-scan. I logged out and logged back in for unrelated reasons and found Insync apparently doing a full re-scan. I didn’t wait for it to finish before zipping up the logs. Hopefully, that’s fine. If you require end of scan logs, too, I can try and provide those as well.