- Updated Drive API batch request endpoint
Please help us test
Please help us test
No package for arch/manjaro?
New version makes insync offline all the time (confirmed by “insync get_status”; the icon on GNOME’s status bar also appears gray). New files created locally are not being synced with GDrive, same happens to remote files, which are not being synced to local folders. Switching back to 1.5.5…
EDIT: first attempt didn’t replace 1.5.5, but actually installed 1.5.7 alongside it. I removed both and tried to install only 1.5.7:
> sudo dnf install ./insync-184.108.40.206371-fc25.x86_64.rpm Last metadata expiration check: 0:37:54 ago on ter 19 mar 2019 09:19:36 -03. Dependencies resolved. ================================================================================ Package Architecture Version Repository Size ================================================================================ Installing: insync x86_64 220.127.116.11371-fc25 @commandline 136 M Transaction Summary ================================================================================ Install 1 Package Total size: 136 M Installed size: 363 M Is this ok [y/N]: y Downloading Packages: Running transaction check Transaction check succeeded. Running transaction test Transaction test succeeded. Running transaction Preparing : 1/1 Installing : insync-18.104.22.168371-fc25.x86_64 1/1 Running scriptlet: insync-22.214.171.124371-fc25.x86_64 1/1 error: can't create transaction lock on /var/lib/rpm/.rpm.lock (Resource temporarily unavailable) error: -: key 1 import failed. which: no xmessage in (/usr/lib/insync:/sbin:/bin:/usr/sbin:/usr/bin:/usr/X11R6/bin) Insync installation has finished. You may now start it. Verifying : insync-126.96.36.199371-fc25.x86_64 1/1 Installed: insync-188.8.131.52371-fc25.x86_64 Complete! > insync get_status OFFLINE
Quitting insync through the status bar icon doesn’t actually terminate it. The icon remains grayed out, but further attempts to quit through the command line return “Insync doesn’t seem to be running. Start it first.” I ran insync start with --no-daemon, and when I tried to quit it, it got stuck here:
INFO 2019-03-19 10:06:23,681 [platform_impl_portable:quit:164] calling quit in platform_impl INFO 2019-03-19 10:06:23,685 [unix_socket_server_portable:stop:61] unix socket server thread stop ERROR 2019-03-19 10:06:23,851 [clientlogging:_logged_report_error:223] Uncaught error from <AnalyticsUploaderTask at 0x7fa11e59e0f0> Traceback (most recent call last): File "gevent/greenlet.py", line 390, in run File "ideskmain/clienttasks/analytics.py", line 80, in _run File "ideskmain/clienttasks/analytics.py", line 151, in __upload File "idesknet/clienthttp.py", line 144, in request File "idesknet/clienthttp.py", line 219, in raw_request File "idesknet/clienthttp.py", line 238, in __request File "idesknet/clienthttpsconnection.py", line 93, in connect File "gevent/ssl.py", line 419, in wrap_socket File "gevent/ssl.py", line 84, in __init__ File "idesknet/clienthttp.py", line 440, in sslwrap File "ssl.py", line 347, in __new__ SSLError: ('failed to allocate SSL context',) INFO 2019-03-19 10:06:23,871 [gdsyncer:stop:77] Stopping GD syncer... INFO 2019-03-19 10:06:23,871 [fswatch:_stop:544] LinuxFSWatcher._stop
Had to manually kill insync process. Something is seriously wrong with 1.5.7…
Just installed Insync 1.5.7 on a fresh Fedora 29 install and cannot get Insync to add my Google accounts. I’ve tried both the normal and alternate login methods. The normal method just leaves me at a browser window with the message “Connecting to Insync” while the alternate login method just clears the code that I paste in when I click the login button.
I’m really sorry for this! Could you please try changing networks and let me know if that helps?
Will be bringing up this issue to our Linux team.
Thank you so much for the detailed report.
I removed the Insync 1.5.7 RPM and installed 1.5.5 which seems to work with the alternate login method. I tried upgrading from 1.5.5 to 1.5.7 and while it maintained my Google account, files do not sync.
Can you try re-downloading the Fedora package above and install by using
sudo dnf install?
Let me know what happens
@Kurt_Ko I upgraded from 1.5.5 to 1.5.7 with the latest RPM and things seem to be working again.
I terminated a running instance of 1.5.5, and tried to install 1.5.7 (re-downloaded from link above) with sudo dnf install. At the end, both 1.5.5 and 1.5.7 were installed:
> sudo dnf install ./insync-184.108.40.206371-fc26.x86_64.rpm Last metadata expiration check: 0:24:05 ago on qui 21 mar 2019 10:21:22 -03. Dependencies resolved. ================================================================================ Package Architecture Version Repository Size ================================================================================ Upgrading: insync x86_64 220.127.116.11371-fc26 @commandline 135 M Transaction Summary ================================================================================ Upgrade 1 Package Total size: 135 M Is this ok [y/N]: y Downloading Packages: Running transaction check Transaction check succeeded. Running transaction test Transaction test succeeded. Running transaction Preparing : 1/1 Upgrading : insync-18.104.22.168371-fc26.x86_64 1/2 Running scriptlet: insync-22.214.171.124371-fc26.x86_64 1/2 error: can't create transaction lock on /var/lib/rpm/.rpm.lock (Resource temporarily unavailable) error: -: key 1 import failed. which: no xmessage in (/usr/lib/insync:/sbin:/bin:/usr/sbin:/usr/bin:/usr/X11R6/bin) Insync installation has finished. You may now start it. Running scriptlet: insync-126.96.36.199367-fc26.x86_64 2/2 Killed > rpm -qa insync insync-188.8.131.52367-fc26.x86_64 insync-184.108.40.206371-fc26.x86_64
I removed both of them, and reinstalled 1.5.7, and started it manually. Now it seems to be working just fine. I will keep using and report back here any problems.
The RPM upgrade through dnf still needs to be fixed to avoid simultaneous versions, and the installation script also has some issues (xmessage is not installed – maybe gxmessage should be listed as a dependency? – and some key import seems fo fail). But, aside from that, insync seems to be running just fine once again. Thanks for the update!
Please, check my questions there, that will affect if I will use InSync or not. Thanks.