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 .. 36 37 38 39 40 41 42 43 44 45 46 .. 66 Next › Last »

uke-eda commented on 2013-11-02 22:16 (UTC)

Hello there. I get /usr/bin/insync: line 3: 22645 Segmentation fault (core dumped) LC_TIME=C ./insync "$@" when I try to run insync. Any suggestions what this means?

orschiro commented on 2013-10-23 06:02 (UTC)

@colinkeenan The idea for a systemd service file was taken from Dropbox. Have you ever looked into their service file? As for Dropbox I have nobody seen complaining about it. Apparently it does its job well.

colinkeenan commented on 2013-10-23 03:52 (UTC)

Never mind my previous comment. On repeated reboots, systemd refused to start Insync in XFCE no matter what I do. Clearly, simply putting a check in the box to start Insync on startup from the Insync preferences menu is the easiest and most reliable way to handle this and the wiki needs to be updated. I don't think a systemd service file should even be included anymore.

colinkeenan commented on 2013-10-23 03:41 (UTC)

I removed the '...sleep 60' from /usr/lib/systemd/system/insync@.service again and followed the advice on : systemctl enable NetworkManager-wait-online.service I removed the checkmark in the insync preferences to start on boot and sudo systemctl enable insync@colin But, it still didn't work. In fact, it never started (or at least the icon never showed up). I discovered my problem is probably specific to XFCE because what finally solved the issue was the following while insync was running: Settings -> Session and Startup -> Session, find insync.py and in the far column left-click on 'if running' and choose 'never'. This makes sure XFCE doesn't try to restart insync.py, thus allowing systemd to do what it's supposed to do. The insync.py program can be running even when you exit Insync. I think XFCE was restoring insync.py without the icon for Insync showing and that prevented systemd from starting Insync properly. Of course, all of this begs the question. Why use systemd for starting Insync anyway? I'm doing it because that's what the wiki says. The wiki is out of date though.

colinkeenan commented on 2013-10-23 03:05 (UTC)

I decided to read the official systemd info at http://www.freedesktop.org and found this page specifically about the network.target not working: http://www.freedesktop.org/wiki/Software/systemd/NetworkTarget/. I couldn't believe the following information at the end of the first section: "In systemd network.target by default does not have much meaning...By defaulting to the empty meaning we hence provide a speedy boot that is not slowed down by external factors for the majority of cases, but by allowing network.target to be defined by the administrator as he likes any policy is implementable instead." This explains why starting after network.target isn't working for us. We also have to give network.target some meaning. The next section is appropriately titled: "Cut the crap! How do I make network.target work for me?". I'm about to read it and suggest others interested in systemd read it as well.

colinkeenan commented on 2013-10-15 07:26 (UTC)

I've decided to give up on systemd for starting insync. The more reliable way is to just checkmark 'Start Insync when computer starts' in the preferences menu. I may follow up in the forums to work out if there's a better file to use for systemd with insync or if there's a bug, but not right now.

xzy3186 commented on 2013-10-15 01:19 (UTC)

Updated to 1.0.24 @colinkeenan,orschiro Since no conclusion has been made yet, I re-add 'ExecStartPre=/usr/bin/sleep 60' back to the service file temporally to make it work.

orschiro commented on 2013-10-14 19:58 (UTC)

@colinkeenan Have you already asked on the forums for help? I find this quite an interesting issue to investigate. Maybe it is a bug within systemd?

« First ‹ Previous 1 .. 36 37 38 39 40 41 42 43 44 45 46 .. 66 Next › Last »