Package Details: insync 3.9.10.60041-1

Git Clone URL: https://aur.archlinux.org/insync.git (read-only, click to copy)
Package Base: insync
Description: An unofficial Dropbox, Google Drive, and OneDrive client that runs on Linux, with support for various desktops
Upstream URL: https://www.insynchq.com/downloads
Keywords: drive dropbox google onedrive
Licenses: custom:insync
Submitter: xzy3186
Maintainer: thenaterhood
Last Packager: thenaterhood
Votes: 323
Popularity: 0.050692
First Submitted: 2012-09-07 17:45 (UTC)
Last Updated: 2026-05-03 16:19 (UTC)

Latest Comments

« First ‹ Previous 1 .. 7 8 9 10 11 12 13 14 15 16 17 .. 66 Next › Last »

guiodic commented on 2021-07-22 10:13 (UTC)

error: could not open file /var/lib/pacman/local/insync-3.4.3.40990-2/desc: No such file or directory

gadicc commented on 2021-07-15 16:04 (UTC)

@thenaterhood! Massive thanks! The patches you integrated finally fixed issues I've been having since upgrading to GNOME 40 / Wayland. Note: wasn't trying to change my sync dir, maybe I did a long time ago. Further info for others at https://forums.insynchq.com/t/insync-not-working-on-gnome-40-with-workaround/17149.

thenaterhood commented on 2021-07-13 12:13 (UTC)

I've integrated patches for the sync dir crash from two threads on the insync forums:

+   echo "-> Patching https://forums.insynchq.com/t/crash-when-changing-sync-folders-linux-with-solution/17254/4"
+   mv ${pkgdir}/usr/lib/insync/libgdk_pixbuf-2.0.so.0{,.bak}
+   echo "-> Patching https://forums.insynchq.com/t/crash-changing-sync-directory-with-fix/17364/10"
+   mv ${pkgdir}/usr/lib/insync/libpangoft2-1.0.so.0{,.bak}

If that causes problems, feel free to restore one or both of those libs and comment here and/or in the insync forums.

dgimortal commented on 2021-07-10 01:43 (UTC)

mbcooper this work! Good Job, i recommend to the package maintainer to insert this command in upcoming package updates.

mbcooper commented on 2021-07-09 11:11 (UTC)

Re: Insync crashing when changing the base directory.

I found this workaround from rooting around in the insync support forums. run this command and you will be able to change the basedir. (looks like an incompatibility with some library)

sudo mv /usr/lib/insync/libgdk_pixbuf-2.0.so.0{,.bak}


Actually this is what I did. I had quite some support help from Mia freom Insynq and this is what actually helped: sudo mv /usr/lib/insync/libgdk_pixbuf-2.0.so.0{,.bak}

So it looks like a dependency issue between the libraries/packages coming with insync and newer versions of some libraries in arch linux.


thenaterhood commented on 2021-06-17 22:06 (UTC)

Hey folks, I'm tracking discussion of the issue of insync crashing when changing sync directory over on the insync forums at https://forums.insynchq.com/t/crash-changing-sync-directory/17364.

I'll update the PKGBUILD if something actionable comes up. Until then, if you're seeing that issue I encourage you to take a look at the ongoing discussion.

fabwu commented on 2021-06-14 07:33 (UTC) (edited on 2021-06-14 07:35 (UTC) by fabwu)

I can't get insync to autostart with systemd on my laptop with Gnome 40. Does anybody has the same problem or a fix?

Here's the error message:

