Grive 0.2, which I use regularly, started failing a few days ago, so I upped the anteto grive 0.3, but it fails similarly. It looks like there is an unexpected http reply when it starts scanning the remote end.
Synchronizing folders
exception: /tmp/grive/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: N5boost16exception_detail10clone_implIN2gr4http5ErrorEEE
[PN2gr4expt12BacktraceTagE] = #0 0x812612f grive gr::Exception::Exception()
#1 0x810acb6 grive gr::http::Error::Error()
#2 0x8110bad grive gr::AuthAgent::CheckHttpResponse(long, std::string const&, gr::http::Header const&)
#3 0x81106e5 grive gr::AuthAgent::Get(std::string const&, gr::DataStream*, gr::http::Header const&)
#4 0x80f4ab8 grive gr::v1::Drive::SyncFolders()
#5 0x80f502b grive gr::v1::Drive::DetectChanges()
#6 0x80dfcf3 grive Main(int, char**)
#7 0x80e0303 grive main
#8 0xb7012a63 /lib/i386-linux-gnu/i686/cmov/libc.so.6 __libc_start_main
#9 0x80deb11 grive
[PN2gr4http15HttpResponseTagE] = 400
[PN2gr4http6UrlTagE] =
https://docs.google.com/feeds/default/private/full/-/folder?max-results=50&showroot=true
[PN2gr4http9HeaderTagE] = Authorization: Bearer ya29.XXXXXXXX57XvsjsXXXXXXXXlm0bORD2SNjXXXXXXXXXXXXj
GData-Version: 3.0
Any pointers?