The following signatures were invalid: EXPKEYSIG 1397BC53640DB551 Announcing the arrival of Valued Associate #679: Cesar Manara Planned maintenance scheduled April 23, 2019 at 23:30 UTC (7:30pm US/Eastern)Ubuntu 18.04 update problemWhat to do with KEYEXPIRED 1555048520 on updating Google Chrome and Earth repositories?Failed to install PlayOnLinuxApt-get failed to fetch from Ubuntu server with error code 404Issues opening everything“Something wicked happened” error in apt-getIs this an error => Starting pkgProblemResolver with broken count: 0E: The repository 'https://download.01.org/gfx/ubuntu/17.04/main zesty Release' does no longer have a Release fileappstreamcli: AppStream system cache was updated, but problems were found: Metadata files have errors: /var/cache/app-info/xmls/fwupd.xmlUbuntu server 18.04 LTS apt unable updateUnable to install dovecot-lmtpd on Ubuntu 18.04 serverhash sum mismatch, you have held broken packages, unable to fetch etchttp://security.debian.org/dists/cosmic/Release 404 Not Found [IP: 151.101.184.204 80]

White walkers, cemeteries and wights

Why complex landing gears are used instead of simple,reliability and light weight muscle wire or shape memory alloys?

Is openssl rand command cryptographically secure?

What is the difference between a "ranged attack" and a "ranged weapon attack"?

Tips to organize LaTeX presentations for a semester

Weaponising the Grasp-at-a-Distance spell

What is a more techy Technical Writer job title that isn't cutesy or confusing?

Rationale for describing kurtosis as "peakedness"?

How to change the tick of the color bar legend to black

Delete free apps from library

GDP with Intermediate Production

How much damage would a cupful of neutron star matter do to the Earth?

Why is it faster to reheat something than it is to cook it?

AppleTVs create a chatty alternate WiFi network

How can a team of shapeshifters communicate?

I got rid of Mac OSX and replaced it with linux but now I can't change it back to OSX or windows

Simple Line in LaTeX Help!

Why not send Voyager 3 and 4 following up the paths taken by Voyager 1 and 2 to re-transmit signals of later as they fly away from Earth?

Mounting TV on a weird wall that has some material between the drywall and stud

How were pictures turned from film to a big picture in a picture frame before digital scanning?

Why shouldn't this prove the Prime Number Theorem?

New Order #6: Easter Egg

Central Vacuuming: Is it worth it, and how does it compare to normal vacuuming?

Where is the Next Backup Size entry on iOS 12?



The following signatures were invalid: EXPKEYSIG 1397BC53640DB551



Announcing the arrival of Valued Associate #679: Cesar Manara
Planned maintenance scheduled April 23, 2019 at 23:30 UTC (7:30pm US/Eastern)Ubuntu 18.04 update problemWhat to do with KEYEXPIRED 1555048520 on updating Google Chrome and Earth repositories?Failed to install PlayOnLinuxApt-get failed to fetch from Ubuntu server with error code 404Issues opening everything“Something wicked happened” error in apt-getIs this an error => Starting pkgProblemResolver with broken count: 0E: The repository 'https://download.01.org/gfx/ubuntu/17.04/main zesty Release' does no longer have a Release fileappstreamcli: AppStream system cache was updated, but problems were found: Metadata files have errors: /var/cache/app-info/xmls/fwupd.xmlUbuntu server 18.04 LTS apt unable updateUnable to install dovecot-lmtpd on Ubuntu 18.04 serverhash sum mismatch, you have held broken packages, unable to fetch etchttp://security.debian.org/dists/cosmic/Release 404 Not Found [IP: 151.101.184.204 80]



.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;








90















This is Issue 952287: [User Feedback - Stable] Reports of Chrome for Linux failing to install/update due to expired GPG signing key




Today, running apt in all my machines gives this error with the Google PPA (for google-chrome):



me@mymachine:~$ sudo apt clean && sudo apt update && sudo apt full-upgrade -y && sudo apt autoremove -y && sudo apt autoclean -y && sudo snap refresh 
[sudo] password for me:
Ign:1 http://dl.google.com/linux/chrome/deb stable InRelease
Hit:2 http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu bionic InRelease
Hit:3 http://dl.google.com/linux/chrome/deb stable Release
Hit:4 http://archive.ubuntu.com/ubuntu bionic InRelease
Get:5 http://archive.ubuntu.com/ubuntu bionic-updates InRelease [88,7 kB]
Get:6 http://archive.ubuntu.com/ubuntu bionic-backports InRelease [74,6 kB]
Err:7 http://dl.google.com/linux/chrome/deb stable Release.gpg
The following signatures were invalid: EXPKEYSIG 1397BC53640DB551 Google Inc. (Linux Packages Signing Authority) <linux-packages-keymaster@google.com>
Get:8 http://archive.ubuntu.com/ubuntu bionic-security InRelease [88,7 kB]
Get:9 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages [574 kB]
Get:10 http://archive.ubuntu.com/ubuntu bionic-updates/main i386 Packages [488 kB]
Get:11 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 DEP-11 Metadata [278 kB]
Get:12 http://archive.ubuntu.com/ubuntu bionic-updates/main DEP-11 48x48 Icons [66,7 kB]
Get:13 http://archive.ubuntu.com/ubuntu bionic-updates/main DEP-11 64x64 Icons [123 kB]
Get:14 http://archive.ubuntu.com/ubuntu bionic-updates/universe amd64 Packages [756 kB]
Get:15 http://archive.ubuntu.com/ubuntu bionic-updates/universe i386 Packages [745 kB]
Get:16 http://archive.ubuntu.com/ubuntu bionic-updates/universe Translation-en [201 kB]
Get:17 http://archive.ubuntu.com/ubuntu bionic-updates/universe amd64 DEP-11 Metadata [209 kB]
Get:18 http://archive.ubuntu.com/ubuntu bionic-updates/universe DEP-11 48x48 Icons [191 kB]
Get:19 http://archive.ubuntu.com/ubuntu bionic-updates/universe DEP-11 64x64 Icons [360 kB]
Get:20 http://archive.ubuntu.com/ubuntu bionic-updates/multiverse amd64 DEP-11 Metadata [2.468 B]
Get:21 http://archive.ubuntu.com/ubuntu bionic-backports/universe amd64 DEP-11 Metadata [7.352 B]
Get:22 http://archive.ubuntu.com/ubuntu bionic-security/main amd64 Packages [296 kB]
Get:23 http://archive.ubuntu.com/ubuntu bionic-security/main i386 Packages [216 kB]
Get:24 http://archive.ubuntu.com/ubuntu bionic-security/main amd64 DEP-11 Metadata [204 B]
Get:25 http://archive.ubuntu.com/ubuntu bionic-security/universe i386 Packages [127 kB]
Get:26 http://archive.ubuntu.com/ubuntu bionic-security/universe amd64 Packages [131 kB]
Get:27 http://archive.ubuntu.com/ubuntu bionic-security/universe Translation-en [74,2 kB]
Get:28 http://archive.ubuntu.com/ubuntu bionic-security/universe amd64 DEP-11 Metadata [20,8 kB]
Get:29 http://archive.ubuntu.com/ubuntu bionic-security/universe DEP-11 48x48 Icons [12,2 kB]
Get:30 http://archive.ubuntu.com/ubuntu bionic-security/universe DEP-11 64x64 Icons [50,4 kB]
Get:31 http://archive.ubuntu.com/ubuntu bionic-security/multiverse amd64 DEP-11 Metadata [2.464 B]
Fetched 5.183 kB in 2s (2.131 kB/s)
Reading package lists... Done
Building dependency tree
Reading state information... Done
All packages are up to date.
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://dl.google.com/linux/chrome/deb stable Release: The following signatures were invalid: EXPKEYSIG 1397BC53640DB551 Google Inc. (Linux Packages Signing Authority) <linux-packages-keymaster@google.com>
W: Failed to fetch http://dl.google.com/linux/chrome/deb/dists/stable/Release.gpg The following signatures were invalid: EXPKEYSIG 1397BC53640DB551 Google Inc. (Linux Packages Signing Authority) <linux-packages-keymaster@google.com>
W: Some index files failed to download. They have been ignored, or old ones used instead.
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Reading package lists... Done
Building dependency tree
Reading state information... Done
All snaps up to date.



Already tried importing GPG key again with:



wget -q -O - https://dl-ssl.google.com/linux/linux_signing_key.pub | sudo apt-key add -


Source: Google Linux Software Repositories



EDIT: add error line in Spanish for better visibility:



Las siguientes firmas no fueron válidas: EXPKEYSIG 1397BC53640DB551 Google Inc. (Linux Packages Signing Authority) <linux-packages-keymaster@google.com>



EDIT2: and French (to cover top 3 languages):



Les signatures suivantes ne sont pas valables : EXPKEYSIG 1397BC53640DB551 Google Inc. (Linux Packages Signing Authority) <linux-packages-keymaster@google.com>










