grive not syncing on ubuntu 14.04

leobrowning92 commented 9 years ago

I am having trouble syncing with my google drive account from grive running on Ubuntu 14.04. I have never had problems previously. I tried purging drive from my system and deleting all local folders, but still come up with this when I try to run grive after reinstalling.

user@user-OptiPlex-780:~/drive$ grive
grive: Symbol `json_tokener_errors' has different size in shared  object, consider re-linking
Reading local directories
Synchronizing folders
exception: /build/buildd/grive-0.2.0/libgrive/src/http/CurlAgent.cc(149): Throw in function long int    gr::http::CurlAgent::ExecCurl(const string&, gr::http::Receivable*, const   gr::http::Header&)
Dynamic exception type:boost::exception_detail::clone_impl<gr::http::Error>
std::exception::what: std::exception
[gr::expt::MsgTag*] = 
[gr::http::CurlCodeTag*] = 0
[gr::http::HttpResponseTag*] = 400
[gr::http::UrlTag*] = https://docs.google.com/feeds/default/private/full/-/folder?max-results=50&showroot=true
[gr::http::HeaderTag*] = Authorization: Bearer ya29.WwFOho3OkmkxFIdn86HBbtpSIyBYDzDgQua1K6JcEu7kCBLgvY1aEiUHCZlSCuli_qPHkTfNZLhDfQ
GData-Version: 3.0

Here is a link to a google developers page that suggests that the API has changed today link. could that be an issue?

colinkeenan commented 9 years ago

Same here on Arch Linux, also started last night, and still a problem today:

Reading local directories
Synchronizing folders
exception: /home/colin/aur/grive/src/grive-master/libgrive/src/protocol/AuthAgent.cc(174): Throw in function long int gr::AuthAgent::CheckHttpResponse(long int, const string&, const gr::http::Header&)
Dynamic exception type: boost::exception_detail::clone_impl<gr::http::Error>
[gr::http::HttpResponseTag*] = 400
[gr::http::UrlTag*] = https://docs.google.com/feeds/default/private/full/-/folder?max-results=50&showroot=true
[gr::http::HeaderTag*] = Authorization: Bearer ya29.XAGBkIdDKv3JmDcr9IPmKtOZyxUYx_TFg1-l7lWBX9oxJEWEmGTvaRCdhhckleJ0_t4O1avZ2QF60A
GData-Version: 3.0

wakkadojo commented 9 years ago

Well, this did press me to find alternative tools, and I found one far superior to grive

https://github.com/odeke-em/drive/

There are also other alternatives, on arch you can search google drive in AUR:

https://aur.archlinux.org/packages/?O=0&K=google+drive

jnazaroff commented 9 years ago

Grive isn't working for me, either. I use ES File Explorer on my Android phone, and it has a cloud drive integration tool. Google Drive integration no longer works on it, either, though my OneDrive does. Seems like a global issue, not a Linux issue.

Anyone have any updates on the reason why?

colinkeenan commented 9 years ago

Thanks wakkadojo for pointing me to "drive". This is EXACTLY what I wanted! I was wishing this morning I could just push and pull like git, and you pointed me right to the package that does it. Better than grive for sure. I was using grive because it wasn't automatic and so worked as a backup and didn't so easily corrupt files as Insync Pro. This "drive" integrates far better with the features of Google Drive though and is very sensible.

jnazaroff, it must be the API change for Google Drive which was known about a long time ago and issues raised here, but apparently, grive is not being actively developed anymore. I use ES File Explorer too, but didn't realize it had a cloud drive integration. Apparently, ES File Explorer also needs to update to the new API.

jnazaroff commented 9 years ago

@colinkeenan, Thanks for the info.

@wakkadojo, I'm going to give that a shot right now. Is it also terminal-based, like grive, or does it have a GUI? I'm fine with either one. Just double-checking. Thanks for the help, everyone! :)

jnazaroff commented 9 years ago

@wakkadojo Also, can I simply change the name of the grive folder to gdrive to make the change effortless? Do the programs sync differently? In other words, would it mess anything up, do you think?

colinkeenan commented 9 years ago

"drive" is terminal based, but you have more control similar to what you can do in the browser.

On Tue, Apr 21, 2015 at 11:45 AM, jnazaroff notifications@github.com wrote:

@colinkeenan https://github.com/colinkeenan, Thanks for the info.

@wakkadojo https://github.com/wakkadojo, I'm going to give that a shot right now. Is it also terminal-based, like grive, or does it have a GUI? I'm fine with either one. Just double-checking. Thanks for the help, everyone! :)

— Reply to this email directly or view it on GitHub https://github.com/Grive/grive/issues/311#issuecomment-94900765.

jnazaroff commented 9 years ago

Thanks colinkeenan! :) What about the last question I asked wakkadojo, if you don't mind? Can I simply change the folder name so that I don't have to download everything all over again? I'm tethering from my phone, and that will be a hefty download and hefty fine. lol. Thanks to both of you though! :)

colinkeenan commented 9 years ago

I'm trying it out now, and used the same folder I had used with grive, "~/Google Drive". Here's what I did after installation:

drive init ~/Google\ Drive/
cd ~/Google\ Drive/
drive push

The init step gave me a URL which I pasted into Chrome. After approving Google Drive permissions, it gave me something to paste back into the terminal.

The push step did a checksum on all the files and listed everything with a '-' in front of those to be deleted from the cloud and a '+' in front of those to be added, and it asked if that's what I wanted to do. I said yes.

It appears to be going even slower than grive on the upload though. I'm not sure why, but it's going to take hours to complete. Maybe it's doing something different than I think, like for example, uploading everything again.

jnazaroff commented 9 years ago

Also, in case anyone is interested, if you use Chrome (I presume Chromium would work as well; I use google-chrome-stable), you can make an application shortcut and change the command to google-chrome-stable /opt/google/chrome/google-chrome --app=https://drive.google.com/drive/my-drive and add it as a shortcut on whatever DE you use (I use KDE4). Works pretty well. I guess this is only for those who want a quick fix, like me; it doesn't function as a backup as others have commented.

colinkeenan commented 9 years ago

It appears that "drive" does something to every file. It takes hours, and recent activity shows up saying I "edited" everything one by one, except for those files I added or deleted.

colinkeenan commented 9 years ago

jnazaroff, thanks for the tip - I like how it has the correct icon, but I've always got Chrome running and just use the customizable menu of Google products on the new-tab page to get to Google Drive.

jnazaroff commented 9 years ago

@colinkeenan Oooh..........not fun. Let me know if it does that every time or just this first time; I would imagine it's just a first-time deal.

And yeah, when I have chrome running, I do that, too. I guess I like the idea of accessing it directly from my desktop. seems quicker that way, and since I'll probably be using this for a little while, I like that it's one click away. :)

colinkeenan commented 9 years ago

@jnazaroff, "drive" sped up as it went and didn't take the many hours it was predicting. I think it only took an hour or less. I edited something to test it what it does after the first run. It's takes about the same or maybe faster than grive - it just changes what needs to be changed. As we expected, the messing with every file thing was just what it does on the first run. I'll mainly be using "drive push" which is about the same as "grive", but I'm glad it has so many other capabilities and I'll eventually use some of them.

jnazaroff commented 9 years ago

@colinkeenan: Excellent news! Thanks for sharing. Going to install now. :) So, I'm assuming after I add the repo, I can install via apt-get? Or should I just install the binary?

EDIT: Never mind, I answered my own question. Didn't realize go was a compiler. :)

jnazaroff commented 9 years ago

I like the interface of "drive." You see what's going on, and I like that it gives you a chance to review everything. I wonder if I could use | grep - or | grep + to see what's happening better; I have a lot of folders. lol.