"Google Docs Offline" for Chromium linux

1,505 views
Skip to first unread message

James LaBarre

unread,
May 19, 2017, 12:43:32 PM5/19/17
to Chromium-discuss
I have been trying to get the "Google Docs Offline" extension to work under Chromium on Linux (Mint 18.1 in my case).  I have v58.0.3029 on a 64bit and 32bit installation.  The 64bit version will activate, and work briefly (enabling the extension, setting a couple docs for offline sync, start and start the application a couple of times) and then deactivate itself.  Under 32bit it can't be started at all (the on/off slider is stuck half-way).  Really need it to work under 32bit, as it's a Netbook I would carry to places where I don't have connectivity (I loaded linux on it in place of the extremely obsolete WinXP that was on it).

PhistucK

unread,
May 19, 2017, 12:47:25 PM5/19/17
to j.e.l...@gmail.com, Chromium-discuss
Sounds weird, perhaps extensions by Google have some kind of a "protection" that prevents their use in non Google Chrome products... That would be kind of petty and bumming of them, but it is possible.

Though not running at all on 32 bit installations... That is very weird. I thought it might be using Native Client modules (which are platform specific), but the extension seems to only include JavaScript files (which are not platform specific, obviously).

Not sure.


PhistucK

On Fri, May 19, 2017 at 4:36 PM, James LaBarre <j.e.l...@gmail.com> wrote:
I have been trying to get the "Google Docs Offline" extension to work under Chromium on Linux (Mint 18.1 in my case).  I have v58.0.3029 on a 64bit and 32bit installation.  The 64bit version will activate, and work briefly (enabling the extension, setting a couple docs for offline sync, start and start the application a couple of times) and then deactivate itself.  Under 32bit it can't be started at all (the on/off slider is stuck half-way).  Really need it to work under 32bit, as it's a Netbook I would carry to places where I don't have connectivity (I loaded linux on it in place of the extremely obsolete WinXP that was on it).

--
--
Chromium Discussion mailing list: chromium...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-discuss

---
You received this message because you are subscribed to the Google Groups "Chromium-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-discuss+unsubscribe@chromium.org.

Torne (Richard Coles)

unread,
May 19, 2017, 12:56:24 PM5/19/17
to phis...@gmail.com, j.e.l...@gmail.com, Chromium-discuss
Does your chromium build have up to date API keys with all the APIs used by current Chrome enabled? It's possible the extension is relying on an extension API that's backed by a Google API that your build can't reach..

To unsubscribe from this group and stop receiving emails from it, send an email to chromium-discu...@chromium.org.

PhistucK

unread,
May 19, 2017, 1:09:55 PM5/19/17
to Torne (Richard Coles), j.e.l...@gmail.com, Chromium-discuss
I see usages of chrome.storage.managed. But it seems to be related to G Suite accounts.


PhistucK

On Fri, May 19, 2017 at 7:56 PM, Torne (Richard Coles) <to...@chromium.org> wrote:
Does your chromium build have up to date API keys with all the APIs used by current Chrome enabled? It's possible the extension is relying on an extension API that's backed by a Google API that your build can't reach..
On Fri, 19 May 2017 at 12:47 PhistucK <phis...@gmail.com> wrote:
Sounds weird, perhaps extensions by Google have some kind of a "protection" that prevents their use in non Google Chrome products... That would be kind of petty and bumming of them, but it is possible.

Though not running at all on 32 bit installations... That is very weird. I thought it might be using Native Client modules (which are platform specific), but the extension seems to only include JavaScript files (which are not platform specific, obviously).

Not sure.


PhistucK

On Fri, May 19, 2017 at 4:36 PM, James LaBarre <j.e.l...@gmail.com> wrote:
I have been trying to get the "Google Docs Offline" extension to work under Chromium on Linux (Mint 18.1 in my case).  I have v58.0.3029 on a 64bit and 32bit installation.  The 64bit version will activate, and work briefly (enabling the extension, setting a couple docs for offline sync, start and start the application a couple of times) and then deactivate itself.  Under 32bit it can't be started at all (the on/off slider is stuck half-way).  Really need it to work under 32bit, as it's a Netbook I would carry to places where I don't have connectivity (I loaded linux on it in place of the extremely obsolete WinXP that was on it).

--
--
Chromium Discussion mailing list: chromium...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-discuss

---
You received this message because you are subscribed to the Google Groups "Chromium-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-discuss+unsubscribe@chromium.org.

James LaBarre

unread,
May 19, 2017, 2:14:53 PM5/19/17
to Chromium-discuss, phis...@gmail.com, j.e.l...@gmail.com


On Friday, May 19, 2017 at 12:56:24 PM UTC-4, Torne (Richard Coles) wrote:
Does your chromium build have up to date API keys with all the APIs used by current Chrome enabled? It's possible the extension is relying on an extension API that's backed by a Google API that your build can't reach..


It's a pre-compiled build from an Ubuntu repository (running LinuxMint 18.1), so I don't know what I would need to look for in the package information.  It's not one I compiled myself (build 58.0.3029.110-0ubuntu0.16.04.12 if it makes any difference).

Torne (Richard Coles)

unread,
May 19, 2017, 2:33:48 PM5/19/17
to j.e.l...@gmail.com, Chromium-discuss, phis...@gmail.com
I don't know if this is actually the problem with this particular extension or not, but if it was, then this would be something the packager of your build would have to investigate/fix.

Olivier Tilloy

unread,
Jun 18, 2017, 1:57:49 AM6/18/17
to Chromium-discuss, j.e.l...@gmail.com, phis...@gmail.com
Le vendredi 19 mai 2017 20:33:48 UTC+2, Torne (Richard Coles) a écrit :
I don't know if this is actually the problem with this particular extension or not, but if it was, then this would be something the packager of your build would have to investigate/fix.

If the same extension works (although briefly) on a 64bits system with the same chromium package, then it's unlikely that the issue lies with API keys, as the 32bits and 64bits packages were built with the same API keys.
Reply all
Reply to author
Forward
0 new messages