share|improve this question



















  • 11





    It just happened to me as well.

    – Fred
    Apr 12 at 8:04






  • 8





    upvote this link support.google.com/chrome/thread/4032170?hl=en and wait! We can do nothing more.

    – Carlos Alberto Silveira de And
    Apr 12 at 10:31







  • 1





    I've added a link to the bug report at the top of the post. Please feel free to move it or to delete it.

    – DK Bose
    Apr 12 at 17:01






  • 4





    I think it is fixed now

    – Leo
    Apr 12 at 17:26






  • 1





    This happened to me today, 8 days later and it's still happening.

    – Gregory Smitherman
    10 hours ago

















90















This is Issue 952287: [User Feedback - Stable] Reports of Chrome for Linux failing to install/update due to expired GPG signing key




Today, running apt in all my machines gives this error with the Google PPA (for google-chrome):



me@mymachine:~$ sudo apt clean && sudo apt update && sudo apt full-upgrade -y && sudo apt autoremove -y && sudo apt autoclean -y && sudo snap refresh 
[sudo] password for me:
Ign:1 http://dl.google.com/linux/chrome/deb stable InRelease
Hit:2 http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu bionic InRelease
Hit:3 http://dl.google.com/linux/chrome/deb stable Release
Hit:4 http://archive.ubuntu.com/ubuntu bionic InRelease
Get:5 http://archive.ubuntu.com/ubuntu bionic-updates InRelease [88,7 kB]
Get:6 http://archive.ubuntu.com/ubuntu bionic-backports InRelease [74,6 kB]
Err:7 http://dl.google.com/linux/chrome/deb stable Release.gpg
The following signatures were invalid: EXPKEYSIG 1397BC53640DB551 Google Inc. (Linux Packages Signing Authority) <linux-packages-keymaster@google.com>
Get:8 http://archive.ubuntu.com/ubuntu bionic-security InRelease [88,7 kB]
Get:9 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages [574 kB]
Get:10 http://archive.ubuntu.com/ubuntu bionic-updates/main i386 Packages [488 kB]
Get:11 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 DEP-11 Metadata [278 kB]
Get:12 http://archive.ubuntu.com/ubuntu bionic-updates/main DEP-11 48x48 Icons [66,7 kB]
Get:13 http://archive.ubuntu.com/ubuntu bionic-updates/main DEP-11 64x64 Icons [123 kB]
Get:14 http://archive.ubuntu.com/ubuntu bionic-updates/universe amd64 Packages [756 kB]
Get:15 http://archive.ubuntu.com/ubuntu bionic-updates/universe i386 Packages [745 kB]
Get:16 http://archive.ubuntu.com/ubuntu bionic-updates/universe Translation-en [201 kB]
Get:17 http://archive.ubuntu.com/ubuntu bionic-updates/universe amd64 DEP-11 Metadata [209 kB]
Get:18 http://archive.ubuntu.com/ubuntu bionic-updates/universe DEP-11 48x48 Icons [191 kB]
Get:19 http://archive.ubuntu.com/ubuntu bionic-updates/universe DEP-11 64x64 Icons [360 kB]
Get:20 http://archive.ubuntu.com/ubuntu bionic-updates/multiverse amd64 DEP-11 Metadata [2.468 B]
Get:21 http://archive.ubuntu.com/ubuntu bionic-backports/universe amd64 DEP-11 Metadata [7.352 B]
Get:22 http://archive.ubuntu.com/ubuntu bionic-security/main amd64 Packages [296 kB]
Get:23 http://archive.ubuntu.com/ubuntu bionic-security/main i386 Packages [216 kB]
Get:24 http://archive.ubuntu.com/ubuntu bionic-security/main amd64 DEP-11 Metadata [204 B]
Get:25 http://archive.ubuntu.com/ubuntu bionic-security/universe i386 Packages [127 kB]
Get:26 http://archive.ubuntu.com/ubuntu bionic-security/universe amd64 Packages [131 kB]
Get:27 http://archive.ubuntu.com/ubuntu bionic-security/universe Translation-en [74,2 kB]
Get:28 http://archive.ubuntu.com/ubuntu bionic-security/universe amd64 DEP-11 Metadata [20,8 kB]
Get:29 http://archive.ubuntu.com/ubuntu bionic-security/universe DEP-11 48x48 Icons [12,2 kB]
Get:30 http://archive.ubuntu.com/ubuntu bionic-security/universe DEP-11 64x64 Icons [50,4 kB]
Get:31 http://archive.ubuntu.com/ubuntu bionic-security/multiverse amd64 DEP-11 Metadata [2.464 B]
Fetched 5.183 kB in 2s (2.131 kB/s)
Reading package lists... Done
Building dependency tree
Reading state information... Done
All packages are up to date.
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://dl.google.com/linux/chrome/deb stable Release: The following signatures were invalid: EXPKEYSIG 1397BC53640DB551 Google Inc. (Linux Packages Signing Authority) <linux-packages-keymaster@google.com>
W: Failed to fetch http://dl.google.com/linux/chrome/deb/dists/stable/Release.gpg The following signatures were invalid: EXPKEYSIG 1397BC53640DB551 Google Inc. (Linux Packages Signing Authority) <linux-packages-keymaster@google.com>
W: Some index files failed to download. They have been ignored, or old ones used instead.
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Reading package lists... Done
Building dependency tree
Reading state information... Done
All snaps up to date.



Already tried importing GPG key again with:



wget -q -O - https://dl-ssl.google.com/linux/linux_signing_key.pub | sudo apt-key add -


Source: Google Linux Software Repositories



EDIT: add error line in Spanish for better visibility:



Las siguientes firmas no fueron válidas: EXPKEYSIG 1397BC53640DB551 Google Inc. (Linux Packages Signing Authority) <linux-packages-keymaster@google.com>



EDIT2: and French (to cover top 3 languages):



Les signatures suivantes ne sont pas valables : EXPKEYSIG 1397BC53640DB551 Google Inc. (Linux Packages Signing Authority) <linux-packages-keymaster@google.com>










share|improve this question



















  • 11





    It just happened to me as well.

    – Fred
    Apr 12 at 8:04






  • 8





    upvote this link support.google.com/chrome/thread/4032170?hl=en and wait! We can do nothing more.

    – Carlos Alberto Silveira de And
    Apr 12 at 10:31







  • 1





    I've added a link to the bug report at the top of the post. Please feel free to move it or to delete it.

    – DK Bose
    Apr 12 at 17:01






  • 4





    I think it is fixed now

    – Leo
    Apr 12 at 17:26






  • 1





    This happened to me today, 8 days later and it's still happening.

    – Gregory Smitherman
    10 hours ago













90












90








90


23






This is Issue 952287: [User Feedback - Stable] Reports of Chrome for Linux failing to install/update due to expired GPG signing key




Today, running apt in all my machines gives this error with the Google PPA (for google-chrome):



me@mymachine:~$ sudo apt clean && sudo apt update && sudo apt full-upgrade -y && sudo apt autoremove -y && sudo apt autoclean -y && sudo snap refresh 
[sudo] password for me:
Ign:1 http://dl.google.com/linux/chrome/deb stable InRelease
Hit:2 http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu bionic InRelease
Hit:3 http://dl.google.com/linux/chrome/deb stable Release
Hit:4 http://archive.ubuntu.com/ubuntu bionic InRelease
Get:5 http://archive.ubuntu.com/ubuntu bionic-updates InRelease [88,7 kB]
Get:6 http://archive.ubuntu.com/ubuntu bionic-backports InRelease [74,6 kB]
Err:7 http://dl.google.com/linux/chrome/deb stable Release.gpg
The following signatures were invalid: EXPKEYSIG 1397BC53640DB551 Google Inc. (Linux Packages Signing Authority) <linux-packages-keymaster@google.com>
Get:8 http://archive.ubuntu.com/ubuntu bionic-security InRelease [88,7 kB]
Get:9 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages [574 kB]
Get:10 http://archive.ubuntu.com/ubuntu bionic-updates/main i386 Packages [488 kB]
Get:11 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 DEP-11 Metadata [278 kB]
Get:12 http://archive.ubuntu.com/ubuntu bionic-updates/main DEP-11 48x48 Icons [66,7 kB]
Get:13 http://archive.ubuntu.com/ubuntu bionic-updates/main DEP-11 64x64 Icons [123 kB]
Get:14 http://archive.ubuntu.com/ubuntu bionic-updates/universe amd64 Packages [756 kB]
Get:15 http://archive.ubuntu.com/ubuntu bionic-updates/universe i386 Packages [745 kB]
Get:16 http://archive.ubuntu.com/ubuntu bionic-updates/universe Translation-en [201 kB]
Get:17 http://archive.ubuntu.com/ubuntu bionic-updates/universe amd64 DEP-11 Metadata [209 kB]
Get:18 http://archive.ubuntu.com/ubuntu bionic-updates/universe DEP-11 48x48 Icons [191 kB]
Get:19 http://archive.ubuntu.com/ubuntu bionic-updates/universe DEP-11 64x64 Icons [360 kB]
Get:20 http://archive.ubuntu.com/ubuntu bionic-updates/multiverse amd64 DEP-11 Metadata [2.468 B]
Get:21 http://archive.ubuntu.com/ubuntu bionic-backports/universe amd64 DEP-11 Metadata [7.352 B]
Get:22 http://archive.ubuntu.com/ubuntu bionic-security/main amd64 Packages [296 kB]
Get:23 http://archive.ubuntu.com/ubuntu bionic-security/main i386 Packages [216 kB]
Get:24 http://archive.ubuntu.com/ubuntu bionic-security/main amd64 DEP-11 Metadata [204 B]
Get:25 http://archive.ubuntu.com/ubuntu bionic-security/universe i386 Packages [127 kB]
Get:26 http://archive.ubuntu.com/ubuntu bionic-security/universe amd64 Packages [131 kB]
Get:27 http://archive.ubuntu.com/ubuntu bionic-security/universe Translation-en [74,2 kB]
Get:28 http://archive.ubuntu.com/ubuntu bionic-security/universe amd64 DEP-11 Metadata [20,8 kB]
Get:29 http://archive.ubuntu.com/ubuntu bionic-security/universe DEP-11 48x48 Icons [12,2 kB]
Get:30 http://archive.ubuntu.com/ubuntu bionic-security/universe DEP-11 64x64 Icons [50,4 kB]
Get:31 http://archive.ubuntu.com/ubuntu bionic-security/multiverse amd64 DEP-11 Metadata [2.464 B]
Fetched 5.183 kB in 2s (2.131 kB/s)
Reading package lists... Done
Building dependency tree
Reading state information... Done
All packages are up to date.
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://dl.google.com/linux/chrome/deb stable Release: The following signatures were invalid: EXPKEYSIG 1397BC53640DB551 Google Inc. (Linux Packages Signing Authority) <linux-packages-keymaster@google.com>
W: Failed to fetch http://dl.google.com/linux/chrome/deb/dists/stable/Release.gpg The following signatures were invalid: EXPKEYSIG 1397BC53640DB551 Google Inc. (Linux Packages Signing Authority) <linux-packages-keymaster@google.com>
W: Some index files failed to download. They have been ignored, or old ones used instead.
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Reading package lists... Done
Building dependency tree
Reading state information... Done
All snaps up to date.



