Comment 77 for bug 1641380

Okay, that didn't take long. My slack windows started to "Aw snap!" within another 10 minutes.

Both the Xenial [*1] version and the version from Haw Loeung (hloeung) [*2] work fine though. Where the second is better because the broken Xenial version is lower and would be auto-replaced with the broken Yakkety build until a fixed version is uploaded.

Answering w2vy's (tom-moulton) question: a fixed version will likely be still higher and auto-update over these manually installed files. In short: no manual uninstall will have to be performed.

[*1]
http://nl.archive.ubuntu.com/ubuntu/pool/universe/c/chromium-browser/chromium-browser_53.0.2785.143-0ubuntu0.16.04.1.1257_amd64.deb
http://nl.archive.ubuntu.com/ubuntu/pool/universe/c/chromium-browser/chromium-browser-l10n_53.0.2785.143-0ubuntu0.16.04.1.1257_all.deb
http://nl.archive.ubuntu.com/ubuntu/pool/universe/c/chromium-browser/chromium-codecs-ffmpeg-extra_53.0.2785.143-0ubuntu0.16.04.1.1257_amd64.deb

[*2] from: https://launchpad.net/~canonical-chromium-builds/+archive/ubuntu/stage/+sourcepub/7137607/+listing-archive-extra
https://launchpad.net/~canonical-chromium-builds/+archive/ubuntu/stage/+files/chromium-browser_53.0.2785.143-0ubuntu2.16.10.1323_amd64.deb
https://launchpad.net/~canonical-chromium-builds/+archive/ubuntu/stage/+files/chromium-browser-l10n_53.0.2785.143-0ubuntu2.16.10.1323_all.deb
https://launchpad.net/~canonical-chromium-builds/+archive/ubuntu/stage/+files/chromium-codecs-ffmpeg-extra_53.0.2785.143-0ubuntu2.16.10.1323_amd64.deb

Answering Eloquence's (eloquence) question:
- find the broken packages on your system:
  $ dpkg -l | grep chromium
- select and download the replacements from here:
  https://launchpad.net/~canonical-chromium-builds/+archive/ubuntu/stage/+sourcepub/7137607/+listing-archive-extra
  (pay attention to your architecture (arm vs amd64))
- install the downloaded files:
  $ sudo dpkg -i THE_DOWNLOADED_FILES...

P.S. I'm a bit puzzled that the fix for Xenial didn't get into Yakkety immediately. Now I ran into this issue on two separate occasions.