How do I fix Chrome apt sources when upgrading from 22.04 to 24.04?

Support and Help
1

Ubuntu Version:
Upgraded from 22.04 to 24.04

Desktop Environment (if applicable):
GNOME

Problem Description:

I upgraded today from 22.04 to 24.04. The upgrade went well, apart from one item: Google Chrome.

Before the upgrade, /etc/apt/sources.list.d/google-chrome.list looked like this (with comments removed):

deb [arch=amd64] https://dl.google.com/linux/chrome/deb/ stable main

After the upgrade, the file has been replaced with google-chrome.sources. Its contents are:

Enabled: no
Types: deb
URIs: https://dl.google.com/linux/chrome/deb/
Suites: stable
Components: main
Signed-By:
 -----BEGIN PGP PUBLIC KEY BLOCK-----
 [removed for brevity]
 -----END PGP PUBLIC KEY BLOCK-----

I’ve changed Enabled: no to Enabled: yes.

Error Messages:

Unfortunately, now when I run sudo apt update, I get an error message:

N: Skipping acquisition of configured file 'main/binary-i386/Packages', as repository 'https://dl.google.com/linux/chrome/deb stable InRelease' doesn't support architecture 'i386'

What I’ve Tried:

I don’t know what to do about this, partly because I don’t understand the error message.

I tried reinstalling Chrome from the official website, in the hopes that this would fix it, but it didn’t.

I removed the sources file (after making a backup) and reinstalled Chrome again, but that also didn’t help.

What can I do about this error, please?

Thank you

2

Paddy I’m not sure where you are currently on the source issue:
This is how I got it working:

 sudo /usr/bin/wget -q -O - https://dl.google.com/linux/linux_signing_key.pub | gpg --dearmor | sudo tee /etc/apt/trusted.gpg.d/google.gpg >/dev/null
gpg: WARNING: unsafe permissions on homedir '/home/me/.gnupg'

Not the same error, after update:

Warning: https://dl.google.com/linux/chrome/deb/dists/stable/InRelease: The key(s) in the keyring /etc/apt/trusted.gpg.d/google.asc are ignored as the file is not readable by user executing gpgv.
Warning: https://dl.google.com/linux/chrome/deb/dists/stable/InRelease: The key(s) in the keyring /etc/apt/trusted.gpg.d/google.asc are ignored as the file has an unsupported filetype.
Warning: https://dl.google.com/linux/chrome/deb/dists/stable/InRelease: The key(s) in the keyring /etc/apt/trusted.gpg.d/google.gpg are ignored as the file is not readable by user executing gpgv.
Warning: https://dl.google.com/linux/chrome/deb/dists/stable/InRelease: The key(s) in the keyring /etc/apt/trusted.gpg.d/google.gpg are ignored as the file has an unsupported filetype.

This worked for me.

sudo apt modernize-sources

This is shown after:

The following files need modernizing:
  - /etc/apt/sources.list
  - /etc/apt/sources.list.d/google-chrome.list

Modernizing will replace .list files with the new .sources format,
add Signed-By values where they can be determined automatically,
and save the old files into .list.bak files.

This command supports the 'signed-by' and 'trusted' options. If you
have specified other options inside [] brackets, please transfer them
manually to the output files; see sources.list(5) for a mapping.

For a simulation, respond N in the following prompt.
Rewrite 2 sources? [Y/n] y
Modernizing /etc/apt/sources.list...

Modernizing /etc/apt/sources.list.d/google-chrome.list...
- Writing /etc/apt/sources.list.d/google-chrome.sources

After update:

sudo apt update
Hit:1 http://archive.ubuntu.com/ubuntu questing InRelease
Hit:2 http://archive.ubuntu.com/ubuntu questing-updates InRelease              
Hit:3 http://security.ubuntu.com/ubuntu questing-security InRelease            
**Hit:4 https://dl.google.com/linux/chrome/deb stable InRelease**                  
Hit:5 http://archive.ubuntu.com/ubuntu questing-backports InRelease            
Hit:6 http://archive.ubuntu.com/ubuntu questing-proposed InRelease
Hit:7 https://ppa.launchpadcontent.net/graphics-drivers/ppa/ubuntu plucky InRelease
Hit:8 https://ppa.launchpadcontent.net/heyarje/makemkv-beta/ubuntu plucky InRelease
Hit:9 https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu plucky InRelease
Hit:10 https://ppa.launchpadcontent.net/teejee2008/foss/ubuntu noble InRelease
All packages are up to date.

Something like this:

sudo grep -r google  /etc/apt | grep -v amd64 
/etc/apt/sources.list.d/google-chrome.sources:URIs: https://dl.google.com/linux/chrome/deb/
/etc/apt/sources.list.d/google-chrome.sources:Signed-By: /etc/apt/trusted.gpg.d/google-chrome.gpg
grep: /etc/apt/trusted.gpg.d/google-chrome.gpg: binary file matches
grep: /etc/apt/trusted.gpg.d/google.gpg: binary file matches
2 Likes
3

Your google-chrome.list file was converted to the DEB822 format but not completely it appears. This part, "deb [arch=amd64] ", should have caused the upgrade script to add the following newline “Architectures: amd64” to the new google-chrome.sources file. This will tell apt to only download lists for the packages built for the amd64 architecture despite having any other architectures (like i386) defined by apt’s config setting “Apt::Architecture”.

So adding “Architectures: amd64” to the google-chrome.sources file and re-updating the package lists should get rid of that warning. You might also want to file a bug.

2 Likes
4

Thank you. This helps with my understanding of what happens.

This did the job, thank you!

I’ll try to do so now, and post the link here.

Interestingly, I notice that, as with snap, launchpad.net doesn’t respond when I use IPv6. I’ll report that as well.

1 Like
5

I have reported the bug.

Thank you again for your help!

1 Like
6

Glad it worked for you. And thanks for filing the bug!

1 Like
7

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.