Fedora

Chrome and missing key

Are you using Chrome in Fedora? You might have noticed messages about a missing public key and you may have encountered problems with updating the application. That’s because Google fails to provide the public key for the Chrome RPM package. It’s become a serious problem in Fedora 22 where it aborts the update process completely and the package can’t be updated. The most convenient solution for users would be importing they key while installing the package, but some argue that an RPM should never automatically import keys.

Another solution is to simply add the following line to the repo file that the installation creates:

gpgkey=https://dl-ssl.google.com/linux/linux_signing_key.pub

And you’ll be asked to confirm the key import during the next updating. This solution is a one-liner. It was reported to Google 10 months ago and the problem has not been fixed yet. This a bright example of problems with using proprietary software. You’re completely dependent on the vendor and on their will to solve your problems. Fedora developers are sometimes accused of not caring about how proprietary software runs on Fedora. At least here in the desktop team, we do care because we care about the experience our users have using Fedora. But in most cases including this one, we just can’t do anything. I can only advise you to import the key manually to get rid of the problems:

sudo rpm --import https://dl-ssl.google.com/linux/linux_signing_key.pub
Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s