This forum is dedicated to testing early releases and cauldron : Howtos, tips, tricks and user global feedback and thoughts...
Helpful tip :For bugs tracking we use :
https://bugs.mageia.org = The Mageia Bug Tracker
In this bug tracker you'll find already reported bugs and you'll be able to report those you have found....
by dlocklear01 » Oct 13th, '16, 06:03
Why does updates to Google Chrome give a error message of "bad signature" ?
Also, why does the list for media updates list Chrome x_64 and another called Google Chrome ?
I am in Google Chrome 54 now, after the October 12th update.
-
dlocklear01
-
- Posts: 35
- Joined: Sep 29th, '16, 18:03
by ozky » Oct 13th, '16, 13:40
Take a look here you can delete chrome_x86_64 repo and use google added one.
viewtopic.php?f=36&t=2053&p=64959&hilit=google+chrome#p64959One extra step is needed: associating the key with the Google repository.
From the Software Management window, go to Options menu -> Media Manager.
From the Configure Media window, go Options menu -> Manage keys.
Scroll down to sellect the chrome_* medium, and click the Add button.
Select the Google signing key, click OK.
Right key is 7fac5991.
Last edited by
doktor5000 on Oct 13th, '16, 17:59, edited 1 time in total.
Reason: fixed quote tags

Mageia user
-

ozky
-
- Posts: 581
- Joined: Jul 2nd, '11, 08:48
- Location: Nakkila Finland
by doktor5000 » Oct 13th, '16, 17:59
ozky wrote:Take a look here you can delete chrome_x86_64 repo and use google added one.
If he's already using the google repo there's no need to delete it to replace it with the same repo.
-

doktor5000
-
- Posts: 18052
- Joined: Jun 4th, '11, 10:10
- Location: Leipzig, Germany
-
by ozky » Oct 15th, '16, 18:56
No google rpm post install script add that second one google-chrome.

Mageia user
-

ozky
-
- Posts: 581
- Joined: Jul 2nd, '11, 08:48
- Location: Nakkila Finland
Return to Testing : Alpha, Beta, RC and Cauldron
Who is online
Users browsing this forum: No registered users and 1 guest