I use a recent standalone version of Ungoogled Chromium so I know it's possible. Firefox is easy to run current.

How can I get 120s Chromium .deb for Xenial?

I need to overcome all the NSS & GLIB errors. Of course once the Chromium dependencies are in, all our Chromium-based browsers will run.

duplicate of https://www.linuxquestions.org/quest...me-4175730101/

Good reminder I forgot. I'm persistent.

I did add new information:

I'm using Chromium 117 in Xenial. It's standalone. If I had more technical experience, I would just grab the dependencies for a .deb install, so I thought I'd ask.

I asked the Ubuntu crowd & the response I received asserts the vulnerabilities are in the os. To me, that vindicates the browser even more.

Should I use an out-dated browser in an unsupported os, or a new browser in an unsupported os?

If new browsers in recently unsupported os are a big problem, I'll need to trip on that myself.

More progress:

I'm in a new Chromium again by AppImage. The os required one additional dependency libnss3 I acquired from Debian.

So I can get on by standalone or AppImage. The achievement will be finding those Xenial .deb.

So far so good:

Attached Thumbnails

 

Chromium updates to 90 in Ubuntu 16.

106 works with normal dependencies (3 total). Shouldn't browsers update to the most current compatible version?

I am sure amd64 106 .deb are out there but they are not easy to find.

https://askubuntu.com/questions/8905...on-of-chromium

https://launchpad.net/~savoury1/+arc...buntu/chromium offers version 112 for Xenial.
(For bionic and newer, current version is offered, 121 as of today).

Of course, flatpak or snap are options if you need current version too, but that won't get you dependencies. I suspect it cannot be built with the libraries offered in Xenial, so any build that works on there would be doing static linking or whatever it's called to include bundled dependencies, similar to Appimage, so wouldn't help you with other browsers either.

Seems its time to upgrade your OS version.

I've run an AppImage of 120 in Xenial with a warning, but it works. For now 106 is acceptable as .deb though not seeing it anywhere.

112 probably means additional dependencies.