Package Details: insync 3.9.6.60027-2

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.60
First Submitted: 2012-09-07 17:45 (UTC)
Last Updated: 2025-05-19 12:22 (UTC)

Latest Comments

« First ‹ Previous 1 .. 20 21 22 23 24 25 26 27 28 29 30 .. 66 Next › Last »

thenaterhood commented on 2019-08-03 01:36 (UTC)

@taflaj awesome! glad to hear it!

@soundscape that's very strange.

taflaj commented on 2019-08-02 02:27 (UTC)

@thenaterhood Today I got the update. Installed it without any issues. Insync is working fine. Thank you!

soundscape commented on 2019-08-01 12:03 (UTC) (edited on 2019-08-02 10:46 (UTC) by soundscape)

Build 1.5.7-3 is crashing with coredump:

/#18 0x0000560acd7a4807 n/a (insync)

/#19 0x0000560acd78f2e6 PyObject_Call (insync)

/#20 0x0000560acd796b66 n/a (insync)

/#21 0x0000560acd78f2e6 PyObject_Call (insync)

/#22 0x0000560acd7490cd PyEval_CallObjectWithKeywords (insync)

/#23 0x00007f8f88754509 n/a (greenlet.so)

/#24 0x00007f8f887547af n/a (greenlet.so)

/#25 0x0000560acdb39d80 _Py_NotImplementedStruct (insync)

Fresh build & install.

Edit: Seems to only crash with the GUI open, possibly only during a sync. Sync with the GUI closed seems to run fine.

thenaterhood commented on 2019-08-01 02:31 (UTC)

Cool, okay. I tried removing /usr/lib/insync/libstdc++.so.6 and that was fine on my end too. If that's the official suggestion, then seems like updating the PKGBUILD to do the same is the right thing for now.

taflaj commented on 2019-07-31 15:07 (UTC) (edited on 2019-07-31 15:10 (UTC) by taflaj)

I did do a fresh install, and the problem remained.

Today I got an update from the vendor. They suggested I remove /usr/lib/insync/libstdc++.so.6, which I did, and then it started working flawlessly. @thenaterhood this may be the key to it.

thenaterhood commented on 2019-07-31 02:39 (UTC)

My system is upgraded to the latest and greatest, and I've tried re-building and re-installing insync, but it's working fine for me (...of course, right?). I'm running (regular) mesa and not even seeing the mesa problem. I'll double check that the fix from @testbird71 doesn't break anything on my end, and I'm more than happy to add it.

For those having issues with segfaults or insync not starting, have you tried rebuilding the package and reinstalling?

thenaterhood commented on 2019-07-30 11:55 (UTC)

Howdy folks - apologies for the delay. I've been reading comments, but I have not had a chance to investigate.

taflaj commented on 2019-07-30 06:46 (UTC)

Here's what Insynchq Pte. Ltd. responded when I reported the problem to them: "This is currently out of our control since Insync's Arch builds are maintained by the AUR. With that, we highly recommend users to contact the package maintainer or the AUR regarding this."

taflaj commented on 2019-07-30 04:44 (UTC)

Using Manjaro with kernel 5.2.2-1-MANJARO. After the latest upgrades insync stopped running. When I try to run it manually, it quits without even an error message.

Any help is greatly appreciated.

ArthurBorsboom commented on 2019-07-29 07:48 (UTC)

dmesg (after package upgrades?):

insync[10274]: segfault at 68 ip 00007f41a32eb2b4 sp 00007ffe7162db60 error 4 in ld-2.29.so[7f41a32e0000+1f000]

« First ‹ Previous 1 .. 20 21 22 23 24 25 26 27 28 29 30 .. 66 Next › Last »