Bug 2165126

Summary:	Prompted to install updates that are not prepared
Product:	Red Hat Enterprise Linux 9	Reporter:	Michael Catanzaro <mcatanza>
Component:	gnome-software	Assignee:	Milan Crha <mcrha>
Status:	CLOSED MIGRATED	QA Contact:	Desktop QE <desktop-qa-list>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	9.2	CC:	klember, rhughes, tpopela
Target Milestone:	rc	Keywords:	MigratedToJIRA
Target Release:	---	Flags:	pm-rhel: mirror+
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-07-24 06:55:35 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:
Bug Depends On:	2056721
Bug Blocks:

Description Michael Catanzaro 2023-01-27 19:07:50 UTC

In RHEL 9.1, I just received a desktop notification from GNOME Software prompting me to install updates that were not yet downloaded. By default, desktop notifications should only be created after the update is prepared (all updates are downloaded) with the only exception being if automatic update downloading is disabled (I did not disable that). This is the same bug that existed in Fedora 34-37 until it was recently resolved.

We probably need https://gitlab.gnome.org/GNOME/gnome-software/-/merge_requests/1401 and https://gitlab.gnome.org/GNOME/gnome-software/-/merge_requests/1565 at least.

Comment 1 Milan Crha 2023-01-31 16:44:02 UTC

Thanks for a bug report. There are more things to be backported and maintained, because the 41.5 has missing things done since then, which are related to this update monitor/PackageKit plugin. One such is commit 336737c374031f7f30e52a58b2a3745fe5ef2023 (I would reference it directly, but the GNOME's GitLab is currently down due to a maintenance).

The 42.x and 43.x received significant amount of API and internal architectural changes, where some of them can influence the proposed patches to be backported, which means a high maintenance burden. Not talking that apart of making mistakes in the backport, I'll surely forget some of the needed patches.

Comment 2 Michael Catanzaro 2023-01-31 19:50:09 UTC

Might be easiest to just rebase to whatever version you're most comfortable with.

Comment 3 Milan Crha 2023-02-21 12:56:43 UTC

Right, it should be easiest to rebase, but to the most recent version (44.x series at the moment), to not try to find out all the related changes. Problems/changes with the rebase:

* the 44.x will need the latest gtk4 (related to bug #2056721, but gnome-software needs 4.9.2)
* will need the latest libadwaita (not in RHEL9 yet, requires 1.3.alpha at the moment)
* the current fedora version builds against libsoup3, which is not part of the RHEL9, but it can be switched to libsoup2
* RHEL9 has PackageKit 1.2.4, but 1.2.5 and 1.2.6 contain changes related to gnome-software
* there landed significant changes for the 44.beta, which are not fully/thoroughly tested yet (one crash found already)

Due to the above, let's wait for the rebase until the dependencies are satisfied and the latest changes properly tested. It can be in time of 45.0, rebasing to 44.x (whichever version will be the latest).

Comment 4 Tomas Popela 2023-07-24 06:51:49 UTC

This is targeted for 9.4 and 9.4 will be tracked in JIRA, let me migrate this to JIRA.