It is possible that the font package is not installed.
You could try that with the --noautoremove option to skip the font package and see what it tells you then. The font package comes from fedora and chrome comes from google.
BTW, I just moved one system to F37 last night and it shows
google-chrome-stable x86_64 108.0.5359.71-1 @google-chrome 301 M
You can either install Google-Chrome creating a specif repository or download an .rpm package that creates the repository allowing updates : either way is fully documented on their website. Youâre reporting error from DNF package manager, remove specific repository file in /etc/yum.repos.d with console command rm. After, to keep yourself reassured, run âdnf clean allâ.
This is why a lot of answers are somewhat incorrect guesses. The problem here is that Google still uses the insecure SHA1 hashes and Rawhide rpm is more strict. You will need to loosen up your crypto policies to allow it to process the chrome rpm:
(adding information for people searching for solutions)
The official âcodeâ packages (Visual Studio Code, vscode) have the same problem and it can also be worked around with the command Elliott provided.
This issue happened to me today, on a Sunday night when I need Chrome in the morning at 8am. Not a fun time. I am running Fedora 38, latest updates, 3900x, 64GB ram and did nearly everything above, including reinstalling and reboots. I had to force power down my machine (power button) to force Fedora to offer the selecting the kernel menu. I was running kernel 6.3.6 and selected the previous 6.3.5 and booted up. Now Chrome installs properly and I can access all my bookmarks and saved sites. It would seem if you are using Fedora, it is not always a browser issue. Might be the latest kernel⌠But I defer confirmation of that to people smarter than me in Kernel design⌠Hope this helps someone else while Fedora and Chrome issue patchesâŚ