Already tried importing GPG key again with:



wget -q -O - https://dl-ssl.google.com/linux/linux_signing_key.pub | sudo apt-key add -


Source: Google Linux Software Repositories



EDIT: add error line in Spanish for better visibility:



Las siguientes firmas no fueron válidas: EXPKEYSIG 1397BC53640DB551 Google Inc. (Linux Packages Signing Authority) <linux-packages-keymaster@google.com>



EDIT2: and French (to cover top 3 languages):



Les signatures suivantes ne sont pas valables : EXPKEYSIG 1397BC53640DB551 Google Inc. (Linux Packages Signing Authority) <linux-packages-keymaster@google.com>










share|improve this question
















This is Issue 952287: [User Feedback - Stable] Reports of Chrome for Linux failing to install/update due to expired GPG signing key




Today, running apt in all my machines gives this error with the Google PPA (for google-chrome):



me@mymachine:~$ sudo apt clean && sudo apt update && sudo apt full-upgrade -y && sudo apt autoremove -y && sudo apt autoclean -y && sudo snap refresh 
[sudo] password for me:
Ign:1 http://dl.google.com/linux/chrome/deb stable InRelease
Hit:2 http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu bionic InRelease
Hit:3 http://dl.google.com/linux/chrome/deb stable Release
Hit:4 http://archive.ubuntu.com/ubuntu bionic InRelease
Get:5 http://archive.ubuntu.com/ubuntu bionic-updates InRelease [88,7 kB]
Get:6 http://archive.ubuntu.com/ubuntu bionic-backports InRelease [74,6 kB]
Err:7 http://dl.google.com/linux/chrome/deb stable Release.gpg
The following signatures were invalid: EXPKEYSIG 1397BC53640DB551 Google Inc. (Linux Packages Signing Authority) <linux-packages-keymaster@google.com>
Get:8 http://archive.ubuntu.com/ubuntu bionic-security InRelease [88,7 kB]
Get:9 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages [574 kB]
Get:10 http://archive.ubuntu.com/ubuntu bionic-updates/main i386 Packages [488 kB]
Get:11 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 DEP-11 Metadata [278 kB]
Get:12 http://archive.ubuntu.com/ubuntu bionic-updates/main DEP-11 48x48 Icons [66,7 kB]
Get:13 http://archive.ubuntu.com/ubuntu bionic-updates/main DEP-11 64x64 Icons [123 kB]
Get:14 http://archive.ubuntu.com/ubuntu bionic-updates/universe amd64 Packages [756 kB]
Get:15 http://archive.ubuntu.com/ubuntu bionic-updates/universe i386 Packages [745 kB]
Get:16 http://archive.ubuntu.com/ubuntu bionic-updates/universe Translation-en [201 kB]
Get:17 http://archive.ubuntu.com/ubuntu bionic-updates/universe amd64 DEP-11 Metadata [209 kB]
Get:18 http://archive.ubuntu.com/ubuntu bionic-updates/universe DEP-11 48x48 Icons [191 kB]
Get:19 http://archive.ubuntu.com/ubuntu bionic-updates/universe DEP-11 64x64 Icons [360 kB]
Get:20 http://archive.ubuntu.com/ubuntu bionic-updates/multiverse amd64 DEP-11 Metadata [2.468 B]
Get:21 http://archive.ubuntu.com/ubuntu bionic-backports/universe amd64 DEP-11 Metadata [7.352 B]
Get:22 http://archive.ubuntu.com/ubuntu bionic-security/main amd64 Packages [296 kB]
Get:23 http://archive.ubuntu.com/ubuntu bionic-security/main i386 Packages [216 kB]
Get:24 http://archive.ubuntu.com/ubuntu bionic-security/main amd64 DEP-11 Metadata [204 B]
Get:25 http://archive.ubuntu.com/ubuntu bionic-security/universe i386 Packages [127 kB]
Get:26 http://archive.ubuntu.com/ubuntu bionic-security/universe amd64 Packages [131 kB]
Get:27 http://archive.ubuntu.com/ubuntu bionic-security/universe Translation-en [74,2 kB]
Get:28 http://archive.ubuntu.com/ubuntu bionic-security/universe amd64 DEP-11 Metadata [20,8 kB]
Get:29 http://archive.ubuntu.com/ubuntu bionic-security/universe DEP-11 48x48 Icons [12,2 kB]
Get:30 http://archive.ubuntu.com/ubuntu bionic-security/universe DEP-11 64x64 Icons [50,4 kB]
Get:31 http://archive.ubuntu.com/ubuntu bionic-security/multiverse amd64 DEP-11 Metadata [2.464 B]
Fetched 5.183 kB in 2s (2.131 kB/s)
Reading package lists... Done
Building dependency tree
Reading state information... Done
All packages are up to date.
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://dl.google.com/linux/chrome/deb stable Release: The following signatures were invalid: EXPKEYSIG 1397BC53640DB551 Google Inc. (Linux Packages Signing Authority) <linux-packages-keymaster@google.com>
W: Failed to fetch http://dl.google.com/linux/chrome/deb/dists/stable/Release.gpg The following signatures were invalid: EXPKEYSIG 1397BC53640DB551 Google Inc. (Linux Packages Signing Authority) <linux-packages-keymaster@google.com>
W: Some index files failed to download. They have been ignored, or old ones used instead.
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Reading package lists... Done
Building dependency tree
Reading state information... Done
All snaps up to date.



Already tried importing GPG key again with:



wget -q -O - https://dl-ssl.google.com/linux/linux_signing_key.pub | sudo apt-key add -


Source: Google Linux Software Repositories



EDIT: add error line in Spanish for better visibility:



Las siguientes firmas no fueron válidas: EXPKEYSIG 1397BC53640DB551 Google Inc. (Linux Packages Signing Authority) <linux-packages-keymaster@google.com>



EDIT2: and French (to cover top 3 languages):



Les signatures suivantes ne sont pas valables : EXPKEYSIG 1397BC53640DB551 Google Inc. (Linux Packages Signing Authority) <linux-packages-keymaster@google.com>







apt 18.04 updates google-chrome ppa






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Apr 12 at 16:59









DK Bose

15.3k124389




15.3k124389










asked Apr 12 at 7:53









LeoLeo

3,08311232




3,08311232







  • 11





    It just happened to me as well.

    – Fred
    Apr 12 at 8:04






  • 8





    upvote this link support.google.com/chrome/thread/4032170?hl=en and wait! We can do nothing more.

    – Carlos Alberto Silveira de And
    Apr 12 at 10:31







  • 1





    I've added a link to the bug report at the top of the post. Please feel free to move it or to delete it.

    – DK Bose
    Apr 12 at 17:01






  • 4





    I think it is fixed now

    – Leo
    Apr 12 at 17:26






  • 1





    This happened to me today, 8 days later and it's still happening.

    – Gregory Smitherman
    10 hours ago












  • 11





    It just happened to me as well.

    – Fred
    Apr 12 at 8:04






  • 8





    upvote this link support.google.com/chrome/thread/4032170?hl=en and wait! We can do nothing more.

    – Carlos Alberto Silveira de And
    Apr 12 at 10:31







  • 1





    I've added a link to the bug report at the top of the post. Please feel free to move it or to delete it.

    – DK Bose
    Apr 12 at 17:01






  • 4





    I think it is fixed now

    – Leo
    Apr 12 at 17:26






  • 1





    This happened to me today, 8 days later and it's still happening.

    – Gregory Smitherman
    10 hours ago







