RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

If a user is not allowed to install update because the system is 'managed', we should not show him update lists and an 'restart and install' button - he can't use it.

Just to clarify: this is different from a totally locked down system, where gnome-software should just not be installed. Here, the user is still expected to use gnome-software for finding and installing applications, but the updates are centrally managed.

This is really a gnome-software bug, but it doesn't have a bz component yet, so filing against gnome-packagekit for now.

Another thing to look at in this context is software sources - if the polkit privileges are missing to change repositories, we shouldn't offer the big red remove button.

Created attachment 1028452 [details]
incomplete patch

Here is a quick proof-of-concept.

To try it, UPDATES_ARE_MANAGED=1 ./gnome-software (after killing your session service). Also try UPDATES_ARE_MANAGED=1 ./gnome-software --mode=updates

Still tbd: How do we determine if the system is managed - look at polkit privileges, add a separate setting, something else ?

More complete patch in the upstream bug

We backported the patch to gnome-software 3.14.6 which is the version included in the rebase errata.

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHEA-2015-2139.html