This is incorrect. Flash is still bundled with Chrome and will only be removed “toward the end of 2020” (basically when Adobe stops supporting it). Chrome also uses the more secure sandboxed PPAPI version of flash, whereas Chromium uses the unsandboxed NPAPI version.
Apart from flash and codecs, the main difference comes down to building and testing. Google tests each Chrome release, but doesn’t even do any releasing of Chromium. That’s managed by the different distributions which may or may not do testing, release in a timely manner and change code including sandboxing. More details can be found here.
I think openSUSE does a pretty good job so that PPAPI vs NPAPI flash and codecs supported are the only significant differences.
hmm I remember a few threads about flash missing from google chrome’s distribution
Adobe did restart development and distribution of flash for linux so while opensuse does not redistribute flash the packman repo does, updating a browser just to update a plugin is beyond silly
afaik the main difference between Chromium and Chrome is the spyware google puts in to track our browsing habits one of the reasons to prefer Chromium
Perhaps there is an other reason. Since chrome 60, there is an other update-system. Its in the browser self. I therefore think you don’t have to have an repo.
But maybe i am wrong (however, till now its working)
Hello, I just imported Google’s linux_signing_key.pub, added their repository, received the same error. I found this thread by Google searching:
File ‘repomd.xml’ from repository ‘Google-Chrome’ is signed with an unknown key ‘1397BC53640DB551’. Continue?
I then downloaded the key 0x1397BC53640DB551 from https://keyserver.opensuse.org and tried to import it into Yast. It appears the key ‘1397BC53640DB551’ is identical to key ‘7721F63BD38B4796’, the Google, Inc (Linux Packages Signing Authority) Key, which was already imported from linux_signing_key.pub. See the following screenshot.
What I am getting out of that thread is that Google started signing their repositories with subkeys, which provide increased security, but zypper does not support subkeys. So this is an issue with that should be fixed in zypper.
Bingo - Google started using subkeys, Zypper does not support them (yet). So this is a problem with zypp and needs to be fixed by the SUSE development team.
The easy solution to the problem is to uninstall Google Chrome; install chromium from the official repositories; then install chromium-ffmpeg-extra, chromium-plugin-widevinecdm, and flash-player-ppapi from Packman. It provides the same functionality as Google Chrome with much less stress than dealing with these signature issues.
Has anyone reported that to bugzilla? Otherwise I think it won’t get fixed.
But the actual problem is the key signing, not how to replace one program with another. Google Chrome is not identical to Chromium as mentioned in earlier posts.
Concerning the discussion of Chromium vs. Chrome it’s also worth noting that for web or extension developers it’s important to be ahead of the curve (i.e. notice if anything breaks before it breaks for the majority of people) and AFAIK no repo with a package of the beta channel Chromium exists while for Chrome it does.
Well,
In my case it’s still the same. I have the latest libzypp in Leap 42.3 and I still see the same issue with subkeys, although I removed all Google GPG keys and re-added them manually.