11




11





It just happened to me as well.

– Fred
Apr 12 at 8:04





It just happened to me as well.

– Fred
Apr 12 at 8:04




8




8





upvote this link support.google.com/chrome/thread/4032170?hl=en and wait! We can do nothing more.

– Carlos Alberto Silveira de And
Apr 12 at 10:31






upvote this link support.google.com/chrome/thread/4032170?hl=en and wait! We can do nothing more.

– Carlos Alberto Silveira de And
Apr 12 at 10:31





1




1





I've added a link to the bug report at the top of the post. Please feel free to move it or to delete it.

– DK Bose
Apr 12 at 17:01





I've added a link to the bug report at the top of the post. Please feel free to move it or to delete it.

– DK Bose
Apr 12 at 17:01




4




4





I think it is fixed now

– Leo
Apr 12 at 17:26





I think it is fixed now

– Leo
Apr 12 at 17:26




1




1





This happened to me today, 8 days later and it's still happening.

– Gregory Smitherman
10 hours ago





This happened to me today, 8 days later and it's still happening.

– Gregory Smitherman
10 hours ago










9 Answers
9






active

oldest

votes


















63














This is the protection you are getting from these checks. You don't want to update your software right now while something is messed up on Google's end. Wait until they fix it. Don't try to override by reinstalling keys until some official word comes out that a new key is the solution.






share|improve this answer


















  • 9





    Waiting until they fix it may not be an option for all. E.g. this is breaking CI pipelines for us. If you now what you are doing, you might take the risk and disable checks for this repo for now by adding [trusted=yes] to it's configuration: deb [trusted=yes] http://dl.google.com/linux/chrome/deb/ stable main

    – jelhan
    Apr 12 at 8:48






  • 4





    It's not the first time this happens. I remember having this same issue with google at least 2 more times over the last years. I wonder what's going on at Google and why they can't keep their stuff together.

    – Michael Härtl
    Apr 12 at 9:48






  • 4





    @jelhan That’s why CI pipelines ideally tap into local mirrors/caches rather than going directly upstream.

    – Konrad Rudolph
    Apr 12 at 11:16






  • 2





    @MichaelHärtl I've been watching Google and meritocracy seems to be out of vogue.

    – DK Bose
    Apr 12 at 14:02






  • 5





    trusted=yes defeats the whole purpose of digital signing and basically compromise your whole system. You should not do that lightly, especially not a good idea for a "temporary workaround".

    – kissgyorgy
    Apr 12 at 16:49


















33














Apparently Google did not extend the validity of the signing cert...
it was due to end today and so it did.
https://pgp.surfnet.nl/pks/lookup?op=vindex&fingerprint=on&search=0x7721F63BD38B4796



maybe Google will change it, today or so… then the update of the cert should work fine and everything should go back to normal.