#0  0x00007f6e9584ed22 raise (libc.so.6 + 0x3cd22)
#1  0x00007f6e95838862 abort (libc.so.6 + 0x26862)
#2  0x00007f6e8cec1e2c _ZNK14QMessageLogger5fatalEPKcz (libQt5Core.so.5 + 0x85e2c)
#3  0x00007f6e8d7126c8 _ZN22QGuiApplicationPrivate25createPlatformIntegrationEv (libQt5Gui.so.5 + 0x1436c8)
#4  0x00007f6e8d7129dd _ZN22QGuiApplicationPrivate21createEventDispatcherEv (libQt5Gui.so.5 + 0x1439dd)
#5  0x00007f6e8d0b62ff _ZN23QCoreApplicationPrivate4initEv (libQt5Core.so.5 + 0x27a2ff)
#6  0x00007f6e8d71430b _ZN22QGuiApplicationPrivate4initEv (libQt5Gui.so.5 + 0x14530b)
#7  0x00007f6e8df5d1d9 _ZN19QApplicationPrivate4initEv (libQt5Widgets.so.5 + 0x1651d9)
#8  0x00007f6e8ea0e984 Sbk_QApplication_Init (QtWidgets.abi3.so + 0x18b984)
#9  0x00007f6e955c3ae2 type_call (libpython3.7m.so.1.0 + 0xe9ae2)
#10 0x00007f6e9556d7d3 _PyObject_FastCallKeywords (libpython3.7m.so.1.0 + 0x937d3)
#11 0x00007f6e95546b1b call_function (libpython3.7m.so.1.0 + 0x6cb1b)
#12 0x00007f6e955414db function_code_fastcall (libpython3.7m.so.1.0 + 0x674db)
#13 0x00007f6e95549e61 call_function (libpython3.7m.so.1.0 + 0x6fe61)
#14 0x00007f6e955414db function_code_fastcall (libpython3.7m.so.1.0 + 0x674db)
#15 0x00007f6e9554adf9 call_function (libpython3.7m.so.1.0 + 0x70df9)
#16 0x00007f6e9564288e _PyEval_EvalCodeWithName (libpython3.7m.so.1.0 + 0x16888e)
#17 0x00007f6e9556cf3b _PyFunction_FastCallDict (libpython3.7m.so.1.0 + 0x92f3b)
#18 0x00007f6e95545cbd do_call_core (libpython3.7m.so.1.0 + 0x6bcbd)
#19 0x00007f6e9564288e _PyEval_EvalCodeWithName (libpython3.7m.so.1.0 + 0x16888e)
#20 0x00007f6e9556cf3b _PyFunction_FastCallDict (libpython3.7m.so.1.0 + 0x92f3b)
#21 0x00007f6e9556e0fd _PyObject_Call_Prepend (libpython3.7m.so.1.0 + 0x940fd)
#22 0x00007f6e9556f305 PyObject_Call (libpython3.7m.so.1.0 + 0x95305)
#23 0x00007f6e95545cbd do_call_core (libpython3.7m.so.1.0 + 0x6bcbd)
#24 0x00007f6e955414db function_code_fastcall (libpython3.7m.so.1.0 + 0x674db)
#25 0x00007f6e95549e61 call_function (libpython3.7m.so.1.0 + 0x6fe61)
#26 0x00007f6e9564288e _PyEval_EvalCodeWithName (libpython3.7m.so.1.0 + 0x16888e)
#27 0x00007f6e9556d0f3 _PyFunction_FastCallKeywords (libpython3.7m.so.1.0 + 0x930f3)
#28 0x00007f6e95549e61 call_function (libpython3.7m.so.1.0 + 0x6fe61)
#29 0x00007f6e9564288e _PyEval_EvalCodeWithName (libpython3.7m.so.1.0 + 0x16888e)
#30 0x00007f6e9556cf3b _PyFunction_FastCallDict (libpython3.7m.so.1.0 + 0x92f3b)
#31 0x00007f6e9556e0fd _PyObject_Call_Prepend (libpython3.7m.so.1.0 + 0x940fd)
#32 0x00007f6e9556f305 PyObject_Call (libpython3.7m.so.1.0 + 0x95305)
#33 0x00007f6e95545cbd do_call_core (libpython3.7m.so.1.0 + 0x6bcbd)
#34 0x00007f6e9564288e _PyEval_EvalCodeWithName (libpython3.7m.so.1.0 + 0x16888e)
#35 0x00007f6e9556cf3b _PyFunction_FastCallDict (libpython3.7m.so.1.0 + 0x92f3b)
#36 0x00007f6e9556e0fd _PyObject_Call_Prepend (libpython3.7m.so.1.0 + 0x940fd)
#37 0x00007f6e955cbea5 slot_tp_call (libpython3.7m.so.1.0 + 0xf1ea5)
#38 0x00007f6e9556d7d3 _PyObject_FastCallKeywords (libpython3.7m.so.1.0 + 0x937d3)
#39 0x00007f6e95545e17 call_function (libpython3.7m.so.1.0 + 0x6be17)
#40 0x00007f6e9564288e _PyEval_EvalCodeWithName (libpython3.7m.so.1.0 + 0x16888e)
#41 0x00007f6e95642b0e PyEval_EvalCodeEx (libpython3.7m.so.1.0 + 0x168b0e)
#42 0x00007f6e95642b3b PyEval_EvalCode (libpython3.7m.so.1.0 + 0x168b3b)
#43 0x0000000000402ca1 n/a (insync + 0x2ca1)
#44 0x0000000000403087 n/a (insync + 0x3087)
#45 0x00007f6e95839b25 __libc_start_main (libc.so.6 + 0x27b25)
#46 0x0000000000401a9e n/a (insync + 0x1a9e)

atescula commented on 2021-05-25 10:42 (UTC)

Apologies for the previous comment. I am in a hotel where they ban some stuff. Updated remotely my home computer. Everything works fine as expected.

atescula commented on 2021-05-25 05:09 (UTC)

Not able to upgrade due to negative passing the validity check

JustinSB commented on 2021-05-24 10:44 (UTC)

For the record, as a workaround you can edit the path in the Sqlite database. The database is ~/.config/Insync/data/gd-***.db and the path is the 1st entry in fs_items. I just used sqlitebrowser, but you have to remember to exit insync before you edit it.