Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Question] Prevent that warning from appearing: "This computer will soon stop receiving Chromium updates because its hardware is no longer supported" #107

Open
Golffies opened this issue Dec 3, 2020 · 4 comments

Comments

@Golffies
Copy link

Golffies commented Dec 3, 2020

Chromium installed from ppa:saiarcot895/chromium-beta and running on a 32bit Intel CPU limited to SS2 instructions set, displays after each restart that warning: "This computer will soon stop receiving Chromium updates because its hardware is no longer supported" (the transcription may not be verbatim).

Is there a setting in chrome://flags or an option with which to start the application to prevent this alert from appearing each time Chromium is restarted?

At the time of writing, the Chromium's version is 87.0.4280.66-0ubuntu1~ppa1~18.04.1

Thank you.

@thetick1234567890
Copy link

thetick1234567890 commented Dec 3, 2020

NOTE: I'm just a user like anyone else but I will offer my opinion anyway.

I think users NEED that comment. I have some decade old AMD and Intel laptops though all are 64-bit and support SSE{1,2,3...} instructions (Sandy Bridge and Fusion APU based). I sure would like to know if and when software is not longer able to execute or update due to an extremely old CPU.

Anyway Chrome and Chromium are not going to lower their requirements and surely at some point increase the requirement:

See https://support.google.com/chrome/a/answer/7100626?hl=en

Linux
To use Chrome Browser on Linux, you'll need:

64-bit Ubuntu 14.04+, Debian 8+, openSUSE 13.3+, or Fedora Linux 24+
An Intel Pentium 4 processor or later that's SSE3 capable

You may soon be forced to build Chromium yourself with compile options specifically for your processor, but that is a very long and very painful process with all the dependencies for build even cross compiled on a modern machine.

@saiarcot895
Copy link
Owner

I'm in favor of keeping this notice, because as of today, Ubuntu 18.04 is the only Ubuntu version for which there is an i386 build in my PPA (Ubuntu 16.04 fails in the final linking stage because it runs out of memory; I can maybe have it be a component build, but 16.04 will be EOL soon anyways). For Ubuntu 20.04, I cannot build i386 packages.

Additionally, while it might be possible for me to make some small code changes that allow it to compile without it using SSE3 instructions, that's going to get harder as time goes on, as they use more low-level SSE3 instructions, so that's not going to be sustainable for me.

@Golffies
Copy link
Author

Golffies commented Dec 3, 2020

Thank you both for your comments.

I hope to have been able to interpret all their meanings, especially the availability of the SS2-only flavour for 18.04. At the moment, Chromium beta 32-bit for 18.04 runs on my SS2 CPU. Am I right to understand that it will be always the case, as long as I remain with 18.04? Or should I have instead understood that in a close future, Chromium beta 32-bit for 18.04 will require SS3 support?

Returning to my original question, it was not my intention to ask for the warning to be withdrawn. However, once the user has read it several times (each time Chromium is restarted), the warning is no longer informative, it becomes disturbing. Please believe me: after a hundred times it becomes irritating.

My question remains: does the end user have a means of disabling the warning, which he has already read many, many times, so that he can use the entire screen area when starting Chromium.

Thank you.

@saiarcot895
Copy link
Owner

From what I recall, there's no way to disable the warning.

At this time, Chromium has moved on to requiring SSE3 (starting with version 89), and had removed that message.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants