Ubuntu Err :18 http://dl.google.com/linux/chrome/deb stable Release.gpg KEYEXPIRED 1555048520
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}
Since this morning I have this error
Err :18 http://dl.google.com/linux/chrome/deb stable Release.gpg
The following signatures are not valid : KEYEXPIRED 1555048520 KEYEXPIRED 1555048520 KEYEXPIRED 1555048520 KEYEXPIRED 1555048520
when I'm running
sudo apt-get update -y
I searched some solutions but I didn't find the good one on google so ... I'm here
ubuntu ubuntu-16.04
New contributor
add a comment |
Since this morning I have this error
Err :18 http://dl.google.com/linux/chrome/deb stable Release.gpg
The following signatures are not valid : KEYEXPIRED 1555048520 KEYEXPIRED 1555048520 KEYEXPIRED 1555048520 KEYEXPIRED 1555048520
when I'm running
sudo apt-get update -y
I searched some solutions but I didn't find the good one on google so ... I'm here
ubuntu ubuntu-16.04
New contributor
Apparently, google's signing key expired, so we just need to wait until they put out a new one. After they did just runwget -q -O - https://dl.google.com/linux/linux_signing_key.pub | sudo apt-key add -
to fix your problem.
– jangxx
Apr 12 at 8:29
I still have the problem
– Thomas COUMES
Apr 12 at 8:37
2
Did you read my comment? You have to wait until google puts out a new signing key. Until they do it, there is nothing we can do about the problem.
– jangxx
Apr 12 at 8:43
3
most probably the same as askubuntu.com/questions/1133199/…
– Gerald Schneider
Apr 12 at 9:46
add a comment |
Since this morning I have this error
Err :18 http://dl.google.com/linux/chrome/deb stable Release.gpg
The following signatures are not valid : KEYEXPIRED 1555048520 KEYEXPIRED 1555048520 KEYEXPIRED 1555048520 KEYEXPIRED 1555048520
when I'm running
sudo apt-get update -y
I searched some solutions but I didn't find the good one on google so ... I'm here
ubuntu ubuntu-16.04
New contributor
Since this morning I have this error
Err :18 http://dl.google.com/linux/chrome/deb stable Release.gpg
The following signatures are not valid : KEYEXPIRED 1555048520 KEYEXPIRED 1555048520 KEYEXPIRED 1555048520 KEYEXPIRED 1555048520
when I'm running
sudo apt-get update -y
I searched some solutions but I didn't find the good one on google so ... I'm here
ubuntu ubuntu-16.04
ubuntu ubuntu-16.04
New contributor
New contributor
New contributor
asked Apr 12 at 7:03
Thomas COUMESThomas COUMES
436
436
New contributor
New contributor
Apparently, google's signing key expired, so we just need to wait until they put out a new one. After they did just runwget -q -O - https://dl.google.com/linux/linux_signing_key.pub | sudo apt-key add -
to fix your problem.
– jangxx
Apr 12 at 8:29
I still have the problem
– Thomas COUMES
Apr 12 at 8:37
2
Did you read my comment? You have to wait until google puts out a new signing key. Until they do it, there is nothing we can do about the problem.
– jangxx
Apr 12 at 8:43
3
most probably the same as askubuntu.com/questions/1133199/…
– Gerald Schneider
Apr 12 at 9:46
add a comment |
Apparently, google's signing key expired, so we just need to wait until they put out a new one. After they did just runwget -q -O - https://dl.google.com/linux/linux_signing_key.pub | sudo apt-key add -
to fix your problem.
– jangxx
Apr 12 at 8:29
I still have the problem
– Thomas COUMES
Apr 12 at 8:37
2
Did you read my comment? You have to wait until google puts out a new signing key. Until they do it, there is nothing we can do about the problem.
– jangxx
Apr 12 at 8:43
3
most probably the same as askubuntu.com/questions/1133199/…
– Gerald Schneider
Apr 12 at 9:46
Apparently, google's signing key expired, so we just need to wait until they put out a new one. After they did just run
wget -q -O - https://dl.google.com/linux/linux_signing_key.pub | sudo apt-key add -
to fix your problem.– jangxx
Apr 12 at 8:29
Apparently, google's signing key expired, so we just need to wait until they put out a new one. After they did just run
wget -q -O - https://dl.google.com/linux/linux_signing_key.pub | sudo apt-key add -
to fix your problem.– jangxx
Apr 12 at 8:29
I still have the problem
– Thomas COUMES
Apr 12 at 8:37
I still have the problem
– Thomas COUMES
Apr 12 at 8:37
2
2
Did you read my comment? You have to wait until google puts out a new signing key. Until they do it, there is nothing we can do about the problem.
– jangxx
Apr 12 at 8:43
Did you read my comment? You have to wait until google puts out a new signing key. Until they do it, there is nothing we can do about the problem.
– jangxx
Apr 12 at 8:43
3
3
most probably the same as askubuntu.com/questions/1133199/…
– Gerald Schneider
Apr 12 at 9:46
most probably the same as askubuntu.com/questions/1133199/…
– Gerald Schneider
Apr 12 at 9:46
add a comment |
3 Answers
3
active
oldest
votes
This is an ongoing problem that only seems to hit Google Chrome. In order to avoid seeing warnings, one can temporarily turn off the repository for GC.
New contributor
Seeing this happen today as well. Disabling the repository may work, as Google Chrome can update itself. If it can't, it will show an icon for you to start the update.
– Ismael Miguel
Apr 12 at 16:56
add a comment |
wget -q -O - https://dl.google.com/linux/linux_signing_key.pub | sudo apt-key add -
https://www.google.com/linuxrepositories/
New contributor
I still have the error ... :/
– Thomas COUMES
Apr 12 at 8:36
this is first what I've tried and it doesn't solve the problem
– gummy
Apr 12 at 8:37
1
Just wait until google updates their signing key. This is not going to help before they do.
– jangxx
Apr 12 at 8:44
2
Must wait Google update there singing key and then do this command. It will be later today I think.
– r00t-err0r
Apr 12 at 8:46
add a comment |
To get rid of the problem (temporary) use --allow-unauthenticated in the apt command and wait until google fix the signing key.
You can check it from time to time by calling
curl 'https://dl.google.com/linux/linux_signing_key.pub' | gpg
New contributor
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "2"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Thomas COUMES is a new contributor. Be nice, and check out our Code of Conduct.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f962734%2fubuntu-err-18-http-dl-google-com-linux-chrome-deb-stable-release-gpg-keyexpir%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
This is an ongoing problem that only seems to hit Google Chrome. In order to avoid seeing warnings, one can temporarily turn off the repository for GC.
New contributor
Seeing this happen today as well. Disabling the repository may work, as Google Chrome can update itself. If it can't, it will show an icon for you to start the update.
– Ismael Miguel
Apr 12 at 16:56
add a comment |
This is an ongoing problem that only seems to hit Google Chrome. In order to avoid seeing warnings, one can temporarily turn off the repository for GC.
New contributor
Seeing this happen today as well. Disabling the repository may work, as Google Chrome can update itself. If it can't, it will show an icon for you to start the update.
– Ismael Miguel
Apr 12 at 16:56
add a comment |
This is an ongoing problem that only seems to hit Google Chrome. In order to avoid seeing warnings, one can temporarily turn off the repository for GC.
New contributor
This is an ongoing problem that only seems to hit Google Chrome. In order to avoid seeing warnings, one can temporarily turn off the repository for GC.
New contributor
New contributor
answered Apr 12 at 10:51
Thomas SandströmThomas Sandström
461
461
New contributor
New contributor
Seeing this happen today as well. Disabling the repository may work, as Google Chrome can update itself. If it can't, it will show an icon for you to start the update.
– Ismael Miguel
Apr 12 at 16:56
add a comment |
Seeing this happen today as well. Disabling the repository may work, as Google Chrome can update itself. If it can't, it will show an icon for you to start the update.
– Ismael Miguel
Apr 12 at 16:56
Seeing this happen today as well. Disabling the repository may work, as Google Chrome can update itself. If it can't, it will show an icon for you to start the update.
– Ismael Miguel
Apr 12 at 16:56
Seeing this happen today as well. Disabling the repository may work, as Google Chrome can update itself. If it can't, it will show an icon for you to start the update.
– Ismael Miguel
Apr 12 at 16:56
add a comment |
wget -q -O - https://dl.google.com/linux/linux_signing_key.pub | sudo apt-key add -
https://www.google.com/linuxrepositories/
New contributor
I still have the error ... :/
– Thomas COUMES
Apr 12 at 8:36
this is first what I've tried and it doesn't solve the problem
– gummy
Apr 12 at 8:37
1
Just wait until google updates their signing key. This is not going to help before they do.
– jangxx
Apr 12 at 8:44
2
Must wait Google update there singing key and then do this command. It will be later today I think.
– r00t-err0r
Apr 12 at 8:46
add a comment |
wget -q -O - https://dl.google.com/linux/linux_signing_key.pub | sudo apt-key add -
https://www.google.com/linuxrepositories/
New contributor
I still have the error ... :/
– Thomas COUMES
Apr 12 at 8:36
this is first what I've tried and it doesn't solve the problem
– gummy
Apr 12 at 8:37
1
Just wait until google updates their signing key. This is not going to help before they do.
– jangxx
Apr 12 at 8:44
2
Must wait Google update there singing key and then do this command. It will be later today I think.
– r00t-err0r
Apr 12 at 8:46
add a comment |
wget -q -O - https://dl.google.com/linux/linux_signing_key.pub | sudo apt-key add -
https://www.google.com/linuxrepositories/
New contributor
wget -q -O - https://dl.google.com/linux/linux_signing_key.pub | sudo apt-key add -
https://www.google.com/linuxrepositories/
New contributor
New contributor
answered Apr 12 at 8:33
r00t-err0rr00t-err0r
212
212
New contributor
New contributor
I still have the error ... :/
– Thomas COUMES
Apr 12 at 8:36
this is first what I've tried and it doesn't solve the problem
– gummy
Apr 12 at 8:37
1
Just wait until google updates their signing key. This is not going to help before they do.
– jangxx
Apr 12 at 8:44
2
Must wait Google update there singing key and then do this command. It will be later today I think.
– r00t-err0r
Apr 12 at 8:46
add a comment |
I still have the error ... :/
– Thomas COUMES
Apr 12 at 8:36
this is first what I've tried and it doesn't solve the problem
– gummy
Apr 12 at 8:37
1
Just wait until google updates their signing key. This is not going to help before they do.
– jangxx
Apr 12 at 8:44
2
Must wait Google update there singing key and then do this command. It will be later today I think.
– r00t-err0r
Apr 12 at 8:46
I still have the error ... :/
– Thomas COUMES
Apr 12 at 8:36
I still have the error ... :/
– Thomas COUMES
Apr 12 at 8:36
this is first what I've tried and it doesn't solve the problem
– gummy
Apr 12 at 8:37
this is first what I've tried and it doesn't solve the problem
– gummy
Apr 12 at 8:37
1
1
Just wait until google updates their signing key. This is not going to help before they do.
– jangxx
Apr 12 at 8:44
Just wait until google updates their signing key. This is not going to help before they do.
– jangxx
Apr 12 at 8:44
2
2
Must wait Google update there singing key and then do this command. It will be later today I think.
– r00t-err0r
Apr 12 at 8:46
Must wait Google update there singing key and then do this command. It will be later today I think.
– r00t-err0r
Apr 12 at 8:46
add a comment |
To get rid of the problem (temporary) use --allow-unauthenticated in the apt command and wait until google fix the signing key.
You can check it from time to time by calling
curl 'https://dl.google.com/linux/linux_signing_key.pub' | gpg
New contributor
add a comment |
To get rid of the problem (temporary) use --allow-unauthenticated in the apt command and wait until google fix the signing key.
You can check it from time to time by calling
curl 'https://dl.google.com/linux/linux_signing_key.pub' | gpg
New contributor
add a comment |
To get rid of the problem (temporary) use --allow-unauthenticated in the apt command and wait until google fix the signing key.
You can check it from time to time by calling
curl 'https://dl.google.com/linux/linux_signing_key.pub' | gpg
New contributor
To get rid of the problem (temporary) use --allow-unauthenticated in the apt command and wait until google fix the signing key.
You can check it from time to time by calling
curl 'https://dl.google.com/linux/linux_signing_key.pub' | gpg
New contributor
New contributor
answered Apr 12 at 11:19
Maik WagnerMaik Wagner
211
211
New contributor
New contributor
add a comment |
add a comment |
Thomas COUMES is a new contributor. Be nice, and check out our Code of Conduct.
Thomas COUMES is a new contributor. Be nice, and check out our Code of Conduct.
Thomas COUMES is a new contributor. Be nice, and check out our Code of Conduct.
Thomas COUMES is a new contributor. Be nice, and check out our Code of Conduct.
Thanks for contributing an answer to Server Fault!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f962734%2fubuntu-err-18-http-dl-google-com-linux-chrome-deb-stable-release-gpg-keyexpir%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Apparently, google's signing key expired, so we just need to wait until they put out a new one. After they did just run
wget -q -O - https://dl.google.com/linux/linux_signing_key.pub | sudo apt-key add -
to fix your problem.– jangxx
Apr 12 at 8:29
I still have the problem
– Thomas COUMES
Apr 12 at 8:37
2
Did you read my comment? You have to wait until google puts out a new signing key. Until they do it, there is nothing we can do about the problem.
– jangxx
Apr 12 at 8:43
3
most probably the same as askubuntu.com/questions/1133199/…
– Gerald Schneider
Apr 12 at 9:46