[Expired for chromium-browser (Ubuntu) because there has been no
activity for 60 days.]
** Changed in: chromium-browser (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in
Thanks for trying to reproduce this, that's much appreciated! And glad
to hear it (apparently) solved itself.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1692319
Title:
The old Acer AspireOne netbook no longer has Linux on it (I was making
it into a FreeDOS machine), but I made a VM of LMDE5 (32-bit edition)
with a "qemu32" processor, and tested this with the v106 Chromium build
there.
The extension installed on that Chromium browser, and I was able to mark
some
Is this still an issue for the current Chromium stable?
** Changed in: chromium-browser (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
And as I mentioned there, if the same extension works (although briefly)
on a 64bits system with the same version of chromium, it's unlikely that
the issue lies with the API keys, as they are exactly the same shared by
all builds.
--
You received this bug notification because you are a member of
For reference, here is the link to the chromium-discuss thread mentioned
in comment #1: https://groups.google.com/a/chromium.org/forum/#!topic
/chromium-discuss/VoNNKLgmAzg.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
I did find an link to the very-last version of GoogleChrome for 32bit
Linux (one that Google didn't manage to obliterate from the internet)
and the extension works there, although it whines and moans that it's an
obsolete and unsupported version. So I know it is not dependent on
64bit. Would
I did see a question on the main Chromium Discuss forum when I asked
about this there:
"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
8 matches
Mail list logo
