Arch Linux User Repository

Could you update this package, please?

Hmm. That doesn't look like it was the answer. I haven't tried running it in a chroot container so that may be an option but I'm not sure how much difference it'll make since I'm on a pretty clean install as it is.

@thenaterhood this looks like some mismatch libs error. Do you have qt5 installed on your system? if so then remove it and try to run without it or start insync in a chroot container with x11 forwarding.
Another solution that might help is to run with env LD_LIBRARY_PATH=/usr/lib/insync insync start

Sorry for the delay, my hard drive died yesterday so I'm getting back in working order. I'm having trouble getting insync to work at the moment, seemingly unrelated to the latest updates. Tracking that down.

Gtk-Message: 23:50:59.326: Failed to load module "canberra-gtk-module"
Gtk-Message: 23:50:59.326: Failed to load module "canberra-gtk-module"
QXcbIntegration: Cannot create platform OpenGL context, neither GLX nor EGL are enabled
libpng warning: iCCP: known incorrect sRGB profile
INFO     2020-09-12 23:50:59,578 [mainlogs:_log_run:122] Core(app_version=3.2.7.40868, platform=Linux-x86_64-arch/) initialized
WARNING  2020-09-12 23:50:59,587 [base_events:_run_once:1771] Executing <Task pending coro=<init() running at ideskcore/core.py:146> wait_for=<Task pending coro=<SettingsMain._load_settings() running at ideskcore/mainsettings.py:169> cb=[_log_tb_after_delay() at ideskasync/coreloop.py:303, <TaskWakeupMethWrapper object at 0x7fde141e2768>()] created at ideskcore/mainsettings.py:147> cb=[_log_tb_after_delay() at ideskasync/coreloop.py:303, _chain_future.<locals>._call_set_state() at asyncio/futures.py:355] created at asyncio/events.py:88> took 0.130 seconds
INFO     2020-09-12 23:50:59,748 [fswatcher:_start:57] LinuxFSWatcher._start
INFO     2020-09-12 23:50:59,748 [inotify_manager:_pull_loop:312] Inotify loop enter
WebEngineContext used before QtWebEngine::initialize() or OpenGL context creation failed.
/usr/lib/insync/QtWebEngineProcess --type=zygote --webengine-schemes=qrc:sLV --lang=en-US: symbol lookup error: /usr/lib/insync/QtWebEngineProcess --type=zygote --webengine-schemes=qrc:sLV --lang=en-US: undefined symbol: _ZN7content20localtime_r_overrideEPKlP2tm, version Qt_5

Sweet. Thanks for the heads up on that. And thanks for the PKGBUILD, you did all the hard work :)

@thenaterhood it might be a good idea to remove /usr/lib/insync/libGL{X,dispatch}.so* from the package. These are already supplied by libglvnd and might cause the app to crash if it tries to use the EGL Wayland backend. edit: also /usr/lib/insync/libdrm.so* should be removed.

edit: here the suggested changes, this works fine for Wayland software rendering but the EGL backend still doesn't work while it is working in a container environment (Flatpak), I'm not sure why.

diff --git a/PKGBUILD b/PKGBUILD
index b1380a3..330feaf 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -6,7 +6,7 @@
 # Source : new application - https://forums.insynchq.com

 pkgname=insync
-pkgver=3.2.6.40863
+pkgver=3.2.7.40868
 pkgrel=1
 _dist=buster
 pkgdesc="An unofficial Google Drive and OneDrive client that runs on Linux, with support for various desktops"
@@ -26,7 +26,7 @@ arch=('x86_64')
 source=("http://s.insynchq.com/builds/${pkgname}_${pkgver}-${_dist}_amd64.deb"
     'insync@.service'
     'insync.service')
-sha256sums=('1f83007e6c1aed6fdeaccd4e45eb39eef70d12911c193b9e5e189b8c2428d705'
+sha256sums=('ffe77e73e6b62bed27312495b3955921ca6801f16bd9b489dcfc38aa4015e6a7'
             'cf276c1dbf1592ea63a21c2d61c75f7ad6ec3b13e87b3aaa331e9c14799f4598'
             '1432141539a6b3c5333631a2ee6696fab9bd2fe8770643bc670d95e4e96203e0')
 package() {
@@ -36,4 +36,5 @@ package() {
    install -Dm644 insync.service ${pkgdir}/usr/lib/systemd/user/insync.service
    install -dm755  ${pkgdir}/usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0
    ln -s /usr/lib/gdk-pixbuf-2.0/2.10.0/loaders.cache ${pkgdir}/usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache
+   rm ${pkgdir}/usr/lib/insync/lib{drm,GLX,GLdispatch}.so*

Heads up, latest 3.2.7 release finally includes Qt5 Wayland shell integration plugins but the app still doesn't load when start as a Wayland client, so QT_QPA_PLATFORM=xcb should still be used.

edit: actually it works perfectly as a Wayland client on my Arch Linux host, it didn't work correcly in a container, strace showing some memory allocation issue.

@tinywrkb: I'm subscribed to the insync discourse releases topic. I usually try not to pick up releases immediately because there have been a few that have been pulled.

Feel free to give me a nudge or mark the package out of date if you think I'm running behind - it does happen.

@thenaterhood, how are you following releases? you seem to be missing out on updates.
This is what I'm doing:

1. On the Insync Discourse I set Watching first post on the Releases topic.

2. I have the following in urlwatcher's urls.yaml

name: "pkg/insync: release at insynchq forums"
url: "https://forums.insynchq.com/c/releases/15"
filter:
  - element-by-class: topic-list-item
  - grep: 'New Insync version'
  - html2text: re
  - re.sub: '.*: '
  - sort: re
---
name: "pkg/insync: debian buster repo"
url: "http://apt.insync.io/debian/dists/buster/non-free/binary-amd64/Packages"
ignore_cached: true
filter:
  - grep: 'Version'
---

p.s. Forgot to mention that the last one (apt repo) doesn't always work correctly due to the fact Last-Modified in the response HTTP header is not always updates on content change so urlwatcher just skip over it.

@biwhite, try to set QT_QPA_PLATFORM as an environment variable. You can also drop your own insync.desktop file with an updated Exec into $XDG_DATA_HOME/applications.

I'm no longer using this AUR package in favor of my own Flatpak but during a little investigation I noticed I can throw away most of the embedded shared libs in favor of system libs, and insync would still work perfectly fine.
IIRC I only had to keep the python, icu, shiboken2, curl libs, and the for rest I used systems libs, include qt5webengine. But I've done it with a Flatpak runtime not with Arch libs.
As this issue might be related to out-of-date QT libs then it probably worth trying to run insync with system libs instead of the embedded ones.