share|improve this answer






























    13














    the problem was solved by Google Abr 12/2019 (Only Google Chrome. Tested in Ubuntu 18.04.x)



    enter image description here
    There's nothing to do. The repository has already been signed



    Update apr 19/2019:



    enter image description here



    Google Team has confirmed that additional fixes have gone out for other non-Chrome Google products



    source: https://support.google.com/chrome/thread/4032170






    share|improve this answer

























    • Where did you report that? Google still hasn't fixed it on certain other repositories, e.g. the Music Manager, so I would like to report that as well.

      – Paddy Landau
      Apr 15 at 15:23


















    9














    Looks like Google's signing keys expired. Be patient and wait for them to fix them (which may or may not require re-adding the key after they fixed it).






    share|improve this answer






























      1














      For anyone not patient enough for google to update cert...



      you can fix this with the following steps :



      1. Download this : https://dl.google.com/linux/direct/google-chrome-stable_current_amd64.deb

      (chrome new version, you can get it yourself by googling chrome)



      1. Close Chrome.

      2. Open "Software and Sources", go to the "Sources" tab

      3. Remove (or disable if you wish to re-enable it at a later time) the Google source (type your password) and close the window

      4. Allow "Software and Sources" to reload sources

      5. Go into Software Center, go to "Installed"

      6. Find Chrome, uninstall it.

      7. Close software and sources


      8. Open a terminal, type :



        sudo apt update && sudo apt autoremove -y && sudo apt autoclean && sudo apt full-upgrade -y



      9. Close the terminal and go to your downloads folder and double click the file "google-chrome-stable_current_amd64.deb" (this will open Software Center)


      10. Click Install

      you can now open chrome back up. all your tabs and saved passwords ect are still there.






      share|improve this answer

























      • @CarlosAlbertoSilveiradeAnd said "Great!!, work for me! Thanks" but as an edit to my post because he doesn't know how to use this site yet.... I'm adding it so people know it worked for someone.

        – tatsu
        Apr 12 at 16:31


















      1














      April 15, and I'm still getting this error with the Google Earth and Music Manager repositories. They sure are taking their sweet time with this.






      share|improve this answer






























        0














        You don't. You must wait for Google to renew their keys and for an update.



        The important message is:




        The following signatures were invalid: EXPKEYSIG 1397BC53640DB551
        Google Inc. (Linux Packages Signing Authority)




        It means that the cryptographic signature is invalid. The source of this can be an attack, a misconfiguration, or other kind of technical problem. Forcing your system to update will result in running an unverified version of your web browser, which can expose you to a lot of security troubles.



        source






        share|improve this answer






























          0














          Google needs to update there GPG key. You can however mark the deb source as trusted, until Google renews their key:




          1. cd /var/lib/apt/lists

          2. sudo rm
            dl.google.com_linux_chrome_deb_dists_stable_main_binary-amd64_Packages
            dl.google.com_linux_chrome_deb_dists_stable_Release
            dl.google.com_linux_chrome_deb_dists_stable_Release.gpg


          3. add trusted=yes in your /etc/apt/sources.list.d/google-chrome.list file, for it to look like this: deb [arch=amd64, trusted=yes] https://dl.google.com/linux/chrome/deb/ stable main


          4. apt clean


          5. apt update


          You still get an invalid GPG error, but you can ignore it for now.



          NOTE: Be careful as this may bring security issues, on non trusted networks, when no https is used in the deb source link.



          EDIT: GPG warning no longer appears. Google has renewed their key. If you followed the solution above, just remove the trusted=yes part, then apt clean & finally apt update. You should no longer see any error :D






          share|improve this answer




















          • 2





            Don't do this. If for no other reason than the source being unencrypted. If you did this, forgot all about it and then strayed onto a bad network, it could easily intercept and subvert the Release, packages.list, and therefore essentially run anything it liked as root on your computer. It's not a good idea.

            – Oli
            Apr 12 at 12:51






          • 2





            You've missed my point. If somebody can intercept your network traffic, they can pretend to be Google. There's no TLS on a http:// connection. Normally Apt has your back here because they check that all release and package lists are signed. If you intercepted this normally —and maliciously changed something— you'd see a signing error. You're bypassing that whole mechanism here.

            – Oli
            Apr 12 at 13:29






          • 1





            Indeed. Thanks for the explanation

            – Dimitris Moraitidis
            Apr 12 at 13:39






          • 2





            Agreed, but you can temporarily just make it https with trusted=yes (for now, assuming you're not being TLS MiTM). For example: deb [arch=amd64, trusted=yes] https://dl.google.com/linux/chrome/deb/ stable main

            – link_boy
            Apr 12 at 14:27







          • 1





            Also indeed. So I guess my recent edit, I should at least go back to 0 instead of -2 :P

            – Dimitris Moraitidis
            Apr 12 at 14:33


















          0














          Looks like, as @DooMMasteR said, Google let signing cert expire for their Linux repositories, which due date was April 12th. @yareckon explained that this apt security error is working as expected to prevent badly signed software being installed.



          9 hours after the issue was posted, Google fixed certs transparently for the users using Google Chrome repo. The error stopped after they renewed the certs, progressively also on the rest of Google owned repos (Google Earth, Google Music Manager...).



          No action is needed (and recommended) from users side, just waiting for the repos in use to be signed with renewed keys.






          share|improve this answer























            protected by Community Apr 12 at 17:03



            Thank you for your interest in this question.
            Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).



            Would you like to answer one of these unanswered questions instead?














            9 Answers
            9






            active

            oldest

            votes








            9 Answers
            9






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            63














            This is the protection you are getting from these checks. You don't want to update your software right now while something is messed up on Google's end. Wait until they fix it. Don't try to override by reinstalling keys until some official word comes out that a new key is the solution.






            share|improve this answer


















            • 9





              Waiting until they fix it may not be an option for all. E.g. this is breaking CI pipelines for us. If you now what you are doing, you might take the risk and disable checks for this repo for now by adding [trusted=yes] to it's configuration: deb [trusted=yes] http://dl.google.com/linux/chrome/deb/ stable main

              – jelhan
              Apr 12 at 8:48






            • 4





              It's not the first time this happens. I remember having this same issue with google at least 2 more times over the last years. I wonder what's going on at Google and why they can't keep their stuff together.

              – Michael Härtl
              Apr 12 at 9:48






            • 4





              @jelhan That’s why CI pipelines ideally tap into local mirrors/caches rather than going directly upstream.

              – Konrad Rudolph
              Apr 12 at 11:16






            • 2





              @MichaelHärtl I've been watching Google and meritocracy seems to be out of vogue.

              – DK Bose
              Apr 12 at 14:02






            • 5





              trusted=yes defeats the whole purpose of digital signing and basically compromise your whole system. You should not do that lightly, especially not a good idea for a "temporary workaround".

              – kissgyorgy
              Apr 12 at 16:49















            63














            This is the protection you are getting from these checks. You don't want to update your software right now while something is messed up on Google's end. Wait until they fix it. Don't try to override by reinstalling keys until some official word comes out that a new key is the solution.






            share|improve this answer


















            • 9





              Waiting until they fix it may not be an option for all. E.g. this is breaking CI pipelines for us. If you now what you are doing, you might take the risk and disable checks for this repo for now by adding [trusted=yes] to it's configuration: deb [trusted=yes] http://dl.google.com/linux/chrome/deb/ stable main

              – jelhan
              Apr 12 at 8:48






            • 4





              It's not the first time this happens. I remember having this same issue with google at least 2 more times over the last years. I wonder what's going on at Google and why they can't keep their stuff together.

              – Michael Härtl
              Apr 12 at 9:48






            • 4





              @jelhan That’s why CI pipelines ideally tap into local mirrors/caches rather than going directly upstream.

              – Konrad Rudolph
              Apr 12 at 11:16






            • 2





              @MichaelHärtl I've been watching Google and meritocracy seems to be out of vogue.

              – DK Bose
              Apr 12 at 14:02






            • 5





              trusted=yes defeats the whole purpose of digital signing and basically compromise your whole system. You should not do that lightly, especially not a good idea for a "temporary workaround".

              – kissgyorgy
              Apr 12 at 16:49













            63












            63








            63







            This is the protection you are getting from these checks. You don't want to update your software right now while something is messed up on Google's end. Wait until they fix it. Don't try to override by reinstalling keys until some official word comes out that a new key is the solution.






            share|improve this answer













            This is the protection you are getting from these checks. You don't want to update your software right now while something is messed up on Google's end. Wait until they fix it. Don't try to override by reinstalling keys until some official word comes out that a new key is the solution.







            share|improve this answer












            share|improve this answer



            share|improve this answer










            answered Apr 12 at 8:08









            yareckonyareckon

            41113




            41113







            • 9





              Waiting until they fix it may not be an option for all. E.g. this is breaking CI pipelines for us. If you now what you are doing, you might take the risk and disable checks for this repo for now by adding [trusted=yes] to it's configuration: deb [trusted=yes] http://dl.google.com/linux/chrome/deb/ stable main

              – jelhan
              Apr 12 at 8:48






            • 4





              It's not the first time this happens. I remember having this same issue with google at least 2 more times over the last years. I wonder what's going on at Google and why they can't keep their stuff together.

              – Michael Härtl
              Apr 12 at 9:48






            • 4





              @jelhan That’s why CI pipelines ideally tap into local mirrors/caches rather than going directly upstream.

              – Konrad Rudolph
              Apr 12 at 11:16






            • 2





              @MichaelHärtl I've been watching Google and meritocracy seems to be out of vogue.

              – DK Bose
              Apr 12 at 14:02






            • 5





              trusted=yes defeats the whole purpose of digital signing and basically compromise your whole system. You should not do that lightly, especially not a good idea for a "temporary workaround".

              – kissgyorgy
              Apr 12 at 16:49












            • 9





              Waiting until they fix it may not be an option for all. E.g. this is breaking CI pipelines for us. If you now what you are doing, you might take the risk and disable checks for this repo for now by adding [trusted=yes] to it's configuration: deb [trusted=yes] http://dl.google.com/linux/chrome/deb/ stable main

              – jelhan
              Apr 12 at 8:48






            • 4





              It's not the first time this happens. I remember having this same issue with google at least 2 more times over the last years. I wonder what's going on at Google and why they can't keep their stuff together.

              – Michael Härtl
              Apr 12 at 9:48






            • 4





              @jelhan That’s why CI pipelines ideally tap into local mirrors/caches rather than going directly upstream.

              – Konrad Rudolph
              Apr 12 at 11:16






            • 2





              @MichaelHärtl I've been watching Google and meritocracy seems to be out of vogue.

              – DK Bose
              Apr 12 at 14:02






            • 5





              trusted=yes defeats the whole purpose of digital signing and basically compromise your whole system. You should not do that lightly, especially not a good idea for a "temporary workaround".

              – kissgyorgy
              Apr 12 at 16:49







            9




            9





            Waiting until they fix it may not be an option for all. E.g. this is breaking CI pipelines for us. If you now what you are doing, you might take the risk and disable checks for this repo for now by adding [trusted=yes] to it's configuration: deb [trusted=yes] http://dl.google.com/linux/chrome/deb/ stable main

            – jelhan
            Apr 12 at 8:48





            Waiting until they fix it may not be an option for all. E.g. this is breaking CI pipelines for us. If you now what you are doing, you might take the risk and disable checks for this repo for now by adding [trusted=yes] to it's configuration: deb [trusted=yes] http://dl.google.com/linux/chrome/deb/ stable main

            – jelhan
            Apr 12 at 8:48




            4




            4





            It's not the first time this happens. I remember having this same issue with google at least 2 more times over the last years. I wonder what's going on at Google and why they can't keep their stuff together.

            – Michael Härtl
            Apr 12 at 9:48





            It's not the first time this happens. I remember having this same issue with google at least 2 more times over the last years. I wonder what's going on at Google and why they can't keep their stuff together.

            – Michael Härtl
            Apr 12 at 9:48




            4




            4





            @jelhan That’s why CI pipelines ideally tap into local mirrors/caches rather than going directly upstream.

            – Konrad Rudolph
            Apr 12 at 11:16





            @jelhan That’s why CI pipelines ideally tap into local mirrors/caches rather than going directly upstream.

            – Konrad Rudolph
            Apr 12 at 11:16




            2




            2





            @MichaelHärtl I've been watching Google and meritocracy seems to be out of vogue.

            – DK Bose
            Apr 12 at 14:02





            @MichaelHärtl I've been watching Google and meritocracy seems to be out of vogue.

            – DK Bose
            Apr 12 at 14:02




            5




            5





            trusted=yes defeats the whole purpose of digital signing and basically compromise your whole system. You should not do that lightly, especially not a good idea for a "temporary workaround".

            – kissgyorgy
            Apr 12 at 16:49





            trusted=yes defeats the whole purpose of digital signing and basically compromise your whole system. You should not do that lightly, especially not a good idea for a "temporary workaround".

            – kissgyorgy
            Apr 12 at 16:49













            33














            Apparently Google did not extend the validity of the signing cert...
            it was due to end today and so it did.
            https://pgp.surfnet.nl/pks/lookup?op=vindex&fingerprint=on&search=0x7721F63BD38B4796



            maybe Google will change it, today or so… then the update of the cert should work fine and everything should go back to normal.






            share|improve this answer



























              33














              Apparently Google did not extend the validity of the signing cert...
              it was due to end today and so it did.
              https://pgp.surfnet.nl/pks/lookup?op=vindex&fingerprint=on&search=0x7721F63BD38B4796



              maybe Google will change it, today or so… then the update of the cert should work fine and everything should go back to normal.






              share|improve this answer

























                33












                33








                33







                Apparently Google did not extend the validity of the signing cert...
                it was due to end today and so it did.
                https://pgp.surfnet.nl/pks/lookup?op=vindex&fingerprint=on&search=0x7721F63BD38B4796



                maybe Google will change it, today or so… then the update of the cert should work fine and everything should go back to normal.






                share|improve this answer













                Apparently Google did not extend the validity of the signing cert...
                it was due to end today and so it did.
                https://pgp.surfnet.nl/pks/lookup?op=vindex&fingerprint=on&search=0x7721F63BD38B4796



                maybe Google will change it, today or so… then the update of the cert should work fine and everything should go back to normal.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Apr 12 at 8:16









                DooMMasteRDooMMasteR

                34125




                34125





















                    13














                    the problem was solved by Google Abr 12/2019 (Only Google Chrome. Tested in Ubuntu 18.04.x)



                    enter image description here
                    There's nothing to do. The repository has already been signed



                    Update apr 19/2019:



                    enter image description here



                    Google Team has confirmed that additional fixes have gone out for other non-Chrome Google products



                    source: https://support.google.com/chrome/thread/4032170






                    share|improve this answer

























                    • Where did you report that? Google still hasn't fixed it on certain other repositories, e.g. the Music Manager, so I would like to report that as well.

                      – Paddy Landau
                      Apr 15 at 15:23















                    13














                    the problem was solved by Google Abr 12/2019 (Only Google Chrome. Tested in Ubuntu 18.04.x)



                    enter image description here
                    There's nothing to do. The repository has already been signed



                    Update apr 19/2019:



                    enter image description here



                    Google Team has confirmed that additional fixes have gone out for other non-Chrome Google products



                    source: https://support.google.com/chrome/thread/4032170






                    share|improve this answer

























                    • Where did you report that? Google still hasn't fixed it on certain other repositories, e.g. the Music Manager, so I would like to report that as well.

                      – Paddy Landau
                      Apr 15 at 15:23













                    13












                    13








                    13







                    the problem was solved by Google Abr 12/2019 (Only Google Chrome. Tested in Ubuntu 18.04.x)



                    enter image description here
                    There's nothing to do. The repository has already been signed



                    Update apr 19/2019:



                    enter image description here



                    Google Team has confirmed that additional fixes have gone out for other non-Chrome Google products



                    source: https://support.google.com/chrome/thread/4032170






                    share|improve this answer















                    the problem was solved by Google Abr 12/2019 (Only Google Chrome. Tested in Ubuntu 18.04.x)



                    enter image description here
                    There's nothing to do. The repository has already been signed



                    Update apr 19/2019:



                    enter image description here



                    Google Team has confirmed that additional fixes have gone out for other non-Chrome Google products



                    source: https://support.google.com/chrome/thread/4032170







                    share|improve this answer














                    share|improve this answer



                    share|improve this answer








                    edited yesterday

























                    answered Apr 12 at 18:59









                    ajcgajcg

                    907412




                    907412












                    • Where did you report that? Google still hasn't fixed it on certain other repositories, e.g. the Music Manager, so I would like to report that as well.

                      – Paddy Landau
                      Apr 15 at 15:23

















                    • Where did you report that? Google still hasn't fixed it on certain other repositories, e.g. the Music Manager, so I would like to report that as well.

                      – Paddy Landau
                      Apr 15 at 15:23
















                    Where did you report that? Google still hasn't fixed it on certain other repositories, e.g. the Music Manager, so I would like to report that as well.

                    – Paddy Landau
                    Apr 15 at 15:23





                    Where did you report that? Google still hasn't fixed it on certain other repositories, e.g. the Music Manager, so I would like to report that as well.

                    – Paddy Landau
                    Apr 15 at 15:23











                    9














                    Looks like Google's signing keys expired. Be patient and wait for them to fix them (which may or may not require re-adding the key after they fixed it).






                    share|improve this answer



























                      9














                      Looks like Google's signing keys expired. Be patient and wait for them to fix them (which may or may not require re-adding the key after they fixed it).






                      share|improve this answer

























                        9












                        9








                        9







                        Looks like Google's signing keys expired. Be patient and wait for them to fix them (which may or may not require re-adding the key after they fixed it).






                        share|improve this answer













                        Looks like Google's signing keys expired. Be patient and wait for them to fix them (which may or may not require re-adding the key after they fixed it).







                        share|improve this answer












                        share|improve this answer



                        share|improve this answer










                        answered Apr 12 at 8:10









                        paed808paed808

                        404310




                        404310





















                            1














                            For anyone not patient enough for google to update cert...



                            you can fix this with the following steps :



                            1. Download this : https://dl.google.com/linux/direct/google-chrome-stable_current_amd64.deb

                            (chrome new version, you can get it yourself by googling chrome)



                            1. Close Chrome.

                            2. Open "Software and Sources", go to the "Sources" tab

                            3. Remove (or disable if you wish to re-enable it at a later time) the Google source (type your password) and close the window

                            4. Allow "Software and Sources" to reload sources

                            5. Go into Software Center, go to "Installed"

                            6. Find Chrome, uninstall it.

                            7. Close software and sources


                            8. Open a terminal, type :



                              sudo apt update && sudo apt autoremove -y && sudo apt autoclean && sudo apt full-upgrade -y



                            9. Close the terminal and go to your downloads folder and double click the file "google-chrome-stable_current_amd64.deb" (this will open Software Center)


                            10. Click Install

                            you can now open chrome back up. all your tabs and saved passwords ect are still there.






                            share|improve this answer

























                            • @CarlosAlbertoSilveiradeAnd said "Great!!, work for me! Thanks" but as an edit to my post because he doesn't know how to use this site yet.... I'm adding it so people know it worked for someone.

                              – tatsu
                              Apr 12 at 16:31















                            1














                            For anyone not patient enough for google to update cert...



                            you can fix this with the following steps :



                            1. Download this : https://dl.google.com/linux/direct/google-chrome-stable_current_amd64.deb

                            (chrome new version, you can get it yourself by googling chrome)



                            1. Close Chrome.

                            2. Open "Software and Sources", go to the "Sources" tab

                            3. Remove (or disable if you wish to re-enable it at a later time) the Google source (type your password) and close the window

                            4. Allow "Software and Sources" to reload sources

                            5. Go into Software Center, go to "Installed"

                            6. Find Chrome, uninstall it.

                            7. Close software and sources


                            8. Open a terminal, type :



                              sudo apt update && sudo apt autoremove -y && sudo apt autoclean && sudo apt full-upgrade -y



                            9. Close the terminal and go to your downloads folder and double click the file "google-chrome-stable_current_amd64.deb" (this will open Software Center)


                            10. Click Install

                            you can now open chrome back up. all your tabs and saved passwords ect are still there.






                            share|improve this answer

























                            • @CarlosAlbertoSilveiradeAnd said "Great!!, work for me! Thanks" but as an edit to my post because he doesn't know how to use this site yet.... I'm adding it so people know it worked for someone.

                              – tatsu
                              Apr 12 at 16:31













                            1












                            1








                            1







                            For anyone not patient enough for google to update cert...



                            you can fix this with the following steps :



                            1. Download this : https://dl.google.com/linux/direct/google-chrome-stable_current_amd64.deb

                            (chrome new version, you can get it yourself by googling chrome)



                            1. Close Chrome.

                            2. Open "Software and Sources", go to the "Sources" tab

                            3. Remove (or disable if you wish to re-enable it at a later time) the Google source (type your password) and close the window

                            4. Allow "Software and Sources" to reload sources

                            5. Go into Software Center, go to "Installed"

                            6. Find Chrome, uninstall it.

                            7. Close software and sources


                            8. Open a terminal, type :



                              sudo apt update && sudo apt autoremove -y && sudo apt autoclean && sudo apt full-upgrade -y



                            9. Close the terminal and go to your downloads folder and double click the file "google-chrome-stable_current_amd64.deb" (this will open Software Center)


                            10. Click Install

                            you can now open chrome back up. all your tabs and saved passwords ect are still there.






                            share|improve this answer















                            For anyone not patient enough for google to update cert...



                            you can fix this with the following steps :



                            1. Download this : https://dl.google.com/linux/direct/google-chrome-stable_current_amd64.deb

                            (chrome new version, you can get it yourself by googling chrome)



                            1. Close Chrome.

                            2. Open "Software and Sources", go to the "Sources" tab

                            3. Remove (or disable if you wish to re-enable it at a later time) the Google source (type your password) and close the window

                            4. Allow "Software and Sources" to reload sources

                            5. Go into Software Center, go to "Installed"

                            6. Find Chrome, uninstall it.

                            7. Close software and sources


                            8. Open a terminal, type :



                              sudo apt update && sudo apt autoremove -y && sudo apt autoclean && sudo apt full-upgrade -y



                            9. Close the terminal and go to your downloads folder and double click the file "google-chrome-stable_current_amd64.deb" (this will open Software Center)


                            10. Click Install

                            you can now open chrome back up. all your tabs and saved passwords ect are still there.







                            share|improve this answer














                            share|improve this answer



                            share|improve this answer








                            edited Apr 13 at 18:46

























                            answered Apr 12 at 13:35









                            tatsutatsu

                            561734




                            561734












                            • @CarlosAlbertoSilveiradeAnd said "Great!!, work for me! Thanks" but as an edit to my post because he doesn't know how to use this site yet.... I'm adding it so people know it worked for someone.

                              – tatsu
                              Apr 12 at 16:31

















                            • @CarlosAlbertoSilveiradeAnd said "Great!!, work for me! Thanks" but as an edit to my post because he doesn't know how to use this site yet.... I'm adding it so people know it worked for someone.

                              – tatsu
                              Apr 12 at 16:31
















                            @CarlosAlbertoSilveiradeAnd said "Great!!, work for me! Thanks" but as an edit to my post because he doesn't know how to use this site yet.... I'm adding it so people know it worked for someone.

                            – tatsu
                            Apr 12 at 16:31





                            @CarlosAlbertoSilveiradeAnd said "Great!!, work for me! Thanks" but as an edit to my post because he doesn't know how to use this site yet.... I'm adding it so people know it worked for someone.

                            – tatsu
                            Apr 12 at 16:31











                            1














                            April 15, and I'm still getting this error with the Google Earth and Music Manager repositories. They sure are taking their sweet time with this.






                            share|improve this answer



























                              1














                              April 15, and I'm still getting this error with the Google Earth and Music Manager repositories. They sure are taking their sweet time with this.






                              share|improve this answer

























                                1












                                1








                                1







                                April 15, and I'm still getting this error with the Google Earth and Music Manager repositories. They sure are taking their sweet time with this.






                                share|improve this answer













                                April 15, and I'm still getting this error with the Google Earth and Music Manager repositories. They sure are taking their sweet time with this.







                                share|improve this answer












                                share|improve this answer



                                share|improve this answer










                                answered Apr 15 at 23:24









                                MikeFMikeF

                                263




                                263





















                                    0














                                    You don't. You must wait for Google to renew their keys and for an update.



                                    The important message is:




                                    The following signatures were invalid: EXPKEYSIG 1397BC53640DB551
                                    Google Inc. (Linux Packages Signing Authority)




                                    It means that the cryptographic signature is invalid. The source of this can be an attack, a misconfiguration, or other kind of technical problem. Forcing your system to update will result in running an unverified version of your web browser, which can expose you to a lot of security troubles.



                                    source






                                    share|improve this answer



























                                      0














                                      You don't. You must wait for Google to renew their keys and for an update.



                                      The important message is:




                                      The following signatures were invalid: EXPKEYSIG 1397BC53640DB551
                                      Google Inc. (Linux Packages Signing Authority)




                                      It means that the cryptographic signature is invalid. The source of this can be an attack, a misconfiguration, or other kind of technical problem. Forcing your system to update will result in running an unverified version of your web browser, which can expose you to a lot of security troubles.



                                      source






                                      share|improve this answer

























                                        0












                                        0








                                        0







                                        You don't. You must wait for Google to renew their keys and for an update.



                                        The important message is:




                                        The following signatures were invalid: EXPKEYSIG 1397BC53640DB551
                                        Google Inc. (Linux Packages Signing Authority)




                                        It means that the cryptographic signature is invalid. The source of this can be an attack, a misconfiguration, or other kind of technical problem. Forcing your system to update will result in running an unverified version of your web browser, which can expose you to a lot of security troubles.



                                        source






                                        share|improve this answer













                                        You don't. You must wait for Google to renew their keys and for an update.



                                        The important message is:




                                        The following signatures were invalid: EXPKEYSIG 1397BC53640DB551
                                        Google Inc. (Linux Packages Signing Authority)




                                        It means that the cryptographic signature is invalid. The source of this can be an attack, a misconfiguration, or other kind of technical problem. Forcing your system to update will result in running an unverified version of your web browser, which can expose you to a lot of security troubles.



                                        source







                                        share|improve this answer












                                        share|improve this answer



                                        share|improve this answer










                                        answered Apr 12 at 17:03









                                        sxnsxn

                                        11




                                        11





















                                            0














                                            Google needs to update there GPG key. You can however mark the deb source as trusted, until Google renews their key:




                                            1. cd /var/lib/apt/lists

                                            2. sudo rm
                                              dl.google.com_linux_chrome_deb_dists_stable_main_binary-amd64_Packages
                                              dl.google.com_linux_chrome_deb_dists_stable_Release
                                              dl.google.com_linux_chrome_deb_dists_stable_Release.gpg


                                            3. add trusted=yes in your /etc/apt/sources.list.d/google-chrome.list file, for it to look like this: deb [arch=amd64, trusted=yes] https://dl.google.com/linux/chrome/deb/ stable main


                                            4. apt clean


                                            5. apt update


                                            You still get an invalid GPG error, but you can ignore it for now.



                                            NOTE: Be careful as this may bring security issues, on non trusted networks, when no https is used in the deb source link.



                                            EDIT: GPG warning no longer appears. Google has renewed their key. If you followed the solution above, just remove the trusted=yes part, then apt clean & finally apt update. You should no longer see any error :D






                                            share|improve this answer




















                                            • 2





                                              Don't do this. If for no other reason than the source being unencrypted. If you did this, forgot all about it and then strayed onto a bad network, it could easily intercept and subvert the Release, packages.list, and therefore essentially run anything it liked as root on your computer. It's not a good idea.

                                              – Oli
                                              Apr 12 at 12:51






                                            • 2





                                              You've missed my point. If somebody can intercept your network traffic, they can pretend to be Google. There's no TLS on a http:// connection. Normally Apt has your back here because they check that all release and package lists are signed. If you intercepted this normally —and maliciously changed something— you'd see a signing error. You're bypassing that whole mechanism here.

                                              – Oli
                                              Apr 12 at 13:29






                                            • 1





                                              Indeed. Thanks for the explanation

                                              – Dimitris Moraitidis
                                              Apr 12 at 13:39






                                            • 2





                                              Agreed, but you can temporarily just make it https with trusted=yes (for now, assuming you're not being TLS MiTM). For example: deb [arch=amd64, trusted=yes] https://dl.google.com/linux/chrome/deb/ stable main

                                              – link_boy
                                              Apr 12 at 14:27







                                            • 1





                                              Also indeed. So I guess my recent edit, I should at least go back to 0 instead of -2 :P

                                              – Dimitris Moraitidis
                                              Apr 12 at 14:33















                                            0














                                            Google needs to update there GPG key. You can however mark the deb source as trusted, until Google renews their key:




                                            1. cd /var/lib/apt/lists

                                            2. sudo rm
                                              dl.google.com_linux_chrome_deb_dists_stable_main_binary-amd64_Packages
                                              dl.google.com_linux_chrome_deb_dists_stable_Release
                                              dl.google.com_linux_chrome_deb_dists_stable_Release.gpg


                                            3. add trusted=yes in your /etc/apt/sources.list.d/google-chrome.list file, for it to look like this: deb [arch=amd64, trusted=yes] https://dl.google.com/linux/chrome/deb/ stable main


                                            4. apt clean


                                            5. apt update


                                            You still get an invalid GPG error, but you can ignore it for now.



                                            NOTE: Be careful as this may bring security issues, on non trusted networks, when no https is used in the deb source link.



                                            EDIT: GPG warning no longer appears. Google has renewed their key. If you followed the solution above, just remove the trusted=yes part, then apt clean & finally apt update. You should no longer see any error :D






                                            share|improve this answer




















                                            • 2





                                              Don't do this. If for no other reason than the source being unencrypted. If you did this, forgot all about it and then strayed onto a bad network, it could easily intercept and subvert the Release, packages.list, and therefore essentially run anything it liked as root on your computer. It's not a good idea.

                                              – Oli
                                              Apr 12 at 12:51






                                            • 2





                                              You've missed my point. If somebody can intercept your network traffic, they can pretend to be Google. There's no TLS on a http:// connection. Normally Apt has your back here because they check that all release and package lists are signed. If you intercepted this normally —and maliciously changed something— you'd see a signing error. You're bypassing that whole mechanism here.

                                              – Oli
                                              Apr 12 at 13:29






                                            • 1





                                              Indeed. Thanks for the explanation

                                              – Dimitris Moraitidis
                                              Apr 12 at 13:39






                                            • 2





                                              Agreed, but you can temporarily just make it https with trusted=yes (for now, assuming you're not being TLS MiTM). For example: deb [arch=amd64, trusted=yes] https://dl.google.com/linux/chrome/deb/ stable main

                                              – link_boy
                                              Apr 12 at 14:27







                                            • 1





                                              Also indeed. So I guess my recent edit, I should at least go back to 0 instead of -2 :P

                                              – Dimitris Moraitidis
                                              Apr 12 at 14:33













                                            0












                                            0








                                            0







                                            Google needs to update there GPG key. You can however mark the deb source as trusted, until Google renews their key:




                                            1. cd /var/lib/apt/lists

                                            2. sudo rm
                                              dl.google.com_linux_chrome_deb_dists_stable_main_binary-amd64_Packages
                                              dl.google.com_linux_chrome_deb_dists_stable_Release
                                              dl.google.com_linux_chrome_deb_dists_stable_Release.gpg


                                            3. add trusted=yes in your /etc/apt/sources.list.d/google-chrome.list file, for it to look like this: deb [arch=amd64, trusted=yes] https://dl.google.com/linux/chrome/deb/ stable main


                                            4. apt clean


                                            5. apt update


                                            You still get an invalid GPG error, but you can ignore it for now.



                                            NOTE: Be careful as this may bring security issues, on non trusted networks, when no https is used in the deb source link.



                                            EDIT: GPG warning no longer appears. Google has renewed their key. If you followed the solution above, just remove the trusted=yes part, then apt clean & finally apt update. You should no longer see any error :D






                                            share|improve this answer















                                            Google needs to update there GPG key. You can however mark the deb source as trusted, until Google renews their key:




                                            1. cd /var/lib/apt/lists

                                            2. sudo rm
                                              dl.google.com_linux_chrome_deb_dists_stable_main_binary-amd64_Packages
                                              dl.google.com_linux_chrome_deb_dists_stable_Release
                                              dl.google.com_linux_chrome_deb_dists_stable_Release.gpg


                                            3. add trusted=yes in your /etc/apt/sources.list.d/google-chrome.list file, for it to look like this: deb [arch=amd64, trusted=yes] https://dl.google.com/linux/chrome/deb/ stable main


                                            4. apt clean


                                            5. apt update


                                            You still get an invalid GPG error, but you can ignore it for now.



                                            NOTE: Be careful as this may bring security issues, on non trusted networks, when no https is used in the deb source link.



                                            EDIT: GPG warning no longer appears. Google has renewed their key. If you followed the solution above, just remove the trusted=yes part, then apt clean & finally apt update. You should no longer see any error :D







                                            share|improve this answer














                                            share|improve this answer



                                            share|improve this answer








                                            edited Apr 12 at 20:40

























                                            answered Apr 12 at 10:00









                                            Dimitris MoraitidisDimitris Moraitidis

                                            386




                                            386







                                            • 2





                                              Don't do this. If for no other reason than the source being unencrypted. If you did this, forgot all about it and then strayed onto a bad network, it could easily intercept and subvert the Release, packages.list, and therefore essentially run anything it liked as root on your computer. It's not a good idea.

                                              – Oli
                                              Apr 12 at 12:51






                                            • 2





                                              You've missed my point. If somebody can intercept your network traffic, they can pretend to be Google. There's no TLS on a http:// connection. Normally Apt has your back here because they check that all release and package lists are signed. If you intercepted this normally —and maliciously changed something— you'd see a signing error. You're bypassing that whole mechanism here.

                                              – Oli
                                              Apr 12 at 13:29






                                            • 1





                                              Indeed. Thanks for the explanation

                                              – Dimitris Moraitidis
                                              Apr 12 at 13:39






                                            • 2





                                              Agreed, but you can temporarily just make it https with trusted=yes (for now, assuming you're not being TLS MiTM). For example: deb [arch=amd64, trusted=yes] https://dl.google.com/linux/chrome/deb/ stable main

                                              – link_boy
                                              Apr 12 at 14:27







                                            • 1





                                              Also indeed. So I guess my recent edit, I should at least go back to 0 instead of -2 :P

                                              – Dimitris Moraitidis
                                              Apr 12 at 14:33












                                            • 2





                                              Don't do this. If for no other reason than the source being unencrypted. If you did this, forgot all about it and then strayed onto a bad network, it could easily intercept and subvert the Release, packages.list, and therefore essentially run anything it liked as root on your computer. It's not a good idea.

                                              – Oli
                                              Apr 12 at 12:51






                                            • 2





                                              You've missed my point. If somebody can intercept your network traffic, they can pretend to be Google. There's no TLS on a http:// connection. Normally Apt has your back here because they check that all release and package lists are signed. If you intercepted this normally —and maliciously changed something— you'd see a signing error. You're bypassing that whole mechanism here.

                                              – Oli
                                              Apr 12 at 13:29






                                            • 1





                                              Indeed. Thanks for the explanation

                                              – Dimitris Moraitidis
                                              Apr 12 at 13:39






                                            • 2





                                              Agreed, but you can temporarily just make it https with trusted=yes (for now, assuming you're not being TLS MiTM). For example: deb [arch=amd64, trusted=yes] https://dl.google.com/linux/chrome/deb/ stable main

                                              – link_boy
                                              Apr 12 at 14:27







                                            • 1





                                              Also indeed. So I guess my recent edit, I should at least go back to 0 instead of -2 :P

                                              – Dimitris Moraitidis
                                              Apr 12 at 14:33







                                            2




                                            2





                                            Don't do this. If for no other reason than the source being unencrypted. If you did this, forgot all about it and then strayed onto a bad network, it could easily intercept and subvert the Release, packages.list, and therefore essentially run anything it liked as root on your computer. It's not a good idea.

                                            – Oli
                                            Apr 12 at 12:51





                                            Don't do this. If for no other reason than the source being unencrypted. If you did this, forgot all about it and then strayed onto a bad network, it could easily intercept and subvert the Release, packages.list, and therefore essentially run anything it liked as root on your computer. It's not a good idea.

                                            – Oli
                                            Apr 12 at 12:51




                                            2




                                            2





                                            You've missed my point. If somebody can intercept your network traffic, they can pretend to be Google. There's no TLS on a http:// connection. Normally Apt has your back here because they check that all release and package lists are signed. If you intercepted this normally —and maliciously changed something— you'd see a signing error. You're bypassing that whole mechanism here.

                                            – Oli
                                            Apr 12 at 13:29





                                            You've missed my point. If somebody can intercept your network traffic, they can pretend to be Google. There's no TLS on a http:// connection. Normally Apt has your back here because they check that all release and package lists are signed. If you intercepted this normally —and maliciously changed something— you'd see a signing error. You're bypassing that whole mechanism here.

                                            – Oli
                                            Apr 12 at 13:29




                                            1




                                            1





                                            Indeed. Thanks for the explanation

                                            – Dimitris Moraitidis
                                            Apr 12 at 13:39





                                            Indeed. Thanks for the explanation

                                            – Dimitris Moraitidis
                                            Apr 12 at 13:39




                                            2




                                            2





                                            Agreed, but you can temporarily just make it https with trusted=yes (for now, assuming you're not being TLS MiTM). For example: deb [arch=amd64, trusted=yes] https://dl.google.com/linux/chrome/deb/ stable main

                                            – link_boy
                                            Apr 12 at 14:27






                                            Agreed, but you can temporarily just make it https with trusted=yes (for now, assuming you're not being TLS MiTM). For example: deb [arch=amd64, trusted=yes] https://dl.google.com/linux/chrome/deb/ stable main

                                            – link_boy
                                            Apr 12 at 14:27





                                            1




                                            1





                                            Also indeed. So I guess my recent edit, I should at least go back to 0 instead of -2 :P

                                            – Dimitris Moraitidis
                                            Apr 12 at 14:33





                                            Also indeed. So I guess my recent edit, I should at least go back to 0 instead of -2 :P

                                            – Dimitris Moraitidis
                                            Apr 12 at 14:33











                                            0














                                            Looks like, as @DooMMasteR said, Google let signing cert expire for their Linux repositories, which due date was April 12th. @yareckon explained that this apt security error is working as expected to prevent badly signed software being installed.



                                            9 hours after the issue was posted, Google fixed certs transparently for the users using Google Chrome repo. The error stopped after they renewed the certs, progressively also on the rest of Google owned repos (Google Earth, Google Music Manager...).



                                            No action is needed (and recommended) from users side, just waiting for the repos in use to be signed with renewed keys.






                                            share|improve this answer





























                                              0














                                              Looks like, as @DooMMasteR said, Google let signing cert expire for their Linux repositories, which due date was April 12th. @yareckon explained that this apt security error is working as expected to prevent badly signed software being installed.



                                              9 hours after the issue was posted, Google fixed certs transparently for the users using Google Chrome repo. The error stopped after they renewed the certs, progressively also on the rest of Google owned repos (Google Earth, Google Music Manager...).



                                              No action is needed (and recommended) from users side, just waiting for the repos in use to be signed with renewed keys.






                                              share|improve this answer



























                                                0












                                                0








                                                0







                                                Looks like, as @DooMMasteR said, Google let signing cert expire for their Linux repositories, which due date was April 12th. @yareckon explained that this apt security error is working as expected to prevent badly signed software being installed.



                                                9 hours after the issue was posted, Google fixed certs transparently for the users using Google Chrome repo. The error stopped after they renewed the certs, progressively also on the rest of Google owned repos (Google Earth, Google Music Manager...).



                                                No action is needed (and recommended) from users side, just waiting for the repos in use to be signed with renewed keys.






                                                share|improve this answer















                                                Looks like, as @DooMMasteR said, Google let signing cert expire for their Linux repositories, which due date was April 12th. @yareckon explained that this apt security error is working as expected to prevent badly signed software being installed.



                                                9 hours after the issue was posted, Google fixed certs transparently for the users using Google Chrome repo. The error stopped after they renewed the certs, progressively also on the rest of Google owned repos (Google Earth, Google Music Manager...).



                                                No action is needed (and recommended) from users side, just waiting for the repos in use to be signed with renewed keys.







                                                share|improve this answer














                                                share|improve this answer



                                                share|improve this answer








                                                edited 11 hours ago

























                                                answered Apr 13 at 17:02









                                                LeoLeo

                                                3,08311232




                                                3,08311232















                                                    protected by Community Apr 12 at 17:03



                                                    Thank you for your interest in this question.
                                                    Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).



                                                    Would you like to answer one of these unanswered questions instead?



                                                    Popular posts from this blog

                                                    រឿង រ៉ូមេអូ និង ហ្ស៊ុយលីយេ សង្ខេបរឿង តួអង្គ បញ្ជីណែនាំ

                                                    QGIS export composer to PDF scale the map [closed] Planned maintenance scheduled April 23, 2019 at 23:30 UTC (7:30pm US/Eastern) Announcing the arrival of Valued Associate #679: Cesar Manara Unicorn Meta Zoo #1: Why another podcast?Print Composer QGIS 2.6, how to export image?QGIS 2.8.1 print composer won't export all OpenCycleMap base layer tilesSave Print/Map QGIS composer view as PNG/PDF using Python (without changing anything in visible layout)?Export QGIS Print Composer PDF with searchable text labelsQGIS Print Composer does not change from landscape to portrait orientation?How can I avoid map size and scale changes in print composer?Fuzzy PDF export in QGIS running on macSierra OSExport the legend into its 100% size using Print ComposerScale-dependent rendering in QGIS PDF output

                                                    PDF-ში გადმოწერა სანავიგაციო მენიუproject page