Re: [arch-general] Libreoffice Google Drive not working

2016-08-14 Thread Martin Zecher via arch-general
The problem never solved here, but I'm not sure it's the same one since I cannot login in the first place. On Sat, Aug 13, 2016 at 12:57 PM, Jonathan Villatoro via arch-general < arch-general@archlinux.org> wrote: > Hello everyone, I hope my reply is no against mailing list etiquette. > If so,

Re: [arch-general] Libreoffice Google Drive not working

2016-08-13 Thread Jonathan Villatoro via arch-general
Hello everyone, I hope my reply is no against mailing list etiquette. If so, please pardon me. I have also experienced the same problem and, even though I currently have libmcis 0.5.1-2 and libreoffice-fresh 5.2.0-2, I'm also unable to open any Google Docs documents on libre office. It says

Re: [arch-general] Libreoffice Google Drive not working

2016-07-04 Thread Martin Zecher via arch-general
Thanks a lot Andy, but I still have the problem after upgrading libcmis to 0.5.1-2 On Mon, Jul 4, 2016 at 2:59 PM, Andreas Radke wrote: > Am Mon, 4 Jul 2016 17:43:29 +0200 > schrieb Andreas Radke : > > > Am Sun, 3 Jul 2016 18:13:24 -0300 > > schrieb

Re: [arch-general] Libreoffice Google Drive not working

2016-07-04 Thread Andreas Radke
Am Mon, 4 Jul 2016 17:43:29 +0200 schrieb Andreas Radke : > Am Sun, 3 Jul 2016 18:13:24 -0300 > schrieb Martin Zecher via arch-general : > > > When trying to access Google Drive under Libreoffice 5.1.4-1, I get > > "The specified device is

Re: [arch-general] Libreoffice Google Drive not working

2016-07-04 Thread Andreas Radke
Am Sun, 3 Jul 2016 18:13:24 -0300 schrieb Martin Zecher via arch-general : > When trying to access Google Drive under Libreoffice 5.1.4-1, I get > "The specified device is invalid". This problem should be fixed since > 5.1.3.2 according to >

[arch-general] Libreoffice Google Drive not working

2016-07-03 Thread Martin Zecher via arch-general
When trying to access Google Drive under Libreoffice 5.1.4-1, I get "The specified device is invalid". This problem should be fixed since 5.1.3.2 according to https://bugs.documentfoundation.org/show_bug.cgi?id=98416 I think there may be a problem with Arch's compilation. -- Martin Usen