Bug 1745745

Summary:	chromium bothers me with impossible updates and asks me to install Google Chrome
Product:	[Fedora] Fedora	Reporter:	Miro Hrončok <mhroncok>
Component:	chromium	Assignee:	Tom "spot" Callaway <tcallawa>
Status:	CLOSED EOL	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	30	CC:	akarshan.biswas, tcallawa, tpopela, yaneti
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-05-26 17:29:25 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Miro Hrončok 2019-08-26 19:38:21 UTC

Description of problem:
chromium tells me it's old. It tells me it cannot be updated and I should reinstall it. It points me to https://www.google.com/chrome/?&brand=CHWL&utm_campaign=en&utm_source=en-et-na-us-chrome-bubble&utm_medium=et and wants me to grab Google Chrome instead.

Version-Release number of selected component (if applicable):
chromium-75.0.3770.100-3.fc30.x86_64

How reproducible: Run older chromium than the latest one.


Steps to Reproduce:
1. Run chromium 75.

Actual results:
The menu button (top right corner) goes red. When clicking it, it says something like "Your chromium is old." (I have Czech locale, so the text is not 100% accurate here.) When clicking it, is say something like "Cannot update Chromium, you don't have the latest features and security fixes." and it urges me to **Reinstall** -> that button leads to https://www.google.com/chrome/?&brand=CHWL&utm_campaign=en&utm_source=en-et-na-us-chrome-bubble&utm_medium=et

Expected results:
dnf handles chromium updates, not chromium

Additional info:
This migth be fixed in chromium 76, but I guess I will not be able to reproduce until 77 is out.

Comment 1 Akarshan Biswas 2019-10-03 15:31:04 UTC

This bug has been reported against chromium-vaapi as well(See: https://github.com/akarshanbiswas/chromium-vaapi/issues/13). It needs investigation. This might be a bug is chromium itself.

Comment 2 Akarshan Biswas 2019-10-15 07:29:50 UTC

Fixed upstream: https://chromium.googlesource.com/chromium/src.git/+/e79d9d0e06b825d2e62b38db03248c0e6ceec7e4

Comment 3 Ben Cotton 2020-04-30 20:57:13 UTC

This message is a reminder that Fedora 30 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 30 on 2020-05-26.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '30'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 30 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 4 Ben Cotton 2020-05-26 17:29:25 UTC

Fedora 30 changed to end-of-life (EOL) status on 2020-05-26. Fedora 30 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.