Description of problem: Problem with "Google Sync" in the chromium-browser package, I'm unable to setup "Google Sync" on this version, it seems because the "API key" is missing for this distrobution, this post explaines the issue: https://groups.google.com/a/chromium.org/forum/?fromgroups=#!topic/chromium-dev/Qks4W0xLxqc Version-Release number of selected component (if applicable): Version 26.0.1410.51 Mageia.Org 2 (191102) How reproducible: Every time you try setting up "Google Sync" Steps to Reproduce: 1. Install chromium-browser via package manager 2. Setup "Google Sync" with your Google account 3. Chrome will tell you "Opps" and that sync is failed Reproducible: Steps to Reproduce:
CC: (none) => sander.lepikHardware: x86_64 => AllAssignee: bugsquad => dmorganec
Version: 2 => CauldronWhiteboard: (none) => MGA2TOO
CC: (none) => alda.cerny
i have the same problem with 64bit Mageia 3 and Chromium 26.0.1410.65
Hardware: All => x86_64Version: Cauldron => 3Source RPM: chromium-browser-stable-26.0.1410.51-1.mga2 => chromium-browser-stable-26.0.1410.65-1.mga3.tainted.x86_64.rpmWhiteboard: MGA2TOO => (none)
CC: (none) => adrien_d
update today : Version 28.0.1500.45 Mageia.Org 3 (205727) Bug still here
CC: (none) => inster.css
Hardware: x86_64 => All
CC: (none) => pterjan
If I understand correctly, generating api keys for binaries distributed by Mageia would then cause all Mageia users to be limited by the requests/day limit of each api function. Perhaps, for Mageia 2 and 3, it's time to replace the binaries with something similar to the flash-player-plugin, and have it download and install the program directly from google. I think the package should be dropped from Mageia 4, due to this change.
CC: (none) => davidwhodgins
The limits shouldn't be visible by the user (unless someone abuse the API using those keys). Other distributions have been adding such keys. Some examples: Debian: http://anonscm.debian.org/gitweb/?p=pkg-chromium/pkg-chromium.git;a=commitdiff;h=1c6f4c3b222a7fc38e7ab36916865ba6c90896e4 PLD: https://github.com/pld-linux/chromium-browser/commit/319f81f79128446be071c78078e1b5b42c5308b0 FreeBSD: http://svnweb.freebsd.org/ports/head/www/chromium/Makefile?r1=319795&r2=319796&view=patch I can create a Mageia key and request a proper quota.
I have created a Mageia key (sharing ownership of it with dmorgan and tv), got the large quota, and added it to the cauldron package. We should also add it to next updates.
When will the update come through, please? Have just updated to Chromium 28.0.1500.71 but problem persists. I have now no updates outstanding.
CC: (none) => phil.stott.derby
28.0.1500.71 update was released for Mageia 3 just before my change, it will be included in next update.
Depends on: (none) => 10922
and it was pushed, thanks
Status: NEW => RESOLVEDResolution: (none) => FIXED