Package Details: insync 3.9.4.60020-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: 321
Popularity: 1.36
First Submitted: 2012-09-07 17:45 (UTC)
Last Updated: 2024-08-11 22:53 (UTC)

Latest Comments

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

orschiro commented on 2013-10-05 11:27 (UTC)

@xzy3186 Together with cilnkeenan we investigated the issue. Can you please update the Insync.service file to reflect the following changes? [Unit] Description=Insync After=local-fs.target network.target [Service] - ExecStartPre=/usr/bin/sleep 60 Environment=DISPLAY=:0 Type=simple ExecStart=/usr/bin/insync_OPTION ExecReload=/bin/kill -HUP $MAINPID KillMode=process - Restart=always + Restart=never User=%I [Install] WantedBy=multi-user.target

colinkeenan commented on 2013-10-04 19:21 (UTC)

Thanks for following up on my investigation of the systemd issue. I forgot to update my system since then or check these comments. Just updated and I have the constantly restarting problem again. So, I changed 'always' to 'never' again on the 'Restart=' line of /usr/lib/systemd/system/insync@.service. I guess I'll followup with orschiro about fixing that in the official file.

orschiro commented on 2013-09-25 11:56 (UTC)

@xzy3186 So far it is still working with my dispatcher package as long as we still allow the service to be run as a user. I think it is safe to include it in the update.

xzy3186 commented on 2013-09-25 01:14 (UTC)

@orschiro I just want to confirm if your package can work properly with the modified service file. If no problem occur, I will include new service file by colinkeenan in the next update.

orschiro commented on 2013-09-23 05:55 (UTC)

@xzy3186 My dispatcher package does not provide the service file anymore and I think it is wise to leave the service file with the original package instead of distributing it in the dispatcher. Thus, can you please include the modified service file in your package? Thanks

xzy3186 commented on 2013-09-21 12:44 (UTC)

@colinkeenan Thanks for your feedback and investigation. To be honest, I am running gnome desktop and the autostart for insync is done by the DE rather than systemd. The service file was originally provided by orschiro for his package of networkmanager-dispatcher-insync-systemd [1]. Could you contact him directly to confirm if your modification work for his package or not? Meanwhile, I will only change the line of 'ExecStart=' in insync.service. [1]: https://aur.archlinux.org/packages/networkmanager-dispatcher-insync-systemd/

colinkeenan commented on 2013-09-21 06:51 (UTC)

I made another change to /usr/lib/systemd/system/insync@.service, replacing "always" with "never" in the line that says "Restart=..." and that solved the constantly restarting problem. Why was it set to keep restarting? It doesn't need to do that. Do I have an outdated insync@.service file or does it need to be updated in AUR? I had tried reinstalling insync using yaourt before messing with insync@.service, and that didn't work.

colinkeenan commented on 2013-09-21 06:41 (UTC)

/usr/lib/systemd/system/insync@.service needs to be changed. A couple of hours ago I realized Insync was not running and probably had not been running for a few days. I could start it manually from the command line with "insync start", but "systemctl start insync@colin" just waited 60 seconds and came back to the prompt without doing anything. I edited "/usr/lib/systemd/system/insync@.service" and noticed "ExecStart=/usr/bin/insync" which if I ran "/usr/bin/insync" from the command line, it would just give me a list of options and not actually run it. So I added "start" to the end of that line. But, now it runs a second instance every 60 seconds and puts up an alert that it's already running so the second instance will quit now. I'm thinking the problem may be with the reload step: "ExecReload=/bin/kill -HUP $MAINPID". If that's the problem, what should it say instead? Why is this set to constantly reload anyway? Insync doesn't seem to need to be reloaded to do it's thing.

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