Summary: | EDITING : CMIS no connection to GDrive | ||
---|---|---|---|
Product: | LibreOffice | Reporter: | sophie <sophi> |
Component: | Writer | Assignee: | Not Assigned <libreoffice-bugs> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | cao.cuong.ngo, cno, dgerard, edmund.laugasson, gagrilli.mailing, giuseppe.castagno, ikuya, mihhkel, philipz85, pje335-lo, serval2412 |
Priority: | medium | ||
Version: | 4.2.0.0.alpha0+ Master | ||
Hardware: | All | ||
OS: | All | ||
See Also: | https://bugs.documentfoundation.org/show_bug.cgi?id=97898 | ||
Whiteboard: | |||
Crash report or crash signature: | Regression By: | ||
Bug Depends on: | |||
Bug Blocks: | 98360 |
Description
sophie
2013-12-12 16:14:51 UTC
On pc Debian x86-64 with master sources updated today or 4.2 sources updated some days ago, I got: "Nonexistent file" when clicking "Refresh". I noticed this: warn:ucb.ucp.gio:25503:1:ucb/source/ucp/gio/gio_content.cxx:378: ignoring GError "Operation not supported" for <> warn:ucb.ucp.gio:25503:1:ucb/source/ucp/gio/gio_content.cxx:378: ignoring GError "Operation not supported" for <> Cédric: put you in cc since you might be interested in this cmis bug. Ok, I put OpenDataSpace as Server Type + https://cmis.cloudoku.com/atom for Binding Url, then I got the dialog user/password after having clicked Refresh button. I entered a valid login/password but had "The specified device is invalid" (see https://bugs.freedesktop.org/show_bug.cgi?id=72277) (In reply to comment #2) > Ok, I put OpenDataSpace as Server Type + https://cmis.cloudoku.com/atom for > Binding Url, then I got the dialog user/password after having clicked > Refresh button. > > I entered a valid login/password but had "The specified device is invalid" > (see https://bugs.freedesktop.org/show_bug.cgi?id=72277) That one specific thing should be the same problem than bug 72277. Thank you Sophie for pointing me to this bug, I can reproduce this bug running: Version: 4.2.1.1 Build ID: d7dbbd7842e6a58b0f521599204e827654e1fb8b mac osx 10.9.1 @Cao Cuong Ngo: Do you have an idea why this isn't working? I can confirm Sophie's bug for 4.2.0.4 (Build ID: 420m0(Build:4)) on (64-bit) Linux Mint 16.... Henri Using 64-bit Linux Mint Cinnamon 17.1 with 4.0.4-040004-generic kernel LibreOffice version: 5.0.0.0.beta1 Build ID: 0a16c3dda4150008d9be6f24cbd15ac198d116d3 Locale: et-EE (et_EE.UTF-8) Allowing LibreOffice menus but still not possible to connect - the "OK" button is just greyed out. Also there is a question - what to write to the "Repository" and "Path" fields. The button in the end of "Repository" shows refresh button and once it even asked login but using the username with or without "@gmail.com" in the end does nothing. But "OK" remains greyed out regardless if I pressed that reload button and once even entered credentials. Using 64-bit DEB-version of LibreOffice 4.4.3.2 40m0(Build:2) do not see the Google Drive choice in CMIS dialog. This is not working for me either with LibO 5.0.2 (Mageia 5, 64-bit RPMs from TDF). I have two-step verification enabled for my Google account - could that cause this? (In reply to Mihkel Tõnnov from comment #8) > This is not working for me either with LibO 5.0.2 (Mageia 5, 64-bit RPMs > from TDF). I have two-step verification enabled for my Google account - > could that cause this? Google 2Fa is not implemented in LO, see bug 97898, comment 10. Daily masters are not Google Drive enabled, this one: <http://dev-builds.libreoffice.org/daily/master/Linux-rpm_deb-x86_64@70-TDF/gdrivetest2/LibreOfficeDev_5.2.0.0.alpha0_Linux_x86-64_deb.tar.gz> It's a special version of master build specifically created to check bug 98416. It probably fixes this bug as well. Note that there's still bug 87938 (two-factor auth for gdrive not working) - so if you want to test, you have to disable two-factor authentication temporarily. At <http://dev-builds.libreoffice.org/daily/master/Linux-rpm_deb-x86_64@70-TDF/gdrivetest2> rpms are available as well. Closing this as its a duplicate, which has just been fixed. *** This bug has been marked as a duplicate of bug 98416 *** |